Add information on access to input files in CABLE documentation

[ccarouge]

While we don't have published configurations in GitHub, do we want to add to the documentation some information on where to find the input files?

For example, for pftlookup.csv, we could add here that Gadi users should use /g/data/rp23/data/no_provenance/casa/pftlookup.csv and non-Gadi users should ask on the ACCESS-Hive Forum.

Is that useful?

[mcuntz]

Links on Gadi are unfortunate. Not even every researcher in Australia has access to NCI.

Why not adding a page in the documentation where the pftlookup.csv is given in a code box so that one can copy/paste it, just like it is done for the pft_params.nml and cable_soilparm.nml?

Or instead of removing the symlink in srcoffline, one could also copy a pftlookup.csv` there.

[SeanBryan51]

For example, for pftlookup.csv, we could add here that Gadi users should use /g/data/rp23/data/no_provenance/casa/pftlookup.csv and non-Gadi users should ask on the ACCESS-Hive Forum.

I would avoid putting the full path there, if someone changes the location of that input file on Gadi, it's likely they are going to forget to update it in the documentation.

I think it would be great to provide small sized input files on GitHub which allow for running CABLE in different ways. E.g. to run:

• Site simulations (these inputs are already available in src/offline)
• Spatial simulations over a small area and/or period (e.g. small test case over ACT)

And of course, to enable additional science like CASA, we can provide these input files too provided they are small enough. This could provide examples for users to base their own configurations off of.

I like the idea of having these in the CABLE repository, as we could run these small test cases as part of the CI so that they are always up to date.