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
2017-07.nc is expected there. Should that be in $wfe_dir/dta/geo/eclm/?
Is it to be generated by $wfe_dir/src/eCLM_atmforcing (this subrepo is our new repo)?
The file 2017-07.nc is indeed expected to be available in the data directory structure, typically under $wfe_dir/dta/geo/eclm/. In the standard workflow, this file would normally be generated through the pre-processing step, in particular via the eCLM_atmforcing submodule, which is responsible for producing the required atmospheric forcing data for eCLM.
However, to simplify the initial setup and lower the barrier for first-time users, a quick start configuration was provided by #27 . This quick start includes explicit instructions for downloading the required input data directly, bypassing the need to run the full pre-processing chain.
For a full production setup, the recommended approach remains to generate the forcing data using the pre-processing workflow.
Activity
mvhulten commentedon Mar 18, 2026
2017-07.ncis expected there. Should that be in$wfe_dir/dta/geo/eclm/?Is it to be generated by
$wfe_dir/src/eCLM_atmforcing(this subrepo is our new repo)?s-poll commentedon Apr 13, 2026
Thank you for raising this question.
The file 2017-07.nc is indeed expected to be available in the data directory structure, typically under
$wfe_dir/dta/geo/eclm/. In the standard workflow, this file would normally be generated through the pre-processing step, in particular via the eCLM_atmforcing submodule, which is responsible for producing the required atmospheric forcing data for eCLM.However, to simplify the initial setup and lower the barrier for first-time users, a quick start configuration was provided by #27 . This quick start includes explicit instructions for downloading the required input data directly, bypassing the need to run the full pre-processing chain.
For a full production setup, the recommended approach remains to generate the forcing data using the pre-processing workflow.
kvrigor commentedon Apr 16, 2026
tl;dr for those experiencing the same problem: