Openstudio version compatible with NREL fault measure
Hello everyone, I am a beginner in OpenStudio and EnergyPlus. I am using OpenStudio 1.3.0 / SDK 3.3.0. I downloaded the "OpenStudio-faults-measures" files from NREL Github. The simulation always fails. Thanks for answering
That repo contains a bunch of measures. I picked out a few that I'd consider applicable to a v3.6.1 model I recently worked on, and they all ran without warnings or errors (e.g. checking the generated out.osw). I didn't pay attention to results - simply whether they could run against a more recent OpenStudio version. Which one(s) specifically were you testing?
Hello Denis Thank you for your response. I tested the following measures one by one: ExcessiveInfiltration, CondenserFooling and CondenserFanDegradation with an AC split system.
@angelson: Reverting to an older OpenStudio version (1.4.0/3.4.0). Can successfully run both the ExcessiveInfiltration (OpenStudio) Measure and CondenserFanDegradation (EnergyPlus) measure. Both measure outputs are informative and simulation results are as expected. Unsuccessful with the CondenserFouling (EnergyPlus) measure (initial run), but I may not be setting it up correctly - 32x user inputs!
Edit your initial answer and share (for each failed run):
... set aside CondenserFouling for now.
In run.log:[20:51:41.999189 ERROR] :/ruby/2.7.0/gems/openstudio-workflow-2.3.1/lib/openstudio/workflow/util/measure.rb failed with message cannot load such file -- C:/Users/ANDRIA~1/AppData/Local/Temp/osmodel-1739294197-0/resources/measures/ExcessiveInfiltration/resources/faultimplementation_EI in eval:132:in
require' eval:132:inrequire' Yet, the measure "faultimplementation_EI" is indeed in resources.Then, in measure.xml: <error>cannot load such file -- C:/Users/ANDRIANIRINA/OpenStudio/Measures/ExcessiveInfiltration/resources/faultimplementation_EI</error>
Freshly installed App v1.3.0 (MacOS, x86): getting the same (successful) outcomes as with v1.4.0. You're clearly on Windows - hopefully some other Windows user can test the measures with 1.3.0/3.3.0. Next step would be to share your .osm file (e.g. Google Drive). You can always shorten the .osm path/file or try the suggested 5-step solution here - e.g. workflow paths may be too long or corrupted?