Skip to content

Feature/atmosphere db 2

Georgios.Voutsinas requested to merge feature/atmosphere_db_2 into main

Molecular atmosphere & DB.

In molecular atmosphere calibration we are mostly doing 3 things

  • produce reference models
  • produce tailor models
  • select reference models

The first two cases (model production) are covered by the atmospheric_model_db_loader.py: in case of a reference model production (which is expected to happen every few years) the tool will be manually invoked by the calibration scientist or whoever responsible. In case of tailored model production, this tool can be called after the production. It can be added as a separated workflow or in a common workflow as a second step or as a single tool (to be discussed).

The selection of reference models is treated in this MR. All metadata (date, provenance, season, site, version) are stored in the DB. The version in particular is retrieved by the atmospheric model table. Again here we need to clarify a bit again what a version is: does it correspond to a reference model production?

Unlike the reference/tailored models, the version is not the key here. The reason is the following: during a year, all night were e.g. the WINTER model is a selected, the version corresponds to the same reference model production. Therefore we can't achieve the key uniqueness. Need to think a bit what's the key here: to what should actually relate a selected model?

Closes #158 (closed)

Related to #128 (closed)

Edited by Mykhailo.Dalchenko

Merge request reports