-
Notifications
You must be signed in to change notification settings - Fork 45
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
Interpolation behavior #643
Comments
New behaviorIn b6cf6cb we change things so that LUC, FFI, and DACCS are retrieved from their respective time series only once, at the beginning of the timestep in
👍 This also reduces the code size, which is a nice bonus. |
Remove old `ffi()`, etc. functions; see #643
I am so enamored of this LUC pulse test — it's a stringent test of model behavior — that adding it as a permanent test. |
@bpbond OMG THIS EXPLAINS SO MUCH. It never made sense to me that Hector was regrowing more carbon than it lost in my pulse experiments, because that isn't how returning to equilibrium should work. But this totally explains it!! So glad you figured it out and fixed it! |
Also, that is SO satisfying to see vegetation just drop to a new equilibrium. |
Remove old `ffi()`, etc. functions; see #643
* Set current LUC, FFI, DACCS once at beginning of timestep * Remove old `ffi()`, etc. functions; see #643 * Disallow interpolation of emissions/uptake time series * Add LUC pulse test (disabling post-pulse test) * Update 1745-1749 constraints to non-zero values * Re-enable old-new test (and rename for consistency)
Current behavior
Hector time series (input data that are time-variant) can be marked as interpolation allowed or not allowed. The land-use emissions time series allows interpolation, because if the solver stops in 1800.5, we want it to 'see' an annualized LUC value that's halfway between that of 1800 and 1801.
But for a single-year pulse test, as in @dawnlwoodard 's in #639 , this produces very undesirable behavior:
Whoops! When the solver hit 1800, the land emits 10 Pg C of LUC emissions, which is what we wanted...but then another 5 (halfway through the year, so a value halfway between 10 and 0) gets debited in 1800.5 and another 2.5 in 1800.75.
We've ended up with a total LUC pulse of 17.5 when the input files specified only 10.
The text was updated successfully, but these errors were encountered: