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

Drought deciduous trees and changing soil moisture initialization #668

Open
rosiealice opened this issue Jul 7, 2020 · 7 comments
Open

Comments

@rosiealice
Copy link
Contributor

rosiealice commented Jul 7, 2020

So, in my ongoing quest to make the DDTs perform non-ridiculously, I realized that the joint phenology/hydrology system is being fundamentally thrown off by the very dry initialization of soil moisture, which is set as VWC of 0.15 in the init_cold routine here:

https://github.com/ESCOMP/CTSM/blob/e33b4658f6c51f8d1cce4ed1986bc3dc28014c5d/src/biogeophys/WaterStateType.F90#L773

What happens after the initialization is that

  1. The soil is dry, and so the leaves come off and stay off for a long time
  2. when they come back on, they've lost so much carbon that they die off (of carbon starvation and then termination). 
  3. when the few survivors try to regrow, they can't pull the soil moisture down far enough to trigger the normal drought deciduous behaviour and get stuck in a perma-wet situation
  4. in the perma-wet situation, they are further penalized for there being no dry season.
  5. they also have extremely low GPP, LAI, biomass etc. 

In this way, most of the savanna areas have been dying in large semi-arid areas of my simulations.  e.g. 
https://github.com/rosiealice/global_pft_scripts/blob/master/analysis_scripts/droughtdec_init0.15.ipynb

Changing the initial soil moisture value to 0.85 massively improves things, as shown in:
here:https://github.com/rosiealice/global_pft_scripts/blob/master/analysis_scripts/droughtdec_initw.ipynb

 If you look at the last figure in these notebooks, of SMP and VWC across soil layers, you can see that in the 0.15 simulation, the system is still not at equilibrium well into the second year. For many hydrology applications that's fine of course, but for these DDT's with their carbon stores and their mortality thresholds, it really isn't. 

 If you look at the first plot (of LAI in each season) to illustrate the impact that changing soil moisture initialization has on the DDT dynamics!

So, my question is, slightly directed at @dlawrenncar and Sean Swenson (who isn't here, but i'll direct him to this later), is there a reason to not modify the initial soil moisture? I can imagine several (flooding, GRACE comparison, permafrost concerns, hydraulic redistribution etc.) Of course this change can go in with a 'use_fates' caveat, and I see it's already been done for cases with HYDRO, but is there any reason not to do this? I imagine that this might also be messing a little bit (but not as much, in the absence of mortality and with the magic of XSMR).

Anyway, with this change, everything makes a lot more sense, thankfully...

n.b. that in these notebooks for some reason the first year took forever to read in, and my newby python skills haven't managed to fix this yet. In general, reading in more than 2-3 years of these daily output files takes forever...

@rgknox
Copy link
Contributor

rgknox commented Jul 7, 2020

@rosiealice is part of the problem that FATES is too sensitive to the initial condition? If there is external seed rain, do the new recruits succeed when the drought timers start to trigger again?

@dlawrenncar
Copy link

@rosiealice I don't think that we have ever really explored the impact of soil water initialization. It does impact permafrost long term dynamics because the initial soil water state deep in the soil essentially gets frozen in until it thaws at some point in the distant future. In general, a higher value of initial soil moisture is possibly more realistic. I'm meeting with Sean tomorrow and I can ask him if he knows of any issues that we should be concerned about.

Do you need to go so such a high level. 0.85 is way above typical saturation levels since watsat tends to be around 0.3-0.4 for non-organic soils. I think this would mean that there would be a big water flux to the rivers on the first timestep as the soils kick out all the excess water. You might be able to get same results with something a bit smaller.

@rosiealice
Copy link
Contributor Author

OK cool. I'll try it with a smaller number. I asked Sean and he didn't think it would be problematic...

Also good point @rgknox. I think that would happen, but also givwn the counters get into some alternative states with soil which is this dry (in deep areas, it needs a lot of water to get back to equilibrium state. So I think I do need to change it...

@walkeranthonyp
Copy link

walkeranthonyp commented Jul 7, 2020 via email

@glemieux
Copy link
Contributor

Pinging @mpaiao on whether your updates in #801 will address this.

@mpaiao
Copy link
Contributor

mpaiao commented Nov 17, 2022

@glemieux I just applied the same assumption done for FATES-Hydro for any FATES simulation, actually following @rosiealice suggestion from this thread.

I think there was a small confusion in the thread, the value that Rosie suggested (0.85) referred to the value relative to saturation, not the absolute initial soil moisture (m3/m3), so the initial soil moisture is reasonable even for non-organic soils.

@glemieux glemieux linked a pull request Nov 17, 2022 that will close this issue
5 tasks
@glemieux glemieux moved this to ❕Todo in FATES issue board Nov 17, 2022
@glemieux glemieux moved this from ❕Todo to 🟢 In Progress in FATES issue board Nov 17, 2022
@rosiealice
Copy link
Contributor Author

I was very confused here until I realised how old this thread was! Hurray for GitHub having a better memory than me...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: 🟢 In Progress
Development

Successfully merging a pull request may close this issue.

6 participants