Closed yingli-NREL closed 1 week ago
Discussing in the development meeting:
For successfully finished job. It's pretty common that Trimming buildstock.csv takes around 8-10 minutes (14 from 21 jobs).
For successfully finished job. It's pretty common that Trimming buildstock.csv takes around 8-10 minutes (14 from 21 jobs).
Yeah, that shouldn't take that long. Something weird is going on there.
This might be fixed in #438.
This is most likely related to series of issue we dealt with in Kestrel before the latest system time. Closing this for now.
Describe the bug When running ResStock in Kestrel, I got some failed jobs for the time limit error. A few weeks ago, just a few jobs (around 5/50) failed. But this week, this problem becomes more serious. All 3 jobs, or 2 of 3 jobs failed. The error message in the
job.out-*
, isFor the job that successfully finished, it even took 10 min to finish the run for some jobs.
Platform:
Workaround method Increase the minutes_per_sim to a larger value. For example, I use minutes_per_sim=6 for a simulation with 600 models. If only a few jobs failed, rerun the failed jobs. https://buildstockbatch.readthedocs.io/en/stable/run_sims.html#re-running-failed-array-jobs