JIRA ticket: LIMS-1917

Summary:

There is no mechanism for SynchWeb to be able to display the status of MX strategy/screening jobs. SynchWeb currently looks for records in the Screening table and if a record exists it will show the results of the pipeline and show that the job has completed. If a pipeline doesn't complete (even for a legitimate reason), there will be no record in SynchWeb that the pipeline has run. It would be good if SynchWeb could show the status of the pipeline (running, completed or failed) in the same way that it does for the autoprocessing and downstream pipelines.

The autoprocessing and downstream pipelines store their processing status in the AutoProcProgram table. The Screening table of ISPyB already contains autoProcProgramId as a foreign key which would allow a Screening record to be easily linked to an AutoProcProgram record.

The changes needed to the analysis pipelines will be deployed in January when @pblowey is back from parental leave, but the Synchweb changes can be done ready.

Changes:

• Get ScreeningStrategyWedge.comments for the alignment axes, rather than Screening.comments (both are currently populated, but the latter will not be in future)
• Display space group and unit cell for alignment pipelines, rounded to 2 decimal places
• Return screening statuses from the backend as an array, rather than a single value
• Get screening statuses with an autoProcProgramId as well as those without one. Merge the 2 arrays.
• Display "xia2-dials+dials.align_crystal" results in the same way as "dials.align_crystal" results. This means that LIMS-1904: Display new xia2-dials+dials.align_crystal pipeline #989 is superseded.

To test:

• Add 'xia2-dials+dials.align_crystal' to the $strat_align config variable, so it becomes

$strat_align = array('XOalign', 'dials.align_crystal', 'xia2-dials+dials.align_crystal');

• Go to an old screening run (eg /dc/visit/mx19800-74/id/6110714), check this is now shown as 2 mosflm successes and 4 EDNA successes, rather than one for each
• Go to /dc/visit/mx23694-144/id/19622929, where @pblowey has deliberately set 3 runs of "xia2-dials+dials.align_crystal", 1 each for success/failure/pending
• Check the Strategies bar shows 3 successes for "dials.align_crystal", and 1 success, 1 failure and 1 pending for "xia2-dials+dials.align_crystal"
• Expand the Strategies bar, check the 4 successes are shown, complete with space group and unit cell
• Check the Downstream Processing bar shows "No Processing Results", and if you expand it, it says "No downstream processing available for this data collection"