-
Notifications
You must be signed in to change notification settings - Fork 13
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
_down_select_var: remove_recalculated_sectors() deletes all gases that are not specified by sector #12
Comments
Hey @jkikstra - in its current implementation, both history and model values must have the exact same variable name. So if you have, for example:
this will fail. For sure, the error message here should be better. Can you make a separate issue to that effect? We could, for example, check the data before running to see if there are no values in either dataset matching the expected prefix/suffix, for example. But in the near term, can you try this replacing |
Note that in the real fix, IMHO, is to get rid of the prefix/suffix stuff. This came from the original variable namings for CMIP6. |
@gidden: sure, I'll make a new isssue about dealing with prefix/suffix, specifying the two options you gave ( a. getting rid of it [or at least making aneris more flexible in dealing with it], b. adding a checking routine and giving a clearer error message). downselecting - empty model |
Ok - I'll try to look at this tonight.
…On Mon, Nov 4, 2019 at 10:44 AM jkikstra ***@***.***> wrote:
@gidden <https://github.com/gidden>: sure, I'll make a new isssue about
dealing with prefix/suffix, specifying the two options you gave ( a.
getting rid of it [or at least making aneris more flexible in dealing with
it], b. adding a checking routine and giving a clearer error message).
*downselecting - empty model*
As for your other point, I had already tried to do that; see the second
error message in my message. *With matching prefix and suffix*, I get a
RuntimeError.
It indicates that 'Model is empty after downselecting regional values'.
The model was fully cleared by the line model =
utils.remove_recalculated_sectors(model, prefix, suffix).
I now realise that this was caused by aneris deleting all
summed/aggregated values for each gas that can contain of multiple sectors,
while I only had aggregated values in my dummy data set.
For the current effort, this behaviour should probably be changed, do you
agree?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#12?email_source=notifications&email_token=AAKUAEJAWRGUCPUNSATOB3LQR7VHTA5CNFSM4JHNLNN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC6VRZY#issuecomment-549279975>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAKUAEKIAGZT33HV7Z23WJTQR7VHTANCNFSM4JHNLNNQ>
.
|
@jkikstra would you be able to write a small unit test that fails that highlights the aggregate gas total issue? If so, then I can directly write a patch that satisfies the test. |
When replicating the Getting Started Tutorial on my pc, everything works as expected.
See this folder for the files used, if you'd like to reproduce.
Now, with the same script, but different minimal input data, aneris seems to break at
_downselect_var()
.To reproduce, use the files in this folder.
When history data has suffix
|History
with model data suffix being|Unharmonized
, I get the error:--> see #14 for further specification of the prefix/suffix issue addressed above. Below, in this thread (#14) we focus further on down_select_var() behaviour wrt aggregates.
When history data has suffix
|Unharmonized
, to more closely mimic the Getting Started Tutorial (with model data suffix being|Unharmonized
), I get:The text was updated successfully, but these errors were encountered: