ropp_pp mdi issues

[Ian Culverwell]

Investigate the difficulties ropp_pp has with missing data - principally, not always recognising it as missing. As Stig says:

3) As far as I understand, the ropp_pp tools are not geared to 
handle missing values, but missing values can be generated on input 
read because of the range-checking. I know that for output I can 
set the no-ranchk option, but I'd rather have range checks being 
fully optional on both input and output all over the ROPP codes. 
Certainly, in our operations, we need to handle missing values 
correctly or simply make sure that they are not there (and let 
processing terminate gracefully if there are some). Alternatively, 
instead of setting missing values on range checks the rangecheck 
could set the <variable>_qual values to 0 instead of 100. This way 
the _qual values would indicate which data points failed the range 
check. Would that be an idea?

Kjartan was also surprised that only for GRAS data are there checks on missing data at the "ingestion" stage: for CDAAC and ROSA data, -9999's are treated as real data.

[Ian Culverwell]

This is a long term piece of work. If anybody used ropp_pp there might be some incentive to do something about it! Meanwhile, moving to the "Whenever" category.

[Ian Culverwell]

I don't think this ticket should have been closed. It's still open, to be completed "whenever".

[Stig Syndergaard]

Many similar tickets under DMI ROPP development. Moving ticket to DMI development. Changing milestone and owner.