Denis Bourgeois's profile - activity

The linked file (Google Drive) requires authorization to access (you'd preferably want to make it public). OpenStudio's

The linked file (Google Drive) requires authorization to access (you'd preferably want to make it public). OpenStudio's

The linked file (Google Drive) requires authorization to access (you'd preferably want to make it public). OpenStudio's

The linked file (Google Drive) requires authorization to access (you'd preferably want to make it public). OpenStudio's

The linked file (Google Drive) requires authorization to access (you'd preferably want to make it public). OpenStudio's

The linked file (Google Drive) requires authorization to access (you'd preferably want to make it public). OpenStudio's

"I am not sure how to apply the airboundary/airwall construction to the ground facing floors without triggering a sever

Are you certain you linked the right file? I'm noticing that "Face 1501" is (also) a wall - not a floor. It does not hav

Are you certain you linked the right file? I'm noticing that "Face 1501" is (also) a wall - not a floor. It does not hav

Hi @Mike117. Indeed, the original model (which I linked, as an example) does not have that issue: "FACE 1501" is a wall

Hi @Mike117. Indeed, the original model (which I linked, as an example) does not have that issue: "FACE 1501" is a wall

@Mike117, please provide a link to the generated OSM or IDF (like this one). Or at a minimum, please provide a relevant

Heating and cooling design supply air temperatures are not room setpoint temperatures (e.g. for thermal comfort). They a

Heating and cooling design supply air temperatures are not room setpoint temperatures (e.g. for thermal comfort). They a

Heating and cooling design supply air temperatures are not room setpoint temperatures (e.g. for thermal comfort). They a

Heating and cooling design supply air temperatures are not room setpoint temperatures (e.g. for thermal comfort). They a

Yes, you can hard-assign a construction to a surface (or rather both interzone surfaces) with the OpenStudio Application

@Mike117, yes: providing the model .osm file helps. Look up surfaces (with conflicting constructions) in the run/in.idf

Sorry, can't help you with fixing what look like to be dozens (potentially hundreds) of surface conflicts with Floorspac

Sorry, can't help you with fixing what look like to be dozens (potentially hundreds) of surface conflicts with Floorspac

Sorry, can't help you with fixing what look like to be dozens (potentially hundreds) of surface conflicts with Floorspac

Based on another recent post, are you also referring to FloorspaceJS? If so, it would be preferable to have "FloorspaceJ

RoofVegetation is available in the OpenStudio Application: Constructions tab ... Materials sub-tab ... ... Roof Vegeta

Depends on climate, building orientation/geometry, fenestration, whether spaces are internal vs external load dominated,

RoofVegetation is available in the OpenStudio Application: Constructions tab Materials sub-tab Roof Vegetation Materia

Often, yes ... depends on context (e.g. office vs warehouse). Certainly less comfortable than 32°C (re ASHRAE 90.1 requi

@Zakaria, based on the layout you shared, each perimeter zone should have 1x wall (adjacent to the "Walk-in Zone") refer

I don't have OpenStudio v1.14.0 and/or compatible SketchUp versions, but could open the shared OSM file with: OpenStud

Sorry for the delay - for whatever reason, I'm recently getting UMH notifications (of follow-up responses/comments) like

Agree. It's not 100% clear from the original question whether @Zakaria intentionally wants dissimilar materials between

@Zakaria, interzone walls must indeed share the same vertices (in reverse order from each other), and their construction

Hi Margot. Something to consider: the "Heat Gain Rate" outputs are tallied "when the total heat flow is positive" (i.e.

@harnimic, when you open both your original OSM file and the exported IDF file with a text editor, are you noting that s

Can't help you with Revit, but the E+ severe error message is clear: Construction:AirBoundary can only be referenced by

@santiago.avila@in2engineering.com, hard to say without knowing more about the technical requirements. If it's code in I

(not a definitive answer - just poking around) I don't have DesignBuilder, but ran both IDFs (noA == "no awning", vs A

@Daffa, for whatever reason your follow-up question didn't pop up (when I re-logged to UMH) - (?). In any case, I suspec

Can reproduce the failure: "Could not find prototype inputs for DOERefPre1980HighriseApartment ...", linked to OpenStudi

Can reproduce the failure: "Could not find prototype inputs for DOERefPre1980HighriseApartment ...", linked to OpenStudi

Bonjour Margot. It would be helpful if you shared the 2 (or 3) IDF files: no awning translucent awning opaque awning (

Ah! Good to know!

(just guessing here - link to idf?) 90.1 has almost always had 4 above-grade wall categories/requirements (e.g. "mass",

(Just guessing here.). 90.1 has almost always had 4 above-grade wall categories/requirements (e.g. "mass", "steel-framed

Similar issue reported here (i.e. mismatch between schedule intervals and simulation timestep) - similar fix (i.e. adjus

(not a complete answer, as the related literature is quite abundant). When it comes to "extreme" design conditions, you

Similar issue reported here (i.e. mismatch between schedule intervals and simulation timestep) - similar fix (i.e. adjus

Hi @paula. This is what I think is happening. First, the generated .shd report is confirming that all your zones are co