KeyError('SIMULATION_CONFIG_FILE',)
dlg0 opened this issue · 7 comments
@ORNL-Fusion/ips-support-team
I'm now trying to use the Genray driver that @parkjm developed in place of another. My simulation is in
/project/projectdirs/atom/users/greendl1/diem_tsc_error4
and is failing with the following error ...
greendl1@edison02:/project/projectdirs/atom/users/greendl1/diem_tsc_error4> cat this.log
2015-05-07 08:45:17,622 FRAMEWORK WARNING RM: listOfNodes = [('5764', '24'), ('5765', '24'), ('5766', '24'), ('5770', '24'), ('5772', '24'), ('5773', '24'), ('5776', '24'), ('5777', '24'), ('5778', '24'), ('5779', '24'), ('5780', '24'), ('5781', '24'), ('5783', '24'), ('5784', '24'), ('5785', '24')]
2015-05-07 08:45:17,623 FRAMEWORK WARNING RM: max_ppn = 24
2015-05-07 08:45:17,623 FRAMEWORK WARNING RM: User set accurateNodes to False
2015-05-07 08:45:17,625 FRAMEWORK WARNING Using user set procs per node: 24
2015-05-07 08:45:17,625 FRAMEWORK WARNING RM: 15 nodes and 24 processors per node
2015-05-07 08:47:01,355 FRAMEWORK ERROR received a failure message from component ss31615_3@generic_driver@2 : (KeyError('SIMULATION_CONFIG_FILE',),)
Tips?
This is an actual bug, something that was in the ORNL version of the framework and has not been migrated over to SF. Working on it.
OK, thanks.
Any idea why it didn't show up until I swapped in JM's genray component wrapper?
I think it's only used by the monitor component, so when it got called it bombed
Yeah, I'd tracked it down to the monitor_comp.py. I'll just disable the monitor until you push the fix. Although I was using the monitor component before swapping in the new genray component wrapper and I thought it was working then.
Not likely. If you were using the SF version, it sould have to have bombed whenever it tried to do anything meaningful
The fix has been pushed,
I've updated to the latest IPS version. Thanks.