OpenStudio 1.0.0 - File Version Update Unhandled Exception
I just updated to OpenStudio 1.0.0 and when I try to open an existing .osm file which was saved in 1.0.0-pre, I receive this Unhandled Exception message.
"C:\Users\jenkins\git\OpenStudio\src\osversion\VersionTranslator.cpp@612: Unable to retrieve OpenStudio Version 3.0.0-rc1 IDD from the IddFactory.
@Patrick can you try this for me. Make a new model in the OpenStudio Application and save. Now make a copy of. your 1.0.0-pre OSM and open it with a text editor. Copy in the version object from the freshly made OSM into this file, then save and close it. Now Open that modified copy through the OpenStudio Application. Let me know if you still get that same error. If you do then send me the pre-modified file to openstudio@nrel.gov and we can take a look at it.
After copying and pasting the OS Version object from a new file it still did not open, but I got a different error:
Model with Version 3.0.0 IDD is not valid to draft strictness level.
The collection is INVALID at strictness level 'Draft', because of the errors: Field level data error of type DataType . Error is in an object of type 'OS:ShadowCalculation', named '', in field 1. Additional information about the error type: field-level data is of an incorrect type. Field level data error of type DataType . Error is in an object of type 'OS:ClimateZones', named '', i
@Patrick, try to remove the OS:ShadowCalculation object with a text editor and try again. You may have to repeat this a few times with different objects.
I discovered that I currently have EnergyPlus 8.9 running. It looks like it did not update to 9.3 when I installed OpenStudioApplication 1.0.0. I am going to manually update to E+ 9.3 and see if that resolves my issue.
The OpenStudio CLI, which is included with the OpenStudio Application includes EnergyPlus 9.3. It should be fine to have other versions of EnergyPlus on your computer. I'd be interested to have you make a new model with the final 1.0.0 application release, and then close and re-open that. I think it will be fine. I think the issue is that you have a model from a pre-release and there may have been model object changes that prevent it from opening in the final release.