idaholab / HERON

Holistic Energy Resource Optimization Network (HERON) is a modeling toolset and plugin for RAVEN to accelerate stochastic technoeconomic assessment of the economic viability of various grid-energy system configurations, especially with application to electrical grids and integrated energy systems (IES).
Apache License 2.0
24 stars 38 forks source link

[DEFECT] Running debug mode with csv file #365

Open wenchichenginl opened 4 months ago

wenchichenginl commented 4 months ago

Defect Description

Describe the defect

What did you expect to see happen?

I would expect the run will be successful when switching from sweep mode to debug mode when the electricity price is in CSV format.

What did you see instead?

The run fails.

Do you have a suggested fix for the development team?

N/A.

Describe how to Reproduce Steps to reproduce the behavior:

  1. Use CSV file for debug mode where electricity price date have more than 1 year
  2. Change from Sweep mode to debug mode and run the codes

Screenshots and Input Files Please attach the input file(s) that generate this error. The simpler the input, the faster we can find the issue.

There were 2 warnings during the simulation run: (1 time) <class 'DeprecationWarning'> "variables" node inputted but has been deprecated! Please list variables in the "inputs" and "outputs" nodes instead. (1 time) There were 1 failed runs! Run with verbosity = debug for more details.

Traceback (most recent call last): File "C:\Users\CHENW\projects\raven\raven_framework.py", line 25, in sys.exit(main(True)) File "C:\Users\CHENW\projects\raven\ravenframework\Driver.py", line 207, in main raven() File "C:\Users\CHENW\projects\raven\ravenframework\Driver.py", line 160, in raven simulation.run() File "C:\Users\CHENW\projects\raven\ravenframework\Simulation.py", line 901, in run self.executeStep(stepInputDict, stepInstance) File "C:\Users\CHENW\projects\raven\ravenframework\Simulation.py", line 834, in executeStep stepInstance.takeAstep(stepInputDict) File "C:\Users\CHENW\projects\raven\ravenframework\Steps\Step.py", line 317, in takeAstep self._localTakeAstepRun(inDictionary) File "C:\Users\CHENW\projects\raven\ravenframework\Steps\MultiRun.py", line 269, in _localTakeAstepRun sampler.finalizeSampler(self.failedRuns) File "C:\Users\CHENW\projects\raven\ravenframework\Samplers\Sampler.py", line 1119, in finalizeSampler self.handleFailedRuns(failedRuns) File "C:\Users\CHENW\projects\raven\ravenframework\Samplers\Sampler.py", line 1141, in handleFailedRuns self._localHandleFailedRuns(failedRuns) File "C:\Users\CHENW\projects\raven\ravenframework\Samplers\Sampler.py", line 1153, in _localHandleFailedRuns self.raiseAnError(IOError, 'There were failed runs; aborting RAVEN.') File "C:\Users\CHENW\projects\raven\ravenframework\BaseClasses\MessageUser.py", line 77, in raiseAnError self.messageHandler.error(self, etype, msg, str(tag), verbosity, color) File "C:\Users\CHENW\projects\raven\ravenframework\MessageHandler.py", line 235, in error raise etype(message) OSError: There were failed runs; aborting RAVEN.

Platform (please complete the following information):


For Change Control Board: Issue Review

This review should occur before any development is performed as a response to this issue.


For Change Control Board: Issue Closure

This review should occur when the issue is imminently going to be closed.

dylanjm commented 3 months ago

@wenchichenginl Please upload your reproducible example along with the failing out~inner file.