CMORmeal: functionality scaling, data movement refining, ID of remaining gaps

[ilaflott]

note: difficulties in italics are very subjective!

up for grabs

• moderate: CMORmeal: figure out how to process 5-years worth of history files #287
• moderate: CMORmeal: omission tracking #269
• difficult?: CMORmeal: implement CMIP7 data-request usage, try using API? #286
• moderate: CMORmeal: cmor.yaml configuration file for fre cmor run use in fre-workflows #320
• wildcard: CMORmeal: remaining CMORization cases worth testing #321
• difficult: CMORmeal: how to handle different exp_config's? #322
• moderate: CMORmeal: let user or config specify grid, rewrite exp_config json accordingly #323
• easy: CMORmeal: make current DEBUG_MODE_RUN_ONE flag in fre/cmor/cmor_mixer.py #324
• easy: data movement discussions:
  • CMORmeal: cmor_mixer data movements- needed, wanted, or neither? #239
  • CMORmeal: cmor_mixer, logic for tmp_dir creation is awkward #240

not up for grabs

• almost done: CMORmeal: successfully process ocean variables on tripolar grid with cmor #298