Question-and-Answer Resource for the Building Energy Modeling Community
Get started with the Help page
Ask Your Question

mit011's profile - activity

2015-04-14 22:10:55 -0500 received badge  Editor (source)
2015-04-14 22:09:00 -0500 answered a question wrong ceiling and floors when exporting revit into sketchup

I am encountering the exact same problem and trying to solve it as well. I think I was able to find a pattern/solution by combining my observations with yours!

I've made several trials to test this issue and it seems that this Sketchup floor/ceiling error does not occur when spaces in Revit are created from the top floor to the bottom floor. Since you are encountering this error, I will guess that your 10th floor spaces were created before your 11th floor spaces. In other words, it seems that Sketchup floors belong to spaces that were created first within Revit and these spaces need to be created from top down. The reversed ceiling surfaces would then be assigned to spaces created 2nd. But don't worry! You will not have to delete spaces and re-create them in the correct order. You can write a script to change this within the GBXML, see below:

1) I noticed that the <surface id=""> Polyloop CartesianPoint order for ceilings are listed in CCW order while floors are listed in CW order. Surfaces will switch types if you simply reverse the order of your cartesian (not coordinate) points.

BUT, I just found an easier way to fix this due to your observations on how the spaces are referenced within the name (thanks! :) it was crucial to how I found this solution)

2) You noticed that the 10th floor space (181) was referenced before the 11th floor space (196). As mentioned above, this is incorrect - the 11th floor space should be referenced first because Revit likes top spaces to be named first for some reason. All you have to is change the order of the <adjacentspaceid>'s. There will be no need to change teh cartesianpoint order. Your code should look like below, referencing the top space before the bottom.

    <AdjacentSpaceId spaceIdRef="sp-196-11th">
    </AdjacentSpaceId>
    <AdjacentSpaceId spaceIdRef="sp-181-10th">
    </AdjacentSpaceId>

You can write a code for this if you have a pattern in your space naming (eg. sp-160 to sp-181 is on the 10th floor sp-182 to sp-200 is on the 11th floor). I named my floors 1xxx for 1st floor spaces, 2xxx for 2nd floor spaces, etc., so it was easy for a code that reversed the AdjacentSpaceId's when the first referenced space was a lower number than the 2nd.

2015-04-14 21:11:25 -0500 commented answer Zone floor area is zero. Floor surfaces not recognized

Yes, this is the exact same error I am encountering. His/her explanation is helpful, thanks! I just posted a solution on that page

2015-04-14 07:00:16 -0500 received badge  Teacher (source)
2015-04-14 00:51:01 -0500 answered a question Zone floor area is zero. Floor surfaces not recognized

Wanted to give an update on my new findings. Upon various trials and closer inspection of the gbxml, I've noticed that the floor/ceiling surface type errors are affected by 1) space order naming in Revit and 2) Cartesianpoint order in GBXML.

1) If spaces are named from the top floor down (2nd floor spaces named before 1st floor spaces), floor and ceiling surface types should be accurately assigned. Spaces named from bottom up (1st floor spaces named before 2nd floor spaces) will encounter this error. You can see the naming sequence by creating a space schedule in Revit.

2) In GBXML's "surface id">"PlanarGeometry">"PolyLoop" section, the <cartesianpoint> order for ceilings are listed in a counter-clockwise fashion. Floor surfaces have CartesianPoint's listed in a counter-clockwise fashion. You can change one surface type to the other by switching the order of these coordinate points.

In my model, I jump from naming spaces from floor to floor (1st>4th>2nd>1st, etc). The naming sequence is more complicated so some floors are listed as ceilings while other floors on the same level are listed as ceilings. I have not been able to figure out a pattern, thus unable to write a script that will yield perfect surface type assignments. I can obviously manually switch the surfaces using the Openstudio Inspector but any change in my revit model will make this Sketchup file unusable, which is why I am trying to find a pattern in order to write scripts.

2015-03-17 23:59:28 -0500 commented answer Zone floor area is zero. Floor surfaces not recognized

I see the difference between the two xmls now. The PlanarGeometry of ceiling surface id's have coordinates listed CCW. InteriorFloors have coordinates listed CW. Simply changing the surfaceType's from InteriorFloor to Ceiling and vice versa will not work - Skp automatically fixes them. A code will be needed to shift the order of these coordinates.

2015-03-17 22:32:43 -0500 commented answer Zone floor area is zero. Floor surfaces not recognized

