Skip to content

Commit

Permalink
Merge pull request #7455 from NREL/AirWallRadSolarMixing
Browse files Browse the repository at this point in the history
New Air Thermal Boundary Construction Type
  • Loading branch information
Myoldmopar authored Aug 20, 2019
2 parents 6cc60de + 2323a3a commit c71ad58
Show file tree
Hide file tree
Showing 53 changed files with 6,503 additions and 1,331 deletions.
Binary file added design/FY2019/Airwall-Fig1-OpenPlanOffice.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
444 changes: 444 additions & 0 deletions design/FY2019/Interzone Air Wall NFP and Design.md

Large diffs are not rendered by default.

Original file line number Diff line number Diff line change
Expand Up @@ -73,6 +73,8 @@ \subsubsection{Specifying an Infrared Transparent (IRT) surface}\label{specifyin

The Infrared Transparent surface should not participate in a convective/conductive exchange between the zones it separates. In order to minimize this effect, the SurfaceProperty:ConvectionCoefficients object must be used. Outside and Inside values for the surface's convection coefficients should be on the order of .1.~ Further examples are given in the Input Output Reference document.

Infrared transparent surfaces may also be specified using Construction:AirBoundary with the \textit{IRTSurface} option for radiant exchange. This method automatically generates an internal material layer with IRT properties and sets the inside convection coefficient to the Minimum Surface Convection Heat Transfer Coefficient Value specified in the HeatBalanceAlgorithm object which defaults to 0.1 [W/m2-K].

\subsection{Behavior Checks}\label{behavior-checks}

The behavior of multi zones separated with infrared transparent surfaces can be checked with a simple comparison. Begin with a single zone model as shown below. This model has a south-facing window, and four walls exposed to wind and sun, and a roof exposed to wind and sun.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -11,11 +11,11 @@ \section{Inside Heat Balance}\label{inside-heat-balance}

where:

\({q''_{LWX}}\) = Net longwave radiant exchange flux between zone surfaces.
\({q''_{LWX}}\) = Net longwave radiant exchange flux between surfaces in a zone or group of zones (enclosure).

\({q''_{SW}}\) ~ = Net short wave radiation flux to surface from lights.

\({q''_{LWS}}\) = Longwave radiation flux from equipment in zone.
\({q''_{LWS}}\) = Longwave radiation flux from equipment in a zone or group of zones (enclosure).

\({q''_{ki}}\) ~ = Conduction flux through the wall.

Expand All @@ -33,6 +33,8 @@ \section{Inside Heat Balance}\label{inside-heat-balance}

\subsection{Internal Long-Wave Radiation Exchange}\label{internal-long-wave-radiation-exchange}

Long-wave radiation exchange is balanced within an enclosure which may be a single zone or a group of zones connected by air boundaries (see Construction:AirBoundary) using the \textit{GroupedZone} radiant exchange method. Throughout this section, "Zone" refers to either type of enclosure.

\subsubsection{LW Radiation Exchange Among Zone Surfaces}\label{lw-radiation-exchange-among-zone-surfaces}

There are two limiting cases for internal LW radiation exchange that are easily modeled:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -2695,13 +2695,16 @@ \subsubsection{User Input View Factors}\label{user-input-view-factors}

\subsection{ZoneProperty:UserViewFactors:bySurfaceName}\label{zonepropertyuserviewfactorsbysurfacename}

The method of entering user view factors is to entere each surface name and its view factor value to other surfaces in the zone
The method of entering user view factors is to enter each surface name and its view factor value to other
surfaces in a zone or group of zones connected by air boundaries (see ``\hyperref[constructionairboundary]{Construction:AirBoundary}'').

\subsubsection{Inputs}\label{inputs-17}

\paragraph{Field: Zone Name}\label{zonepropertyuserviewfactorsbysurfacename-field-zone-name}
\paragraph{Field: Zone or ZoneList Name}\label{zonepropertyuserviewfactorsbysurfacename-field-zone-name}

This field is the zone name for the view factors.
An enclosure for radiant exchange may be a single zone, or a group of zones connected by one or more air boundaries (see ``\hyperref[constructionairboundary]{Construction:AirBoundary}''). If a ZoneList name is specified, the referenced ``\hyperref[zonelist]{ZoneList}'') must match a group of zones connected with Construction:AirBoundary using the \textit{GroupedZones} option for Radiant Exchange Method.

Enter the applicable surface pairs with non-zero view factors. Any omitted surface pair is assumed to have a zero view factor.

\paragraph{Field: From Surface 1}\label{field-from-surface-1}

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -4066,6 +4066,73 @@ \subsubsection{Outputs}\label{outputs-36-1}

This output is the temperature within the surface at the location requested by the user.

\subsection{Construction:AirBoundary}\label{constructionairboundary}

Construction:AirBoundary indicates an open boundary between two zones. It may be used for base surfaces and fenestration surfaces.
When this construction type is used, the Outside Boundary Condition of the surface (or the base surface of a fenestration surface)
must be either \textit{Surface} or \textit{Zone}. A base surface with Construction:AirBoundary cannot hold any fenestration surfaces.

\subsubsection{Inputs}\label{inputs-38-01}

\paragraph{Field: Name}\label{field-name-31-0001}

The name of the construction.

\paragraph{Field: Solar and Daylighting Method}\label{field-solar and-daylighting-method}

