[Equest-users] Purpose of a DESIGN-DAY CLIMATE input?

Fri Dec 2 04:05:21 PST 2016

Hi Nick,

Design day is the day at which design or peak load calculations are done.
It is not a very big deal to have climate as Tropical as it would be
between the Tropic of Cancer to Tropic of Capricorn.
In the midst of which there is equator.
It is mere a margin to show that the Tropical shows that the location is in
the margin of 23.5 degree south of equator to 23.5 degree North of the
equator.

The Mid-latitude can be the location near to the equator as it is the
middle or zero degree latitude of the earth.

The Subarctic region is the space near and hence off the polar to sub polar
region.

The thing that you are missing is the temperate zone which is in between
the 23.5 to 66.5 degree region.

The climate is very hot and warm in tropical region.
The climate is of mild nature in the temperate zone and very cold in the
sub arctic region.
As the solar angle declines away from the equator to the pole.
The solar angle is very less at polar and sub polar region and hence very
cold climate. The solar angle is directly over the head in the equator
region for major part of the year. Hence a sign of mid latitude as it is in
the midst of the globe.

*Thanks,*
Sharad.

............................................................
............................................................
............................................................
....................................................................

On 11/29/2016 9:43 AM, Nicholas Caton via Equest-users wrote:

I have a question concerning doe2/eQUEST DESIGN-DAYs

One of the keywords for DESIGN-DAY confuses me:  CLIMATE.  I have not been
able to find this documented in the current doe2 reference manual or 2.1A
engineering manuals.

It appears the CLIMATE keyword can accept one of three inputs:
“SUBARCTIC,” “MIDLATITUDE,” or “TROPICAL.”  The default is MIDLATITUDE and
does not appear to reference anything else.

So I have a few questions:

1.       What is this input used for?  Does it help to determine solar
angles during design day calculations?  Does it affect how other DESIGN-DAY
inputs are interpreted?

2.       Since one of the options is named “MIDLATITUDE,” my best guess is
this is trying to establish in a loose sense which slice of the globe the
weather station is located at for solar angle purposes.  From that guess, I
googled the topic for a bit
<http://www.lat34north.com/cities/CitiesLatitude.cfm> and came up with this
framework:

a.       SUBARCTIC latitudes are > 66.5 or < -66.5  (Inside the Arctic
circles – experiences days of complete daylight/darkness)

b.      TROPICAL is between -23.5 and 23.5 (Tropic of Capricorn/Cancer –
experiences the sun traversing directly overhead)

c.       MIDLATITUDE = everywhere else

3.       I struggle however with the concept of a DESIGN-DAY input based on
latitude, where

a.       The latitude is already a part of the weather file required for
every simulation… and pulling the exact latitude would be more accurate
anyway (I confess here I have never studied solar pathing in great depth –
the problem may be simpler than I realize?).

b.      These bands alone don’t give you enough information to know when
you’re in the lower hemisphere (where solar angles based on the day/month
would be flipped)

c.       This leads me to question whether there’s a (meaningful)
difference in solar angles experienced for loads calculations when you use
the weather file instead of DESIGN-DAY inputs.

d.      Alternatively, maybe the latitude IS pulled from the weather file
for solar angle purposes so I’m completely on the wrong path as to the
purpose/intent for the CLIMATE input.

Can anyone set me straight on this topic?

~Nick

*Nick Caton, P.E., BEMP*

  Senior Energy Engineer
  Energy and Sustainability Services
  Schneider Electric

D  913.564.6361
M  785.410.3317
E  nicholas.caton at schneider-electric.com
F  913.564.6380

15200 Santa Fe Trail Drive
Suite 204
Lenexa, KS 66219
United States

[image: cid:image001.png at 01D189AB.58634A10]

------------------------------

This message was scanned by Exchange Online Protection Services.
------------------------------

_______________________________________________

Equest-users mailing list

http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org

To unsubscribe from this mailing list send  a blank message to
EQUEST-USERS-UNSUBSCRIBE at ONEBUILDING.ORG
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20161202/3e1bd5a3/attachment-0005.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 7893 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20161202/3e1bd5a3/attachment-0015.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 34261 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20161202/3e1bd5a3/attachment-0016.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 255 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20161202/3e1bd5a3/attachment-0017.png>