Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Critical Soil Moisture #44

Open
10 tasks
nocollier opened this issue May 22, 2023 · 0 comments
Open
10 tasks

Add Critical Soil Moisture #44

nocollier opened this issue May 22, 2023 · 0 comments

Comments

@nocollier
Copy link
Collaborator

nocollier commented May 22, 2023

As part of a push to develop ILAMBv3, I had implemented the critical soil moisture (CSM) metric. See code and results. We would like to port it to current ILAMB. The current version just implemented the calculations and thus is more of a model characteristic that is compared to others. Ideally we would like to compare this to reference data. Paul's cheatsheet has a good discussion of what kinds of observations could be used.

To do:

  • Backport the v3 code to the v2.6
  • Referenced paper was over Europe and used just summer, what do we do globally?
  • One possibility is to use Fluxnet data, there are options for which variables we use.
  • Fluxnet: Choose an energy variable TA (air temperature) or TS (soil temperature), the sheet suggests 'skin temperature', I am using ts from the models.
  • Fluxnet: Choose a water variable SWC (soil water content). I am not sure how deep this measurement is made, I couldn't find a reference. In the calculation I use the top 10 [cm] of soil.
  • Fluxnet: Choose a vegetation variable GPP? The sheet suggests ET, but Fluxnet doesn't provide this variable. Could another serve? Or should we grab ET at the sites from GLEAM? Ultimately I understand that we are only analyzing how the anomalies of each variable correlate.
  • Add a score, consider a simple S = exp( - (CSM_ref - CSM_mod) / CSM_ref) )
  • Consider a combination of gridded products?
  • How do we organize this in the ILAMB configure file? Perhaps a new top level section called 'Coupling'?
  • This index is valid for daily and monthly data. We need the model object to be able to distinguish between the two and an API for extractTimeSeries() to specify which kind of data is being requested. Move the watersheds work into ModelResult.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant