You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the QCF requires an algorithm_info_mod specific to the model (really the QTYs filter is compiled with)
Is your feature request related to a problem?
Ease of building DART with the QCF options
Current model compilation (DART/developer_tests/build_everything):
only models with either QTYs that match DART/assimilation_code/modules/assimilation/algorithm_info_mod.f90 or a local algorithm_info_mod.f90 build successfully
Note this gets us over the compile time vs. runtime hurdle so users/us can build and run any model with QCF options.
There are bunch of science and user-interface discussions to be had.
Describe any alternatives you have considered
Thought about adding the QCF info to the quantity files, but this makes the algorithm_info choice a compile time choice.
input.nml - seems like too much info for a namelist
yaml/toml?
just for completeness here is the observation convert builds:
Use case
Currently the QCF requires an algorithm_info_mod specific to the model (really the QTYs filter is compiled with)
Is your feature request related to a problem?
Ease of building DART with the QCF options
Current model compilation (DART/developer_tests/build_everything):
only models with either QTYs that match DART/assimilation_code/modules/assimilation/algorithm_info_mod.f90 or a local algorithm_info_mod.f90 build successfully
/glade/scratch/hkershaw/DART/Quantile/build_everything/DART/developer_tests/build_everything
Describe your preferred solution
Read in the algorithm info choices at runtime:
https://docs.google.com/document/d/1MnvEFfgj5SfFbnIahGHwjy1XJ5IWBvPS8NB1nrIjc8k/edit
Note this gets us over the compile time vs. runtime hurdle so users/us can build and run any model with QCF options.
There are bunch of science and user-interface discussions to be had.
Describe any alternatives you have considered
Thought about adding the QCF info to the quantity files, but this makes the algorithm_info choice a compile time choice.
input.nml - seems like too much info for a namelist
yaml/toml?
just for completeness here is the observation convert builds:
The text was updated successfully, but these errors were encountered: