search

JGCRI / gcam-core

GCAM -- The Global Change Analysis Model
http://jgcri.github.io/gcam-doc/
Other
273 stars 162 forks source link

Fail to pull out XML database #445

Open 837288251 opened 1 month ago

837288251 commented 1 month ago

When I used configuration.xml to pharse my database, it stoped at "Deleting node: minicam-energy-input". I have tried many way but still don't know how and where to find the problems. Here's my log file: main_log.txt

Thank you so much!

pkyle commented 1 month ago

The last message printed to the log has nothing to do with the error that caused the crash. Unfortunately there are some errors in XML files read to GCAM that cause the model to crash, but do not produce an explanatory message. For instance, if a subsector is created, but it doesn't have any technologies within it, I think that may cause a silent model crash. The way I've always debugged these is, on a Mac, running the model from Xcode, select Product -> Scheme -> Edit scheme -> Run -> Info-> check box for “debug executable” Then when you run the model, and it crashes, that will launch a debugger that can be used to isolate what was happening when the crash occurred.

837288251 commented 1 month ago

The last message printed to the log has nothing to do with the error that caused the crash. Unfortunately there are some errors in XML files read to GCAM that cause the model to crash, but do not produce an explanatory message. For instance, if a subsector is created, but it doesn't have any technologies within it, I think that may cause a silent model crash. The way I've always debugged these is, on a Mac, running the model from Xcode, select Product -> Scheme -> Edit scheme -> Run -> Info-> check box for “debug executable” Then when you run the model, and it crashes, that will launch a debugger that can be used to isolate what was happening when the crash occurred.

Thank you for your answer^_^ Although I used the Window System, I managed to use the Code Comments line by line in Configuration.xml and finally located the wrong xml. Now it runs smoothly~