yungahhh's profile - activity

@Irebello How long did it takes for the measure to work? Just curious. I have similar building (+3-4 more floors) and th

High-Rise Blg Application: IES-VE vs EnergyPlus Hi guys, I'm doing some research on working with high-rise building en

CBECC-RES Batch Processing Function I'm not very familiar with CBECC-RES as much as CBECC-COM. I'm using the 2019 CBECC-

Hi guys, The IES user meeting at the Sim Build conferences seem like there are quite a few IES users in the community. I was wondering is there other support group channels on top of the existing IES-VE forum and their support email? I saw that onebuilding as a virtual-sim mailing list for IES-VE users, but I didn't see many posts in the repository. Any active support forum or slack channels out there?

What are IES-VE support channel? Hi guys, The IES user meeting at the Sim Build conferences seem like there are quite a

With CBECC-COM, I would email CBECC support - cbecc.com@gmail.com , usually with the file and copy of the errors/problem

With CBECC-COM, I would email CBECC support - cbecc.com@gmail.com , usually with the file and copy of the errors/problem

This thread suggests that there may be issue with translating Compact Schedules from EPlus to OS, which might be the sou

@hoffmann1320 I think if a space is considered semi-heated space, then it would be modeled as system 9/10 (system 10 = e

What is your thermal zone type? Curious if it's considered semi-heated or conditioned space? It sounds like sys 10? Syst

There are several factors affecting the auto-sizing in the model such as the Design Ventilation Rates, minimum flow rate

I would just look at the SVA report when you do a preliminary run. You can manually calculate it : cooling capacities /

Not a super eQuest user, but... Yes. Let the program auto-size. Leave the ratio 1.15 for cooling and 1.25 for heating.

There is also Elements by Big Ladder. I usually just load .epw, copy and paste into Excel.

Not really an answer, but I think under the dropdown HVAC Zones, I think that typically transfer over with the thermal z

Similar question answered here.

I think you can find the answer here and here. In short, LegacyOS (or Euclid) is used to built geometry for E+ not for

I think you can find the answer here and here. In short, LegacyOS (or Euclid) is used to built geometry for E+ not for

Possible short term solution: I recently learned about XLSwing which is a python plug-in for Excel. I watched some youtu

What is supplying the air through the mullions?

@ljbrackney sorry for the late reply, but yes, for EMS and linking the refrigeration system with the HVAC

To answer plainly... preferences by the administrators who have deep root in DOE-2.

I think the answer to which is the best program to use always wind down to three things: 1) preferences and 2) what you are trying to achieve and 3) given the budget and the human resources (familiarity).

I'm replying to your question in the context of doing LEED and T24 only. Other type of analysis (parametric, box modelling, component modelling)... that's another day of discussion on its own. Ranking in term of my personal preference, it would be: (hate to love) CBECC-COM, Epro, Open Studio, IES.

IES VE generating results are not as straight forward, several clicks vs one click for OS or EPro, so that's one of the con I don't like about it. I like using IES VE for geometry as well, so we usually just export to CBECC-com to clean up the things that are buggy with IES-T24 module.

But overall, to build T24 and LEED model altogether using this software or that.... it's probably:

• Fastest/cheapest pathway:
  • IES geometry w/ dxf -> EnergyPro for LEED and T24 for basic buildings w/ traditional system
• Detailed Analysis System :
  • IES geometry w/ dxf -> T24 using CBECC-com to clean up the scrap IES geometry w/ dxf
  • IES for LEED to model nat vent, more complex system, claim more savings because there's more capability, better documentation, etc.

I haven't have a reason to use OS over IES-VE other than refrigeration system, eventually need to go down to the IDF editor for E+. But I imagine OS would be more useful at the city-level modeling since there's linkage with 3D warehouse , but there's the sad disconnect from Google Earth. >:( OS is also better if you replicate similar model over and over again. IES Run time can be tedious if you have to click 3 runs to get results. I'm quite fond of the OS measures as well, but have not explore better how it can be better utilized to fasten the LEED / T24 purposes quite yet beside probably QC purposes. Otherwise, most software have the template idea. IES-VE ASHRAE 62.1 interface to integrate with the ApacheHVAC is pretty awesome. The Table for the Zone (the excel-looking one) is also pretty awesome for internal QC. Those features are hard for OS to win over for day to day modeling.

As a reviewer, Open Studio / E+ standard results are pretty easy to review, which is nice. Since that's all you get sometimes, and not the model itself. Have not received IES model to review via incentive program so I can't say much here, but from submitting IES-results reports and what not, it's a little harder to put together into a review-friendly template without doing that Excel magic.

So eh, preferences.

From my adventure with using IES-VE for Title 24 compliance, most of the guidance hold and I noticed the following usability:

1) I still get the ventilation mismatch issues a lot of times. Usually, it's an easy fix for one or two zones after being exported to CBECC-COM and just scroll through the ventilation exhaust tab and checking if they are equaled.

2) Remove all holes or non-window glazing from IES-VE to CBECC-COM.

3) As for room names, I think the advice is pretty much true and avoid many problems down the line. For instance, rooms with the same name will be mapped into the same zone when you develop the zone in IES.

4) A number of things that typically doesn't translate through CBECC-COM is the Supply segments which cause error. When you name the Supply and Return - you kind of need a naming convention that would allow you to keep track and apply them to the appropriate zones - depending on how many systems you have. Copying systems over and having the same name for some of the flow causes error sometimes.

5) There are several ways to make windows in IES, but I would recommend to NEVER use the free-hand window option (when you're in plan view and just specify window width by dragging). It has more potential to generate surface errors because sometimes it doesn't define the geometry needs to be defined in E+/OS.

6) Use Title 24 materials when building constructions. And just double check your SGHC after exporting to CBECC-COM and run the model from there.

Hello there,

I am trying to model a two-stage (low temp and high temp) ammonia refrigeration system serving walkin coolers and freezers for a refrigerated warehouse in OpenStudio.

The tricky part is that this refrigeration loop has a number of heat exchanger serving different uses: 1) one near the condenser -> serving the heating hot water that would serve a handful of single zone AHUs; 2) one near the evaporator-> serving the chilled water loop that would serve a handful of single zone AHUs; 3) one heat exchanger serving the the underslab glycol.

My dilemma is how do I make the connection between Chilled Water Plant Loop (for the AHUs) to the Refrigeration Loop. Doesn't seem like there is anywhere on the GUI for OpenStudio. Or is there a possibility that I'm missing?

I'm thinking the only way to do this is to export the IDF and try to do this in EnergyPlus. I found a similar topic posted in using heat exchanger for glycol in EnergyPlus. I suppose that would work (according to the author) for the glycol apart. However, I haven't been able to find similar questions to connecting the wasted heat from refrigeration system to the district loops.

My questions are: 1) Can all these 3 heat exchangers connected to different loops be modeled successfully? 2) Is there any example idf out there that include the heat exchanger piece? Any recommendation is greatly appreciated.