Writing invalid data to multifiles

[Huw Lewis]

When writing (appending) multiple-profiles to an output file ROPP assumes that the first profile contains valid data. This is because the netCDF output file is only defined based on the contents of the first profile to be written.

So, for example if profile 1 contains no valid Level1b data an output file is defined with no Level1b variables. If the subsequent profiles do however contain valid information, ropp_io_write will exit with an error when it tries to write information to an undefined variable.

Note, this is only an issue for running ropp2ropp with '-m' and no thinning (i.e. just for applying range checking to an existing set of profiles). In this case, a user would actually like to remove missing data, so it is just unfortunate if the invalid data are in the first profile.

This situation should be investigated, and a fix found if it does not overly complicate the write process.

[Huw Lewis]

No fix investigated as yet. For processing multi-files for ropp_pp development it has been necessary to place the biggest possible profile as the first in a file to ensure all data can be stored. Typically, these stand-alone tools would be run in single-profile mode in any case.

Ticket remains open for investigation at a later date.

[Huw Lewis]

No change in status. Move to 5.0. Note limitation documented in Release Notes.

[Dave Offiler]

Issue dealt with in #170.