The config has nested objects. Recursive nesting makes it tricky to combine configs, and flattening makes it easier.. The nesting is only needed to render the form in a nice way, for running the model/download/diff it does not matter.
So we could have a config like
{
"name": "my name",
"description": "my description",
"h_0": 200,
"theta_0": 288,
"dtheta_0": 1,
"q_0": 0.008,
"dq_0": -0.001,
"dt": 60,
"runtime": 43200,
"wtheta": 0.1,
"advtheta": 0,
"gammatheta": 0.006,
"wq": 0.0001,
"advq": 0,
"gammaq": 0,
"divU": 0,
"beta": 0.2
}For rendering the form we could store the grouping in the JSON schema as a "group: 'initialState'".
Derived from #80 (comment)
The config has nested objects. Recursive nesting makes it tricky to combine configs, and flattening makes it easier.. The nesting is only needed to render the form in a nice way, for running the model/download/diff it does not matter.
So we could have a config like
{ "name": "my name", "description": "my description", "h_0": 200, "theta_0": 288, "dtheta_0": 1, "q_0": 0.008, "dq_0": -0.001, "dt": 60, "runtime": 43200, "wtheta": 0.1, "advtheta": 0, "gammatheta": 0.006, "wq": 0.0001, "advq": 0, "gammaq": 0, "divU": 0, "beta": 0.2 }For rendering the form we could store the grouping in the JSON schema as a "group: 'initialState'".
Derived from #80 (comment)