Currently in both the Sensitivity driver and MadsTEMDriver the outputs that are enabled for the actual dvmdostem runs are tied directly to the targets specified by the user in their config files.
In some cases the user may wish to obtain additional NetCDF outputs for their runs beyond simply those needed to match the specified targets. One example of this might be if a user wishes to perform a check that nitrogen is actually being limited. In this case they will want the INGPP output (corresponding to the GPPALLIgnoringNirogen target value) along with the standard GPP output. There is currently no way for the users to specify this in the config file.
In this case we envision a setting in the config file that is passed thru to the drivers outputs list. The BaseDriver.setup_outputs(...) function will need to be extended or accompanied by another function.
Currently in both the Sensitivity driver and MadsTEMDriver the outputs that are enabled for the actual dvmdostem runs are tied directly to the targets specified by the user in their config files.
In some cases the user may wish to obtain additional NetCDF outputs for their runs beyond simply those needed to match the specified targets. One example of this might be if a user wishes to perform a check that nitrogen is actually being limited. In this case they will want the INGPP output (corresponding to the GPPALLIgnoringNirogen target value) along with the standard GPP output. There is currently no way for the users to specify this in the config file.
In this case we envision a setting in the config file that is passed thru to the drivers
outputs
list. TheBaseDriver.setup_outputs(...)
function will need to be extended or accompanied by another function.