ITM Database - defining additional entry fields

[onnieluk]

Some additional entry fields would be beneficial, IMO :-)
Here are a few I could think of so far, and they are the details I tend to vary a lot when I run the simulations:

• input CPO directory ID (e.g. 5 in AUG_28906_5)
• with or without IMP4DV?
• when using 2 turbulence codes, e.g. BGB for the first 20 steps then GEM for the next 1000 steps, it would be nice to have entries showing which code for how many steps, etc.
• what limits are set on the change in Te and dTe
• maximum TAU

I know most of these are information included in the CXA, but I thought it is useful to have them lay out in a table format when looking up database entries.

[olivhoenen]

Thanks @onnieluk (@DavidPCoster please also comment as you will be one of the main first customer for these saved shots):

1. input CPO directory: this will vary a lot, and is volatile so I would be more inclined to upload the input CPOs into a database, and refer to this input using for instance the topinfo/parent_entry

2. modules that are turned on or off I expect that this information is available from the workflow/script directly (saved in topinfo/workflow)

3. when a simulation has different phases, either this is all implemented within a single workflow/script (which is stored) or different workflows/scripts are used when continuing the simulation: in the latter case I would propose to store each continued simulation separately and refer to the previous one using the same topinfo/parent_entry mechanism

4. limits, TAU and other parameters of the workflow I expect to find them in the workflow/script saved in topinfo/workflow

If you want any given formalism for checking these or other parameters at a glance, I propose that you use topinfo/comment for this (remember, in Yaml you can format this string as you want, thus in some sort of table format if convenient).