nigusse's profile - activity

The SetpointManager:WarmestTemperatureFlow sets the minimum flow and modulates (increases) until it meets the cooling lo

Two issues drive the problem: (1) differences in heating coil design capacity and available capacity and (2) air termina

Thanks @Denis Bourgeois for your feedback. I will experiment your suggestion. Certainly, there are reasons to have diffe

Thanks @Denis-Bourgeois for your feedback. I will experiment your suggestion. Certainly, there are reasons to have diffe

Thanks @denis-bourgeois for your feedback. I will experiment your suggestion. Certainly, there are reasons to have diffe

Thanks @denis-bourgeois for your feedback. I will experiment you suggestion. Certainly, there are reasons to have differ

Thanks @alebar. Infact, I did change their order but did not help me in my previous test. I will test if the order in th

Thanks @Denis for your feedback. I will experiment you suggestion. Certainly, there are reasons to have different versio

Thanks @Denis-Bourgeois for your feedback. I will experiment you suggestion. Certainly, there are reasons to have differ

Finally, I was able to build the latest openstudio-standards using Ruby version 2.7.2p137 (2020-10-01 revision 5445e0435

Openstudio-standards build problem Openstudio-standards build fails with the "rake aborted! LoadError: 126: The specifie

Openstudio-standards build problem Openstudio-standards build fails with the "rake aborted! LoadError: 126: The specifie

Openstudio-standards build problem Openstudio-standards build fails with the "rake aborted! LoadError: 126: The specifie

I also checked the UnitarySystem object code. This object either uses the air flow ratio specified in the UnitarySystemP

I am not advocating for not to generate an UnitarySystemPerformance:Multispeed object if the current issue is fixed. But

I also checked the UnitarySystem object code. This object either uses the air flow ratio specified in the UnitarySystemP

The main reason I posted this question was I created the OSM input file programmatically using openstudio V3.4 and Opens

The main reason I posted this question was I created the openstudio input file programmatically using V3.4 and Openstudi

The main reason I posted this question was I created the openstudio input file programmatically using V3.4 and Openstudi

My understanding of the variable speed and multi-speed coil objects is that they are very similar except they were imple

Is the UnitarySystemPerformance:Multispeed object supported for use with variable speed DX coils I created a Variable Sp

Is the UnitarySystemPerformance:Multispeed object supported for use with variable speed DX coils I created a Variable Sp

Running OS using local build Openstudio-standards I want Openstudio (OS) to use local built and installed Openstudio-sta

@shorowit Thanks. I see detailed explanation in documentation and is very helpful.

Running OS using local build Openstudio-standards I want to Openstudio (OS) to use local built and installed Openstudio-

Running OS using local build Openstudio-standards I want to Openstudio (OS) to use local built and installed Openstudio-

Thanks. Posted new OpenStudio issue #4433

Thanks. Posted new issue #4433

I could not open the new OSM file created in OpenStudio because of missing Version object and I confirmed this by text c

I could not open the new OSM file created in OpenStudio because of missing Version object and I confirmed this by text c

The OS model was created as follows: private IdfObjectVector myNewObjVec = new IdfObjectVector(); private Model osNewMo

The OS model was created as follows: private IdfObjectVector myNewObjVec = new IdfObjectVector(); private Model osNewMo

New instance of an OS model is created as follows: private IdfObjectVector myNewObjVec = new IdfObjectVector();

Missing OS:Version IdfObject from Cloned OS Model Loaded OSM file using CSharp binding (V3.2.0), read each of the IdfObj

There are two defects identified in ASHWAT that are being addressed. #7367 being one of them. Your test case has the fie

No, I started from existing E+ IDF for the building input and was trying to add the HVAC system using C# binding.You are right, I could have worked directly on C# binding but adding building geometry with several zones and construction is a lot of work. I was considering the minimum effort option.

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 ) );

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.

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.

I was reviewing the DX heating curve inputs of the PTHP model in OSM and found out that the X independent variable minimum and maximum values for capacity are incorrect. I see 0 and 1.0. I expect to see a range that is typical in heated spaces.

OS:Curve:Biquadratic 11, !- Name ... 0, !- Minimum Value of x 1, !- Maximum Value of x 0, !- Minimum Value of y 1; !- Maximum Value of y

Resolved. I removed the Unit Type input field from OS:ScheduleTypeLimits object when creating the schedules for People, Lights and ElectricEquipment objects.

Why not we use key input value of Fraction for this input field when creating lighting, people, and electric equipment schedules? I was expecting the Dimensionless key input value to work with this objects but it did not. This schedule values are dimensionless multipliers of the peak value. Just a thought!