OS reverse translator does not retain the spectral data type of glazing

asked 2017-04-12 11:02:33 -0600

nigusse
181 ●1 ●7

updated 2017-04-13 11:47:39 -0600

I am trying to load E+ idf and translate it to OS model using C# binding. The glazing data type of the translated model glazing object 'OS:WindowMaterial:Glazing' comes out as 'spectral' instead of 'SpectralAverage'. The glazing data type is lost during translation. I am using Openstudio version 2.1.0.

Is there a method to reset the spectral data type of the glazing? Thanks.

edit retag flag offensive close merge delete

Comments

Here's a related question that might be helpful: https://unmethours.com/question/23474...

MatthewSteen ( 2017-04-12 21:37:43 -0600 )edit

Thank you Mathew. This is not exactly the same problem. Here is what I did:

(1) I loaded an E+ idf and reverse translated the E+ idf to OS model and saved the OS model to new OSM idf. The opticalDataType of glazing objects in E+ idf were SpectralAverage but in the OS idf it is translated to Spectral. The opticalDataType is lost during reverse translation.

nigusse ( 2017-04-13 09:32:38 -0600 )edit

below is the C# binding code I used to load and reverse translate the E+ idf:

OpenStudio.OptionalIdfFile oIdfFile = OpenStudio.IdfFile.load( idfPath, new OpenStudio.IddFileType( "EnergyPlus" ) );
OpenStudio.IdfFile idfFile = oIdfFile.get();
// reverse translate the idf file to an OpenStudio model
OpenStudio.EnergyPlusReverseTranslator translator = new OpenStudio.EnergyPlusReverseTranslator();
OpenStudio.Model model = translator.translateWorkspace( new OpenStudio.Workspace( idfFile ) );

nigusse ( 2017-04-13 09:38:26 -0600 )edit

Just go to the material is the GUI and change it back to SpectralAverage. The reverse translator isn't fully featured and not a OS development priority.

Adam Hilton ( 2017-04-13 10:53:27 -0600 )edit

Is your IDF a complete model or just objects from LBNL WINDOW or maybe another use case? If the former, you'll also completely lose the HVAC systems in reverse translation. Any reason not to simply work on the IDF (workspace) directly with the C# bindings?

MatthewSteen ( 2017-04-13 20:09:00 -0600 )edit

see more comments