CMORize CCI LST - Microwave products

[morobking]

Description

• Closes Update and/or add ESA CCI datasets required for CMUG OWP4.3 #4234 (partially)
• Link to documentation:

---

Before you get started

• ☝ Create an issue to discuss what you are going to do

Checklist

It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

• 🛠 This pull request has a descriptive title
• 🛠 Code is written according to the code quality guidelines
• 🛠 Documentation is available
• 🛠 Tests run successfully
• 🛠 The list of authors is up to date
• 🛠 Any changed dependencies have been added or removed correctly
• 🛠 All checks below this pull request were successful

New or updated recipe/diagnostic

• 🧪 Recipe runs successfully
• 🧪 Recipe is well documented
• 🧪 Figure(s) and data look as expected from literature
• 🛠 Provenance information has been added

New or updated data reformatting script

• 🛠 Documentation is available
• 🛠 The dataset has been added to the CMOR check recipe
• 🛠 The dataset has been added to the shared data pools of DKRZ and Jasmin by the @ESMValGroup/OBS-maintainers team
• 🧪 Numbers and units of the data look physically meaningful

---

To help with the number of pull requests:

• 🙏 We kindly ask you to review two other open pull requests in this repository

[morobking]

Unsure how to correct these comments from Prospector:
cmorizers/data/formatters/datasets/esacci_lst.py
cmorizers/data/formatters/datasets/esacci_lst.py
Line: 50
mccabe: MC0001 / cmorization is too complex (16)
pylint: unused-argument / Unused argument 'cfg_user' (col 38)
pylint: too-many-arguments / Too many arguments (6/5)
pylint: too-many-locals / Too many local variables (22/15)
pylint: too-many-positional-arguments / Too many positional arguments (6/5)
Line: 68
pylint: logging-fstring-interpolation / Use lazy % formatting in logging functions (col 16)

Line 50: are the unused arguments sent into the function by ESMValTool, or can they be removed?
Line 68: Don't know how to fix this.

[morobking]

I've re-written this to handle ascending and descending better and independently.
See issue #4280

[morobking]

@axel-lauer I believe this is now ready at least for the CMUG OWP5.2 and OWP5.9 work.
A single yml file has all four sensors needed, and the python will look over ascending and descending. I've used the ideas from issue #4280 to give a different filename to the sensor/direction pairs.
No change to time is done, overpass time is as an attribute in the cube.
This code I've tested on the SSMI and ASMR MW data. Code has some things left as comments to give backward computability to older CCI LST versions.
Code should work with monthly but not tested, and should work with IR LST from CCI using DAY and NIGHT instead of ASCENDING and DESCENDING.

This is a slightly different way of doing thing than before. Not yet tested with the uncertainty variables but there is not variable name dependency in the python - just looking at whatever is passed from the yml.