Work out how to trigger reprocessing of datasets with multiple calibration edits

[squaregoldfish]

If someone edits multiple calibrations together, the affected datasets are queued for reprocessing each time. This results in multiple jobs scheduled for the same dataset and QuinCe gets very confused. We probably need a way to abort existing jobs, which will work since all the jobs automatically recover themselves from a partial run state.

See also #205

• [x] Single edit in a session
  • [x] External Standards
  • [x] Sensor Calibrations
  • [x] Calculation Coefficients
• [x] Implement front end updates
  • [x] Timeline key
  • [x] Add
  • [x] Edit
  • [x] Date
  • [x] Value
  • [x] Target
  • [x] Delete
  • [x] Implement Save button
  • [x] Saves to database
  • [x] Queues datasets for reprocessing
• [x] Write tests for CalibrationSet
• [x] Multiple edits in a session
  • [x] External Standards
  • [x] Sensor Calibrations
  • [x] Calculation Coefficients
• [x] Calibrations are/are not required (depends on instrument variables)
  • [x] External standards for underway pCO2
  • [x] Sensor Calibrations never
  • [x] CONTROS requires calculation coefficients before and after (does not prevent edit - only warns)
• [x] Ensure datasets are recalculated properly (see #2980)
  • [x] External Standards
  • [x] Sensor Calibrations
  • [x] Calculation Coefficients
• [x] Show calibrations in Create New Dataset timeline
• [x] Handle change of external standards in dataset (data reduction)
• [x] Handle change of sensor calibration in dataset (data extraction) (ExtractDataSetJob:280 ish)
• [x] Change of external standards & sensor calibrations in dataset - check export JSON includes them
• [x] Change of external standards in dataset - check QC screen
• [x] Change of external standards in dataset - Standards Offset QC check
• [x] Do not allow creation of dataset if calculation coefficients change (create dataset, NRT?)
• [x] Calculation coefficients in manifest

[squaregoldfish]

Keep the bean alive until "Back to Instruments List". Aggregate all changed datasets, and submit the jobs when that's clicked.

[squaregoldfish]

For each dataset, record pre-edit and post-edit state of which calibrations affect it. If any have changed after all edits made, they need to be reprocessed.

[squaregoldfish]

1279

[squaregoldfish]

Don't let calibrations be moved/created in the middle of an existing dataset (related to #2584)

[squaregoldfish]

2342

"An alternative algorithm could determine the maximum number of datasets affected (based on where the edit took place) and then examine each dataset in turn to see if it's affected. The speed of the algorithm probably wouldn't changed, but the code could well be a lot clearer."

[squaregoldfish]

Show calibrations in correct display order on timeline (e.g. CONTROS calculation coefficients should be in LinkedHashMap order)

[squaregoldfish]

CONTROS coefficients affect the datasets both before and after the entries. Gas standards are only after. Sensor calibrations may be either. How do we deal with this?

[squaregoldfish]

Notes for initial setup and single edit actions.

[squaregoldfish]

2584

[squaregoldfish]

Ready to go. Waiting for discussion with Ingunn.