Separation of model agnostic forcing preparation from other modelling files

[ShervanGharari]

I suggest separating the modeling files and forcing manipulation into two separate folders or steps. For example, the subfolders of folder 03-model-specific can be like this:

• 03-model-specific:
  • MESH:
    • Forcing
    • File
  • HYPE:
    • Forcing
    • File
  • MESH:
    • Forcing
    • File

The user then can set up a model without any specific forcing in hand. We can also centralize the Forcing manipulation in a more centralized way that can be easier called (actually then it would be kind of model agnostic). The model agnostic part can also follow the same logic. I understand currently it is possible, but it would be cleaner to separate the data tool and remap call and the gistool separately.

[kasra-keshavarz]

The current agnostic workflow appears to be functioning effectively across multiple applications I have encountered thus far, and making modifications would require more time than I can presently allocate to this project.

I trust that there may be another individual available who can adeptly refine the workflow in alignment with your vision.