-
Notifications
You must be signed in to change notification settings - Fork 159
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
Running GCAM core with broken out region #400
Comments
I've seen this error happen a few times, not sure why it's happening here though. Basically what it means is that there's some technology/NonCO2 that's being created, but there's no
` |
Interesting. That all makes sense. On commenting out the file emission_factor_controls.xml from the configuration file, the "could not delete node..." errors go away, and the model still fails in Period 0. However, it now fails due to having "No emissions coefficient set for CH4 in USA in period 0." |
It's hard to say, but just in order to make sure everything in the XML files is consistent with all of the input files and code, I'd recommend running |
Alright, we've failed in the source("data-raw/generate_package_data.R") command with ~50 chunks to go. Argh. [1] "module_gcamusa_L2261.regional_biomass" |
Haha OK that's a bug that we fixed shortly after the release, but it still isn't in a release version or the Github master branch. Instead I've just been recommending for people to retrieve it from my forked repo on github, as described here: #393 (comment) |
Sorry, I must have only copied over the gcam_limits not the gcamusa_limits file when I originally rolled that bug fix in. Confirming that generate_package_data does run to completion now. Driver(), however, did not complete its run and got stuck on modules in aglu, such as module_aglu_L152.ag_GTAP_R_C_GLU_irr. It simply freezes or gets caught in a loop and R crashes. Unsure why. Is this something worth trying to debug? If useful, we are using a bug fix from gcamdata (#f6d240e8, May 31 2023) that includes files in aglu adapted to v7 that are in the vicinity of the aglu freezes. (fix explained here: JGCRI/gcamdata#1236 (comment)) Was a permanent fix implemented such that we should get rid of this patch? |
I don't know; if it was able to run generate_package_data.R then that means all of the code is working, but I guess when it's saving outputs etc. it runs out of memory? If you aren't already, I'd recommend using |
That did it! Good call. Unfortunately, we've still failed while running in period 0. No emissions coefficient set for CH4 in USA in period 0. Unsure if related, Robbie pointed out that configuration.xml uses the same tag for multiple non-CO2 gas files. e.g.:
Other than that, not sure of next steps. Sorry to be less useful here |
As noted in a prior comment in this thread, this error message just means that a nonCO2 object was created but not assigned an emissions coefficient or an input-emissions quantity in the base year(s). Searching out internal forum I see that @jayfuhrman had this issue a few years ago, so Jay feel free to weigh in if you have any notes about the source of the issue. In his case the crash was also preceded by a warning about NA values; do you have that too? It would be in the main_log immediately after the XML file that causes the problem is read in, so it's easy to identify the source of the problem if you have that issue. |
#1 was a good test -- the calibration periods solved and the model failed instead in 2020 with a similar message. No emissions coefficient set for SF6 in USA in period 5 |
Hi GCAM team,
I've broken the UK out of the EU-15 region but am encountering an issue when the model runs. The scenario components update successfully to reference the new XMLs, they parse successfully, then on running a new scenario, I get 54 error messages reading "Could not delete node gdp-control as it does not exist." The model then begins a run but fails due to "No emissions coefficient set for SO2_1 in USA period 0. I'm happy to attach any relevant XMLs here, but have not debugged at this stage before, and am not sure where to start.
Thanks for your guidance.
The text was updated successfully, but these errors were encountered: