-
Notifications
You must be signed in to change notification settings - Fork 0
CreateNewMetFiles
CABLE met files should follow the ALMA convention although codes within cable_input.f90 can deal with some common conventions and scale the values to the suitable units used by CABLE.
The example file convert_metDH.f90 was used some years ago to create a netCDF met file from text files that are distributed by FLUXNET. It also shows how, in single-site studies, users can insert into the met file some parameters particular to the site. However, as CABLE codes have improved since then, those parameters that exist in the def_veg_params.txt file would be easier to be manipulated in the def_veg_params.txt file rather than in the netCDF met file.
The example script rewrite_EucFACE.R was written in 2013 to write a met file for the EucFACE community for a single-site in NSW. It was simple and had all the basic things that are required for CABLE. However, the EucFACE community uses 4-dimension variables (x,y,z,t) while CABLE normally uses 3-dimension variables (x,y,t). It should be easy to modify the R script to change the variables to 3D before the final writing of the file.