Draft: Rough sketch of injecting new constants after report creation

This is a sketch of an idea we discussed last week, to inject new constants after the notebooks have run, and the PDF report has been generated. With this in place, we would adapt the dark notebooks (or other characterisations run through the webservice) to just write constants with all the necessary metadata in their output directory, and remove the db_output parameter. Then the finalize job would find these constants and inject them.

Caveats:

1. We can avoid some CalCat API calls when injecting a group of constants all together, but I haven't done this yet. I don't think it fundamentally changes the logic.
2. This doesn't aim to support any manual review before injection - the newly generated constants are still injected straight away, just a bit later in the pipeline.
3. It means a couple more minutes delay before new constants are available - the main notebooks finish, the summary notebook runs, and the report is built. We could move injection before the report building to mitigate that a bit, but it would still be later than it currently is.
4. This is only meant for constants generated via the webservice (jobs running as xcal); we'd still need an injector service for manually generated constants before we could fully replace calDBRemote.

added 1 commit

• 750b63cf - Rough sketch of injecting new constants after report creation

Compare with previous version