This field controls how the surface is modeled for solar distribution and daylighting calculations. There are two
choices:
\begin{itemize}
\item
\textbf{GroupedZones} - The two zones separated by this air boundary will be grouped together into a combined zone for solar distribution and daylighting. If a given zone has an air boundary with more than one zone, then all of the connected zones will be grouped together. For example, if there is an air boundary between zones A and B, and another air boundary between zones B and C, all three zones (A, B, and C) will be grouped into a single zone.

\item
\textbf{InteriorWindow} - The air boundary will be modeled as a perfectly transmitting interior window. As with other interior windows, all direct solar passing through the interior window will be diffuse in the adjacent zone.
\end{itemize}

\paragraph{Field: Radiant Exchange Method}\label{field-radiant-exchange-method}

This field controls how the surface is modeled for radiant exchange calculations. There are two choices:

\begin{itemize}
\item
\textbf{GroupedZones} - The two zones separated by this air boundary will be grouped together into a combined zone for radiant exchange between surfaces and distribution of radiant internal gains. If a given zone has an air boundary with more than one zone, then all of the connected zones will be grouped together. For example, if there is an air boundary between zones A and B, and another air boundary between zones B and C, all three zones (A, B, and C) will be grouped into a single zone. Normal default simplified view factors will apply unless detailed view factors are specified using \hyperref[zonepropertyuserviewfactorsbysurfacename]{ZoneProperty:UserViewFactors:bySurfaceName}.

\item
\textbf{IRTSurface} - The air boundary will be modeled as blackbody surface between the adjacent zones (similar to, but not exactly the same as, \hyperref[materialinfraredtransparent]{Material:InfraredTransparent}. The surface participates in the radiant exchange within each zone and receives long-wave radiant energy from internal sources. The surface does not absorb any visible or solar radiation, has no thermal resistance, and has zero convective heat transfer coefficients on both sides.
\end{itemize}

\paragraph{Field: Air Exchange Method}\label{field-air-exchange-method}

This field controls how the surface is modeled for radiant exchange calculations. There are two choices:

\begin{itemize}
\item
\textbf{None} - There will be no air exchange modeled across this surface. Other objects, such as \hyperref[zonemixing]{ZoneMixing} and \hyperref[zonecrossmixing]{ZoneCrossMixing} or AirflowNetwork openings may be specified if desired.
\item
\textbf{SimpleMixing} - For each pair of zones connected by Construction:AirBoundary, a pair of ZoneMixing objects will created automatically. These mixing objects may be automatically adjusted to balance HVAC system flows using the \hyperref[zoneairmassflowconservation]{ZoneAirMassFlowConservation} object.

\end{itemize}

\paragraph{Field: Simple Mixing Air Changes per Hour}\label{field-simple-mixing-air-changes-per-hour}

If the Air Exchange Method is \textit{SimpleMixing}* then this field specifies the air change rate [1/hr] using the volume of the smaller zone as the basis. The default is 0.5. If an AirflowNetwork simulation is active this field is ignored.

\paragraph{Field:Simple Mixing Schedule Name}\label{field-Simple-mixing-schedule-name}

If the Air Exchange Method is \textit{SimpleMixing} then this field specifies the schedule name for the air mixing across this boundary. If this field is blank, then the schedule defaults to always 1.0. If an AirflowNetwork simulation is active this field is ignored.

IDF Example:

\begin{lstlisting}
Construction:AirBoundary,
Air Wall, !- Name
GroupedZones, !- Solar and Daylighting Method
GroupedZones, !- Radiant Exchange Method
SimpleMixing, !- Air Exchange Method
0.5, !- Simple Mixing Air Changes per Hour {1/hr}
; !- Simple Mixing Schedule Name
\end{lstlisting}

\subsection{Composite Wall Constructions}\label{composite-wall-constructions}

Expand Down
Loading

7 comments on commit c71ad58

@nrel-bot-3
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

develop (Myoldmopar) - x86_64-MacOS-10.13-clang: OK (1808 of 1808 tests passed, 0 test warnings)

Build Badge Test Badge

@nrel-bot-2b
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

develop (Myoldmopar) - x86_64-Linux-Ubuntu-18.04-gcc-7.4: OK (1828 of 1828 tests passed, 0 test warnings)

Build Badge Test Badge

@nrel-bot-2b
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

develop (Myoldmopar) - x86_64-Linux-Ubuntu-18.04-custom_check: OK (9 of 9 tests passed, 0 test warnings)

Build Badge

@nrel-bot-2
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

develop (Myoldmopar) - x86_64-Linux-Ubuntu-18.04-cppcheck: OK (0 of 0 tests passed, 0 test warnings)

Build Badge

@nrel-bot-2b
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

develop (Myoldmopar) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-UnitTestsCoverage-Debug: OK (1140 of 1140 tests passed, 0 test warnings)

Build Badge Test Badge Coverage Badge

@nrel-bot-2
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

develop (Myoldmopar) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-IntegrationCoverage-Debug: OK (671 of 671 tests passed, 0 test warnings)

Build Badge Test Badge Coverage Badge

@nrel-bot
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

develop (Myoldmopar) - Win64-Windows-10-VisualStudio-16: OK (1808 of 1808 tests passed, 0 test warnings)

Build Badge Test Badge

Please sign in to comment.