Template file writing
Issue
https://jira.esss.lu.se/browse/ECDC-4123
Description of work
The new features are that if you specify an instrument name in the start writing message, kafka-to-nexus should look for a template file and begin the filewriting based on the template instead of creating a new file from scratch.
There is also a "template-maker" that generates a NeXus template file containing the static datasets but without populated writer modules.
We will, therefore, not need to send the static data, such as detector geometry, over Kafka since it already exists in the templates.
The idea of this PR is also to make sure that if a filewriting job is sent with the same information as currently (no instrument name specified), it should write a file in the same way as before, so deploying this should not impact production.
Checklist
-
Changes have been documented in changes.md
-
Documentation has been updated in documentation
directory