This issue supercedes the SRS ticket: https://code.metoffice.gov.uk/trac/moci/ticket/696
For Azure Mass the concept of simplex/duplex data is being replaced by a risk appetite, which can be low or very low. The --single-copy option will still exist, but will set the appetite to low, rather than very low.
References to simplex/duplex should be changed to risk appetite and the non_duplexed_set namelist option renamed, possibly to risk_appetite_not_v_low for clarity.
The -c=umpp option will no longer exist, so should no longer be used here. Conversion of fieldsfiles to pp files should be done during the transform, rather than archiving, stage of the code.
-vv is not a valid option for moo put and should be changed to -v
This issue supercedes the SRS ticket: https://code.metoffice.gov.uk/trac/moci/ticket/696
For Azure Mass the concept of simplex/duplex data is being replaced by a risk appetite, which can be low or very low. The --single-copy option will still exist, but will set the appetite to low, rather than very low.
References to simplex/duplex should be changed to risk appetite and the non_duplexed_set namelist option renamed, possibly to risk_appetite_not_v_low for clarity.
The -c=umpp option will no longer exist, so should no longer be used here. Conversion of fieldsfiles to pp files should be done during the transform, rather than archiving, stage of the code.
-vv is not a valid option for moo put and should be changed to -v