Bug 560122 - Logger failing to write log file for generated model (nCoV) running Global Simulation
Summary: Logger failing to write log file for generated model (nCoV) running Global Si...
Status: ASSIGNED
Alias: None
Product: STEM
Classification: Technology
Component: Simulation (show other bugs)
Version: unspecified   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: 2.0.0   Edit
Assignee: James Kaufman CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-02-13 13:49 EST by James Kaufman CLA
Modified: 2020-02-13 18:30 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description James Kaufman CLA 2020-02-13 13:49:01 EST
Reported by Aldo Crossa who wrote:
I'm trying to run the new nCoV scenario on Windows 10 machine that is behind a firewall. I need to generate logs to analyze after running the simulations.

Following the How-To Guide, I created the new Logger and dragged it into the scenario. It seems to add the file to the scenario, but I also get an error that says "Unhandled event loop exception". I can still run a whole simulation cycle (140 days) with the time series and maps on display, but no files are created under "Recorded Simulations." Also, when I look at "Active Logger" it does not appear on the list. Any suggestions on why this would be the case? I suspect that it has to do with the firewall but I don't know (I'm new to STEM).


Could be the generated model or could be the size of the global scenario. Investigating now.
Comment 1 James Kaufman CLA 2020-02-13 13:51:00 EST
assigning bug
Comment 2 James Kaufman CLA 2020-02-13 18:29:07 EST
After further investigation, this is not a defect in the logger. Logging a global scenario is causing a memory error (out of heap space). Increasing heap to 8G is not enough for a global scenario so logging would really require running on a larger server. Will keep this bug open as we explore alternatives.