imitate Untitled_SKP's correct info by changing the InteriorFloor surface types to Ceiling's. Skp automatically reverts my edits and the ceiling/floor error persists (gives me Warning: Changing surface type from 'RoofCeiling' to 'Floor' for surface 'su-7')

Also, I am new to ruby. Can you show me an example script that would change surface types?

2015-03-17 22:32:27 -0500 commented answer Zone floor area is zero. Floor surfaces not recognized

I've created example files to show my problem: [https://www.dropbox.com/sh/orj2soxgio...]

Untitled.xml is exported from Revit. It shows that matching ceiling&floors reference the same surface. Upon xml import in skp, reversed surfaces are created so that the clg & flr reference diff surface names with the same dimensions. I run into the clg & flr surface switch.

Untitled_SKP is exported from Skp after manual surface type correction. The xml shows no floor surfaces which is unexpected due to the new rev. surfaces created. I tried to alter my original xml to

2015-03-10 23:29:01 -0500 commented answer Zone floor area is zero. Floor surfaces not recognized

You are correct! Some spaces recognize both top and bottom bounding surfaces as floors. Other spaces, have ceiling and floor surfaces switched (spaces in lvl 1-3). OpenStudio was still able to run because the "floor" surface still existed, even if it was in the wrong location. The 4th floor was bounded by two "ceiling" surfaces so it did not run.

Questions now: 1) How can I quickly change surface types if they are incorrect? Manually doing so is tedious. Does a plugin for this (and reversing surfaces) exist? 2)Why does this occur in the first place? Is this due to poor practices in Revit?

2015-03-10 01:35:01 -0500 asked a question Zone floor area is zero. Floor surfaces not recognized

I have been encountering this error because the floor surfaces of my model's 4th floor are not being recognized in OSM:

* Warning * No floor exists in Zone="ZONE-4N10", zone floor area is zero. All values for this zone that are entered per floor area will be zero.

Background info: My model has 4 levels. It is created in Revit, exported to gbxml, then imported to OSM for simulation. . All zones have 1+ spaces in them. All spaces in all zones have floors. The floors for zones on levels 1-3 are recognized by Openstudio but not the floors for level 4 zones. I have tried exporting only the 4th floor and do not encounter this error.

Not sure if this information will be helpful, but in my Revit model, the ceilings are "non-room bounding". This means that the floor is the only bounding element between any 2 stories. Openstudio will recognize the floor of the 4th level and the "ceiling" of the 3rd level as identical but reversed surfaces. However, the 4th level does not recognize any floor surfaces.

Why are these floors not being recognized in Openstudio?

2015-02-24 21:02:21 -0500 asked a question Openstudio unable to load Energy Plus example files

I am currently using OS 1.6.0 and E+ v8.2 but get errors including 1) Some portions of the idf file were not imported 2) File not valid due to draft strictness, and sometimes expands in details depending on the idf file imported.

I have also tried importing the example idf files from v8.1 - another post mentioned that OS 1.6.0 wasn't running e+ 8.2 properly. Still encountered the same errors.

I have also tried uninstalling and reinstalling OS and e+, no change.

Can someone explain what's wrong?

2015-02-23 21:45:18 -0500 received badge  Scholar (source)
2015-02-11 21:03:24 -0500 received badge  Supporter (source)
2015-02-07 21:33:40 -0500 received badge  Student (source)
2015-02-07 20:37:25 -0500 asked a question How to model HVAC system without chiller/boiler eqmt. info in Openstudio?

I am trying to model a HVAC system for a 4-story building with ~400 zones (cooling with zone reheat). This building has chilled and hot water supplied from the central plant, for which I have no information aside CHWS/CHWR/HWS/HWR flow and temperature. The chilled and hot water are in separate parallel loops - the chilled water cools the outside air which then goes into VAV boxes with reheat coils which are served by the hot water (neglecting service hot water in this case). The chilled/hot water are both supplied through shafts from the basement, then into ducts for each zone. I have attempted a model, explained below, but would appreciate confirmation that I am interpreting OSM correctly!

In OSM's HVAC systems tab, I chose the "Packaged Rooftop: VAV with Reheat" template. Since I only have CHW and HW flow/temp info, I deleted the 1) "Condenser Water Loop", 2) "Chilled Water Loop", 3) the hot water coil on the supply side of the "VAV with Reheat Loop". I plan to have the ~400 zones linked in parallel to the "VAV with Reheat Loop", each with a "AirTerminal Single Duct VAV Reheat" that is linked to the "Hot Water Loop". Additionally, I plan to enter the design water flow rate and inlet/outlet water temperature for the cooling coil.

Is this approach correct? Any help is much appreciated!