[Equest-users] Can we reference DESIGN-DAY inputs in zonal expressions?

Thu Sep 7 14:35:14 PDT 2017

Isn't it funny, I thought DESIGN-DAYs should be accessible via #G() initially as well!

I'm a little averse to making my ground temps equal to winter/summer design DB conditions as a general practice... A more innocuous option for leveraging a SITE-PARAMETER as a proxy/container might be LONGITUDE... but ideally I'm looking for a pair of "containers" and I think LATITUDE is actually leveraged for solar sky model stuff (daylight calculations, possibly cooling DESIGN-DAY but I have my doubts)...

Outside of SITE-PARAMETERs... Have I perhaps stumbled upon the exact intent/purpose behind these "Variable##" "containters" under the PROJECT-DATA variables?  Does anyone know how to access these values via keyword expresssions?
[cid:image004.png at 01D327F7.448C3100]

~Nick

[cid:image001.png at 01D327F5.475CA100]
Nick Caton, P.E., BEMP
  Senior Energy Engineer
  Regional Energy Engineering Manager
  Energy and Sustainability Services
  Schneider Electric

D  913.564.6361
M  785.410.3317
F  913.564.6380
E  nicholas.caton at schneider-electric.com<mailto:nicholas.caton at schneider-electric.com>

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

[cid:image002.png at 01D327F5.475CA100]

From: Bishop, Bill [mailto:bbishop at pathfinder-ea.com]
Sent: Thursday, September 07, 2017 3:12 PM
To: Nicholas Caton <Nicholas.Caton at schneider-electric.com>
Cc: equest-users at lists.onebuilding.org
Subject: RE: [Equest-users] Can we reference DESIGN-DAY inputs in zonal expressions?

Hi Nick,
I haven't figured out a way to reference DESIGN-DAY keywords from outside of the command. The DESIGN-DAYs are not global parameters (so you can't use #G), and they do not have children that can reference them as parents. You could create global parameters per your own suggestion below.
An alternative is to reference other climate data inputs for your DESIGN-COOL-T and DESIGN-HEAT-T zone keywords.
For example, you could enter the monthly ground temperatures. Then, say you want the unconditioned zone DESIGN-HEAT-T to match the December ground temperature:
if(#RV(#G("SITE-PARAMETERS","GROUND-T",11))==0)
  then #G("SITE-PARAMETERS","GROUND-T",11)
  else 70 endif

Regards,
~Bill

William Bishop, PE, BEMP, BEAP, CEM, LEED AP | Pathfinder Engineers & Architects LLP
Senior Energy Engineer

[cid:image006.jpg at 01D327F7.448C3100]  [cid:image008.jpg at 01D327F7.448C3100]

134 South Fitzhugh Street                 Rochester, NY 14608

T: (585) 698-1956                        F: (585) 325-6005

bbishop at pathfinder-ea.com<mailto:wbishop at pathfinder-ea.com>             www.pathfinder-ea.com<http://www.pathfinder-ea.com/>

[http://png-5.findicons.com/files/icons/977/rrze/720/globe.png]Carbon Fee and Dividend - simple, effective, and market-based.

From: Equest-users [mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of Nicholas Caton via Equest-users
Sent: Thursday, September 07, 2017 11:59 AM
To: equest-users at lists.onebuilding.org<mailto:equest-users at lists.onebuilding.org>
Subject: [Equest-users] Can we reference DESIGN-DAY inputs in zonal expressions?

Hi friends!

Is fundamentally possible to, from within a user-expression, pull a value from cooling / heating DESIGN-DAY inputs?

In particular, I'd like to return DRYBULB-HIGH from both my cooling and heating DESIGN-DAY, using those values to inform zonal DESIGN-COOL-T and DESIGN-HEAT-T for unconditioned and plenum zones.  I can see a path to have both DESIGN-DAY and zonal inputs reference a pair of global parameters, but I'm making every effort to minimize "#PA spam" in my regular model development.

~Nick

[cid:image001.png at 01D327F5.475CA100]
Nick Caton, P.E., BEMP
  Senior Energy Engineer
  Regional Energy Engineering Manager
  Energy and Sustainability Services
  Schneider Electric

D  913.564.6361
M  785.410.3317
F  913.564.6380
E  nicholas.caton at schneider-electric.com<mailto:nicholas.caton at schneider-electric.com>

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

[cid:image002.png at 01D327F5.475CA100]

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170907/f24c7523/attachment-0004.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 255 bytes
Desc: image001.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170907/f24c7523/attachment-0016.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 8477 bytes
Desc: image002.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170907/f24c7523/attachment-0017.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: oledata.mso
Type: application/octet-stream
Size: 7129 bytes
Desc: oledata.mso
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170907/f24c7523/attachment-0004.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 108580 bytes
Desc: image004.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170907/f24c7523/attachment-0018.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 1240 bytes
Desc: image006.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170907/f24c7523/attachment-0008.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.jpg
Type: image/jpeg
Size: 1307 bytes
Desc: image008.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170907/f24c7523/attachment-0009.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image012.png
Type: image/png
Size: 2846 bytes
Desc: image012.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170907/f24c7523/attachment-0019.png>