bugfix: geoVaLs vector ordering for profiles

[twsearle]

Description

The "results" vector that contains the GeoVaLs data output by the interpolator was defined in the wrong order. This is only an issue if there is more than one level in the data, as there is for profile data.

The ordering should be by variable, z-level, and then horizontal location, with the location varying the fastest. So for the example of profile of 2 observations with two observed variables, the corresponding geovals from a 3 level background field would look like this:

Testing

• The ctests have been adjusted here and in nemo-feedback #18 to reflect this change.
• The geoVaLs were saved to file for some example data using the GOMSaver filter and double checked.

[SusanSun17]

Yeah Toby, you did it! 🥳

[twsearle]

thanks! Got there in the end :)