[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[EnergyPlus_Support] Radiant Slab Boundary Conditions
- To: <EnergyPlus_Support@xxxxxxxxxxxxxxx>
- Subject: [EnergyPlus_Support] Radiant Slab Boundary Conditions
- From: <luke.dorna@xxxxxxxxx>
- Date: 11 Apr 2014 10:00:08 -0700
- Delivered-to: mailing list EnergyPlus_Support@xxxxxxxxxxxxxxx
- Delivery-date: Fri, 11 Apr 2014 11:00:16 -0600
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoogroups.com; s=echoe; t=1397235609; bh=bOrBzmp9hbZJmno4hXnSnxo436fMGz7kpHaGBkqhtM8=; h=Received:Received:X-Yahoo-Newman-Id:X-Sender:X-Apparently-To:X-Received:X-Received:X-Received:X-Received:X-Received:X-Received:X-Received:To:Message-ID:X-Mailer:X-Originating-IP:X-eGroups-Msg-Info:X-Yahoo-Post-IP:From:X-Yahoo-Profile:Sender:MIME-Version:Mailing-List:Delivered-To:List-Id:Precedence:List-Unsubscribe:Date:Subject:Reply-To:X-Yahoo-Newman-Property:Content-Type; b=b/qOsdfcSHFFtxVweFj6zidrys6j5gLp1piWq/zb5QUGJi+MBABcL1s4F2AklCjDZ4Dtyanoh9a/ku471c6VJIlGU5OSKKmsDcv2yVBDAWH/dtkkRz7ju0EV1dEsmTrsvRJd+XNaNfMNLeGGRSBz58Rm+2ZWhVMBCg9BEN32fw8=
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=echoe; d=yahoogroups.com; b=dwvDo6/f+LPCDObdz3OYld+KoI+V+VzaZO6sDfxeKdQoj8s8rO5RBqzYC9LAF7mErla5znkY35PYEhzxBMn9VW90MAqDn4/TZU1AoVZKFXXlAc864INPgDqPK+2+7v9dmSVmp4rJBpnPTHUQywKR0r8WYSwoTSFGcF9SEy3iezY=;
- Envelope-to: linda@xxxxxxxxxxxxxx
- List-id: <EnergyPlus_Support.yahoogroups.com>
- List-unsubscribe: <mailto:EnergyPlus_Support-unsubscribe@yahoogroups.com>
- Mailing-list: list EnergyPlus_Support@xxxxxxxxxxxxxxx; contact EnergyPlus_Support-owner@xxxxxxxxxxxxxxx
- Reply-to: EnergyPlus_Support@xxxxxxxxxxxxxxx
I am currently working on a six story building a HVAC system consisting of heating/cooling radiant slabs and dedicated outdoor air ventilation.
If I recall correctly, previous versions of EnergyPlus required that the boundary condition for a surface acting as a radiant slab had to be "surface" with the appropriate "one to one" intersection of all surfaces in the model. Is this still the case? In short, OpenStudio is starting to freak out over the size of the model and intersecting all the surfaces will give it more excuses to misbehave. A quick experiment I ran with the example file that changed the boundary condition of the radiant surfaces did not produce an error.
Given that the entire building is office, I don't think I'll run into thermal effects from the lack of transfer between zones. Thoughts?
__._,_.___
Primary EnergyPlus support is found at:
<http://energyplus.helpserve.com>http://energyplus.helpserve.com or send a message to energyplus-support@xxxxxxxx
The primary EnergyPlus web site is found at:
<http://www.energyplus.gov>http://www.energyplus.gov
The group web site is:
<http://groups.yahoo.com/group/EnergyPlus_Support/>http://groups.yahoo.com/group/EnergyPlus_Support/
Attachments are currently allowed but be mindful that not everyone has a high speed connection. Limit attachments to small files.
EnergyPlus Documentation is searchable. Open EPlusMainMenu.pdf under the Documentation link and press the "search" button.
<http://geo.yahoo.com/serv?s=97476590/grpId=3387488/grpspId=1705007389/msgId=31704/stime=1397235609>
<https://groups.yahoo.com/neo/groups/EnergyPlus_Support/info;_ylc=X3oDMTJlMDNtMWg5BF9TAzk3MzU5NzE0BGdycElkAzMzODc0ODgEZ3Jwc3BJZAMxNzA1MDA3Mzg5BHNlYwN2dGwEc2xrA3ZnaHAEc3RpbWUDMTM5NzIzNTYwOQ-->Visit Your Group
* <https://groups.yahoo.com/neo/groups/EnergyPlus_Support/members/all;_ylc=X3oDMTJmaGJqY3VzBF9TAzk3MzU5NzE0BGdycElkAzMzODc0ODgEZ3Jwc3BJZAMxNzA1MDA3Mzg5BHNlYwN2dGwEc2xrA3ZtYnJzBHN0aW1lAzEzOTcyMzU2MDk->New Members 8
<https://groups.yahoo.com/neo;_ylc=X3oDMTJkbG1sMmNlBF9TAzk3NDc2NTkwBGdycElkAzMzODc0ODgEZ3Jwc3BJZAMxNzA1MDA3Mzg5BHNlYwNmdHIEc2xrA2dmcARzdGltZQMxMzk3MjM1NjA5><http://l.yimg.com/ru/static/images/yg/img/email/new_logo/logo-groups-137x15.png>
? <https://info.yahoo.com/privacy/us/yahoo/groups/details.html>Privacy ? <mailto:EnergyPlus_Support-unsubscribe@xxxxxxxxxxxxxxx?subject=Unsubscribe>Unsubscribe ? <https://info.yahoo.com/legal/us/yahoo/utos/terms/>Terms of Use
__,_._,___