Changes to distinguish Metop from EUM and UCAR [2 h]

[Ian Culverwell]

https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_pp/build/Makefile.am https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_pp/bangle/ropp_pp_bending_angle_go.f90 https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_pp/preprocess/ropp_pp_cutoff.f90 https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_pp/preprocess/ropp_pp_preproc.f90 https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_pp/preprocess/ropp_pp_preprocess.f90 https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_pp/preprocess/ropp_pp_preprocess_champ.f90 https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_pp/preprocess/ropp_pp_preprocess_cosmic.f90 https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_pp/preprocess/ropp_pp_preprocess_grasrs.f90 https://trac.romsaf.org/ropp/changeset/5427/ropp_src/branches/dev/Share/dmi_trunk_9.0/ropp_pp/tools/ropp_pp_spectra_tool.f90

Original changesets:

Changes to distinguish Metop from EUM and UCAR: https://trac.romsaf.org/ropp/changeset/4534/ropp_src/branches/dev/Share/dmi_trunk_8.0/ropp_pp/preprocess/ropp_pp_preprocess.f90

[Ian Culverwell]

Basically, Hans wants data with leo_id = 'MT??', which is supposed to identify GRAS data generated by UCAR, to have the default (non-)processing, unlike data with leo_id = 'ME??', which is supposed to identify GRAS data generated by EUM or DMI, which undergoes some mission-specific pre-processing and open loop processing. Unfortunately, it's been some time since GRAS data from UCAR had a leo_id of MT??, because the atmPhs and atmPrf reading routines in ROPP both say

  CALL ncdf_getatt('fileStamp', readstr)

  data%leo_id = readstr(1:4)

  IF ...

  ELSE IF ( data%leo_id(1:3) == 'MTP' ) THEN
    data%leo_id(1:3) = 'MET'

  ENDIF

So we need a more sopisticated decision tree, involving the processing centre as well as the leo_id.

Something like this has been in ROPP since v9.1, in fact.

Closing ticket, as ROPP has moved on since the start point of this ticket. Later tickets #594 and #596 address complementary aspects of this problem, and would make better starting points.