add PCL support to Express, fixes #3567 #3962
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When a run is configured, any express streams with the PromptCalibProducer alca producer will
be flagged for PCL. This means the system expects PCL conditons for that run/stream pair.
Inside the Express Spec we configure for ALCAPROMPT output from the PromptCalibProducer and
then add an AlcaHarvest task for it. The AlcaHarvest will write out sqlite files, for which
we add a dummy Condition task. A Condition task has a Condition job splitter, which does
not create any jobs, but just forwards sqlite file information to special t0ast db tables.
Second step (and not part of this ticket) is using the information in these t0ast tables
to upload the conditions to the dropbox and enforce doing this in run order.
Also not part of this ticket yet is a timeout trigger for the PCL.