DB setup and management
Summary
We need instruments to populate a freshly spawned DB and to simplify the importing and exporting data to the DB. Most of the code is already in place, however, a certain refactoring is required.
Currently the code that partially populates the DB for atmospheric calibrations is available in
calibpipe.tools.atmospheric_db_loader.
Another code, that is providing a convenient wrapper to upload data and metadata tables is written in the calibpipe.tests.unittests.database.test_metadata.
What is the expected correct behavior?
- TestMetadata
class fromcalibpipe.tests.unittests.database.test_metadatashall migrate undercalibpipe.database.interfaces.table_handler` -
calibpipe.tools.atmospheric_db_loadertool shall be refactored using the new functionality and also be renamed ascalibpipe_db_setupor similar. - Add a possibility to include/daisy-chain
yamlconfiguration files by bringing a yaml parser with an anchor support (likeruamel)- Check if the compatibility with
ctapipe.core.Toolinterface is preserved.
- Check if the compatibility with