GitLab

bugfix: substituting the accu signature on demand from the very depths of emitting job's param_stack

"parameter stack" implementation using two extra fields in job table. Accu content intended for any job_id has preference over Input_id content for the same job.

Dataflowing minimal information out of Runnables, relying on templates in PipeConfig file to extend it if needed

Start using the new db_conn.pl script instead of building driver-specific commands and running them.

Slow the example down a bit and allow 2 Workers. In "-can_specialize 1" mode the two Workers will complete the whole pipeline.

free 'Start' from dealing with 'a_multiplier' by using an input_id_template in PipeConfig instead; renamed 'Start' to 'DigitFactory' to reflect that

change of default behaviour: hive_capacity is now off by default (=NULL); setting hive_capacity=0 or analysis_capacity=0 stops scheduling AND specialization to a particular analysis

added a new per-analysis "analysis_capacity" limiter for cases where users want to limit analyses independently

Added API and schema support for analysis_base.meadow_type / Analysis->meadow_type(), which will be NULL/undef by default

Dropped 'BLOCKED' job status and introduced 'SEMAPHORED' status that is maintained in sync with semaphore_counts; less confusing and more efficient (with new 3-part index)

Removed maximise_concurrency and added analysis_stats.priority to guide the scheduler; improved scheduler and LSF meadow

Incorporate ENV hash into the tree of possible options in order to be able to "require" a value. And a bit of config inheritance cleanup.

Branch names proved to be too confusing. The functionality stays, but is removed from the example to follow.

big renaming of hive->worker, analysis_job->job, analysis_job_file->job_file, analysis_job_id->job_id, worker.beekeeper->worker.meadow_type, etc