Open ccarouge opened 4 months ago
Some work on the CABLE-POP_TRENDY branch is needed for this. The branch currently contains a number of input and configuration routines that are hard-coded to filenames and hidden configurations e.g. in CRU_INIT
and CRU_GET_FILENAME
subroutines in cable_cru_TRENDY.f90. Should generalise these routines and remove "hidden" configuration parameters, shifting them to the externally visible namelist files.
I had to clone the CABLE repo to get the CABLE-POP-TRENDY branch (again), when I noticed this branch/issue and the name sounded like what I was doing, although it isnt.
I started months back on "merging" the CABLE-POP branch into CABLE3 but it has been so long that I can't exactly remember which files come from where. What I am doing first is pushing the POP branch into the same format as the CABLE3 code. I set it up to build/run serial without POP. I dont care about merging the POP part, whatever is in Juergen's branch will totally over-ride whatever we have. So apart from some minor changes to get it to build/run the code is on the way to being in the same "format". I put it down in the middle of things and just to verify that some of the files that I have already moved are exactly Jurgen's, but it has been so long that my copy, probably on SCRATCH/ has disappeared.
it has been so long that my copy, probably on SCRATCH/ has disappeared.
Do you mean everything has disappeared or have you pushed your work to GitHub? If it's still on GitHub, it would be good to have a branch name and an issue opened for that work, since that is not what this issue is about. I'll modify the title to make this clearer.
If you still have the work in a branch, it sounds like we made more progress towards CABLE4 than I thought.
it has been so long that my copy, probably on SCRATCH/ has disappeared.
Do you mean everything has disappeared or have you pushed your work to GitHub? If it's still on GitHub, it would be good to have a branch name and an issue opened for that work. Since that is not what this issue is about. I'll modify the title to make this clearer.
Nah, all good. I meant just my local copy of Jurgen's branch
@Whyborn I think this issue is too wide and in essence a duplicate of #207 . I'm changing it's description to only be about reading the met. files. The rest of the work should be done in separate issues.
Create a new reading routine for the meteorological forcings. This routine should be generic to work with CRU met forcings and with the CMIP6 output format.
We want to test using the daily output from the historic simulation with ESM1.5. Details about the exact met forcing we will use from CMIP6 is here.