You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a recent modeling team call we discussed the interest in the containerize FATES architecture but that the current limiting factor for many is that it still requires access to the met forcing, domain, surface, and ancillary files for the runs. These can be very large files with limited access
Instead we should develop or expand existing scripts that have been developed to extract single point versions from these gridded files. That way we could provide site-level data packages that can be used with container runs. For example, I modified a script that has been floating around to extract met forcing data to run for a single X-Y (see file). We can expand tools like this to extract the data for all ancillary files but maintain the folder structure making it easy for a user to download the data package, extract, and point the container run to this location as the cesm_input_data location.
On a recent modeling team call we discussed the interest in the containerize FATES architecture but that the current limiting factor for many is that it still requires access to the met forcing, domain, surface, and ancillary files for the runs. These can be very large files with limited access
Instead we should develop or expand existing scripts that have been developed to extract single point versions from these gridded files. That way we could provide site-level data packages that can be used with container runs. For example, I modified a script that has been floating around to extract met forcing data to run for a single X-Y (see file). We can expand tools like this to extract the data for all ancillary files but maintain the folder structure making it easy for a user to download the data package, extract, and point the container run to this location as the cesm_input_data location.
create_GSWP3.0.5d.v1_single_point_forcing_data.py.txt
config_fates.cfg.txt
And then running a case script like this one with the container would allow the user to use that input data locally on their machine.
create_ctsm-fates_1pt_case_custom_site.sh.txt
The text was updated successfully, but these errors were encountered: