As of now, any invalid variable set in the variables.output and variables.diagnostic options is silently glossed over. It would be more helpful, especially now that we transition from regular to multipop cfg files, to get a warning or even an abort if a variable requested is not valid. This is very easy to add in datareduction/datareducer.cpp in the loop over DROs with the long list of if clauses.
As of now, any invalid variable set in the
variables.output
andvariables.diagnostic
options is silently glossed over. It would be more helpful, especially now that we transition from regular to multipop cfg files, to get a warning or even an abort if a variable requested is not valid. This is very easy to add indatareduction/datareducer.cpp
in the loop over DROs with the long list of if clauses.