Sam Currie's profile - activity

Ok, are the light definitions applied to space types? You might also check the eplusout.err file in case there are any c

Based on the units, looks like a lighting issue - you might check your luminaire definitions (maybe a divide by zero sit

@Aaron Boranian thanks for the additional links - I have not seen a post or documentation that explicitly states if the

Importance of Soil Properties in EPW Files When creating EPW files with historical files, are the soil properties in the

I'm implementing the revised ASHRAE (Tau) clear sky model and am trying to find a source for the beam and diffuse optical depths described in the engineering reference: https://www.energyplus.net/sites/defa...

The depths appear to be based on the Beer-Lambert law but I can't find any documentation on how the diffuse and beam are calculated in the ASHRAE material. The goal is to produce the solar radiation estimates for use in a EPW file.

Question: Can someone provide documentation for calculating beam/diffuse optical depths? Or is it just better to use the Zhang-Huang model?

The optical depth estimates in ASHRAE climatic data were calculated using a high performance clear sky radiation model c

The optical depth estimages in ASHRAE climatic data were calculated using a high performance clear sky radiation model c

That's a good point @Julien Marrec - My copy of fundamentals 2009 mentions ASHRAE RP-1453...I'll try and track that down

That's a good point @Julien - My copy of fundamentals 2009 mentions ASHRAE RP-1453...I'll try and track that down and po

@Gio I'm trying to calculate the optical depths; I have the ASHRAE design conditions data

Referring to the engineering reference for the sky temperature: https://www.energyplus.net/sites/default/files/docs/site

Optical depths for the ASHRAE Clear Sky Model I'm implementing the revised ASHRAE (Tau) clear sky model and am trying to

I'm curious if its necessary to recalculate the typical/extreme periods for historical weather data if the model is using a DDY file? Are these dates used in the E+ sizing methods?

The periods I'm referring to are located in the header rows of an EPW file: TYPICAL/EXTREME PERIODS,6,Summer - Week Nearest Max Temperature For Period,Extreme,6/22,6/28,Summer - Week Nearest Average Temperature For Period,Typical,6/ 8,6/14,Winter - Week Nearest Min Temperature For Period,Extreme,1/27,2/ 2,Winter - Week Nearest Average Temperature For Period,Typical,1/ 6,1/12,Autumn - Week Nearest Average Temperature For Period,Typical,10/13,10/19,Spring - Week Nearest Average Temperature For Period,Typical,4/26,5/ 2

I had a feeling that was the case; if you edit your answer to include that bit I will mark it as accepted, thanks!

Thanks, I'm really just wondering about how the TYPICAL/EXTREME PERIODS header gets used within an EPW file and if it ev

Are typical/extreme periods from EPW used if a DDY file is provided? I'm curious if its necessary to recalculate the typ

Are typical/extreme periods from EPW used if a DDY file is provided? I'm curious if its necessary to recalculate the typ

Using OpenStudio's ruby API:

Suppose I have defined an activity level schedule, activitySchedule, and then created a PeopleDefinition object person and a People object: people = OpenStudio::Model::People.new(person) and assigned the activity schedule to people.

How do I add people to a space as a load?

Bonus question: Is it more appropriate to create a single PeopleDefinition object with the number of people set to 1 and share it with each space that has the same occupancy, adjusting the number of people with the space's setNumberOfPeople method

OR

Should I create unique PeopleDefinition objects for every single space?

Thanks @macumber. How does one access the ScheduleDay that the rule constructs? In the method list for ScheduleRule I'm not seeing a straight forward way to do so; is it necessary to call children() and search for the ScheduleDay?

When creating a schedule via ruby scripts, I create a new ScheduleRuleset object ruleset , then create a ScheduleDay object scheduleDay and finally create the associated ScheduleRule as:

rule = OpenStudio::Model::ScheduleRule.new(ruleset, scheduleDay)

This works just fine but (as indicated in the documentation) the ScheduleDay object is cloned and the new object is associated with the rule. Practically this is fine and the ruleset is created as expected but it leaves these orphaned ScheduleDay objects in the OSM.

My question is, is there a (non-hacky) way to create the ScheduleRules without polluting the OSM with a bunch of unused ScheduleDay objects? Or alternatively, if I create the rule without the ScheduleDay and a new ScheduleDay object is created, how do I access it?