[Equest-users] I missed you guys and I feel like sharing - NAME as BDL function argument?
Bishop, Bill via Equest-users
equest-users at lists.onebuilding.org
Thu Aug 17 09:13:17 PDT 2017
Nick,
This expression works for your example below:
if(#P("POLYGON")==#SI("EL1 Floor Polygon","FLOOR","POLYGON"))
then 1.85
else 1.50
endif
However, the expression references the POLYGON of the floor, not the NAME of the floor.
If you try the expression below, you get an error "Invalid BDL Keyword function argument 'NAME'"
if(#P("NAME")==#SI("1STFLOORNAME","FLOOR","NAME"))
then 1.85
else 1.50
endif
You can add comments to the expression to label the cases with floor names, but the expression is still based on the occurrence number of the FLOOR:
switch #SV(#PS())
case 1 : 1.85 $ IceRink Floor 1
case 2 : 1.5 $ IceRink Floor 2
default : 1.0
endswitch
~Bill
From: Nicholas Caton [mailto:Nicholas.Caton at schneider-electric.com]
Sent: Thursday, August 17, 2017 10:55 AM
To: Jones, Christopher <Christopher.r.Jones at wsp.com>; Bishop, Bill <bbishop at pathfinder-ea.com>
Cc: equest-users at lists.onebuilding.org
Subject: RE: I missed you guys and I feel like sharing
Maybe a second set of eyes will help me missing some syntax here... but I think this should work (it doesn't!):
[cid:image016.png at 01D3174F.77238C70]
For those not receiving images (and the archives), the non-working expression I came up with is:
if(#PS()==#SI("1STFLOORNAME","FLOOR","POLYGON"))
then 1.85
else 1.50
endif
I get the following error message:
[cid:image017.png at 01D3174F.77238C70]
Entering just #PS() for LIGHTING-W/AREA does return a numerical value... it should seem possible to look up by symbol index value, but perhaps the symbol name is getting changed in the process of INP --> BDL?
I checked the corresponding *.BDL file for this model (not sure if this is the right way to confirm the above), and I see the name isn't being changed here:
[cid:image018.png at 01D3174F.77238C70]
Again, I sense this SHOULD work... and this framework does work for citing system names with zonal inputs. Perhaps I'm missing something or there's some extra quirk/trick involved on the space/floor side of things.
Can anyone else spot the issue here? The dummy model used for the above exploration is attached, in the interest of continuity and saving other interested parties a minute in setup - v3.65 build 7163.
~Nick
[cid:image019.png at 01D3174F.77238C70]
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:image020.png at 01D3174F.77238C70]
From: Jones, Christopher [mailto:Christopher.r.Jones at wsp.com]
Sent: Wednesday, August 16, 2017 6:40 PM
To: Nicholas Caton <Nicholas.Caton at schneider-electric.com<mailto:Nicholas.Caton at schneider-electric.com>>; Bishop, Bill <bbishop at pathfinder-ea.com<mailto:bbishop at pathfinder-ea.com>>
Cc: equest-users at lists.onebuilding.org<mailto:equest-users at lists.onebuilding.org>
Subject: RE: I missed you guys and I feel like sharing
Thank you team.
I got this far - setting the lighting power density using the floor number but I could not find a way to reference the floor name.
switch SymValue(ParentSym())
case 1 : 1.85
case 2 : 1.5
default : 1.0
endswitch
The floor names:
"IceRink Floor 1" = FLOOR
"IceRink Floor 2" = FLOOR
At any rate, the question came to me wanting to use the floor number so I can respond with this solution. I would still like to know if you can reference the floor name in an expression?
Christopher R. Jones, P.Eng.
Technical Specialist
Sustainability & Energy
[cid:image021.png at 01D3174F.77238C70]
T +1 416-644-0252
2300 Yonge Street, Suite 2300
Toronto, ON M4P 1E4 Canada
wsp.com
Please consider the environment before printing...
From: Nicholas Caton [mailto:Nicholas.Caton at schneider-electric.com]
Sent: Wednesday, August 16, 2017 6:13 PM
To: Bishop, Bill <bbishop at pathfinder-ea.com<mailto:bbishop at pathfinder-ea.com>>; Jones, Christopher <Christopher.r.Jones at wsp.com<mailto:Christopher.r.Jones at wsp.com>>
Cc: equest-users at lists.onebuilding.org<mailto:equest-users at lists.onebuilding.org>
Subject: RE: I missed you guys and I feel like sharing
Chris,
Practically-speaking, are you asking whether it's possible to reference the textual name of a parent component (system/floor/etc) in an expression? If so I can answer that in the affirmative with an example or two.
~Nick
[cid:image019.png at 01D3174F.77238C70]
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:image020.png at 01D3174F.77238C70]
From: Equest-users [mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of Bishop, Bill via Equest-users
Sent: Wednesday, August 16, 2017 3:18 PM
To: Jones, Christopher <Christopher.r.Jones at wsp.com<mailto:Christopher.r.Jones at wsp.com>>
Cc: equest-users at lists.onebuilding.org<mailto:equest-users at lists.onebuilding.org>
Subject: Re: [Equest-users] I missed you guys and I feel like sharing
Christopher,
I don't believe it is possible to reference U-NAMEs with a BDL function. Hopefully I said that right.
However, you can use the same method I described below with spaces and floors.
Here is a modification of the DOE-2 default expression for infiltration AIR-CHANGES/HR that sets ACH values based on the floor the space is assigned to:
switch (#SV(#L("INF-METHOD")))
case 0 : unused
case 1 : switch #SV(#PS())
case 1 : 1.0
case 2 : 1.5
case 3 : 2.0
case 4 : 3.0
default : 0.00 endswitch
case 2 : unused
case 3 : unused
case 4 : unused
default : unused
endswitch
~Bill
From: Jones, Christopher [mailto:Christopher.r.Jones at wsp.com]
Sent: Wednesday, August 16, 2017 3:47 PM
To: Bishop, Bill <bbishop at pathfinder-ea.com<mailto:bbishop at pathfinder-ea.com>>
Cc: equest-users at lists.onebuilding.org<mailto:equest-users at lists.onebuilding.org>
Subject: RE: I missed you guys and I feel like sharing
Thank you Bill,
I am wondering if there is a UDF means to determine the parent floor name of the spaces in the model?
Christopher R. Jones, P.Eng.
Technical Specialist
Sustainability & Energy
[cid:image021.png at 01D3174F.77238C70]
T +1 416-644-0252
2300 Yonge Street, Suite 2300
Toronto, ON M4P 1E4 Canada
wsp.com
Please consider the environment before printing...
From: Equest-users [mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of Bishop, Bill via Equest-users
Sent: Wednesday, August 16, 2017 3:35 PM
To: equest-users at lists.onebuilding.org<mailto:equest-users at lists.onebuilding.org>
Subject: [Equest-users] I missed you guys and I feel like sharing
I've been too clueless to notice that I haven't gotten eQUEST-users messages since May. I blocked Rodrigo's vacation messages which we all got 500 of and everything else was blocked too...
So here's a random Tip-of-the-Day!
Create custom User-Defined Default Expressions that set system and/or zone defaults based on the occurrence number of the system.
Example:
Your project uses 12 systems - five PVAV systems, five PSZ systems, one HVSYS and one UVT, and the order you created them is PVAV-1, PVAV-2,...,PVAV-5, PSZ-1,...,PSZ-5, HVSYS, UVT
The corresponding occurrence numbers for these systems is 1,2,3,4,5,6,7,8,9,10,11,12.
Using the BDL function SymValue combined with LocalSym or ParentSym, you can create expressions such as this one, which assigns different zone cooling thermostat schedules based on the system the zone is assigned to:
COOL-TEMP-SCH =
{if (#SV(#PS())==1 .OR. #SV(#PS())==7) then
#SI("72F Cool Sch", "ZONE", "COOL-TEMP-SCH")
else if (#SV(#PS())>10) then unused
else #SI("74F Cool Sch", "ZONE", "COOL-TEMP-SCH")
endif
endif}
You could make the same assignments with a SWITCH statement:
COOL-TEMP-SCH =
{switch #SV(#PS())
case 1 : #SI("72F Cool Sch", "ZONE", "COOL-TEMP-SCH")
case 7 : #SI("72F Cool Sch", "ZONE", "COOL-TEMP-SCH")
case 11 : unused
case 12 : unused
default : #SI("74F Cool Sch", "ZONE", "COOL-TEMP-SCH")
endswitch}
You would use the BDL function LocalSym to assign SYSTEM keywords by system occurrence number. Since each system TYPE has its own keyword defaults, you would need to customize the expression for each system type, or copy the same expression into each of the system types you want to apply it to.
COOLING-EIR =
{switch #SV(#LS())
case 1 : 0.2945 $ PVAV-1
case 2 : 0.3051 $ PVAV-2
case 3 : 0.2945 $ PVAV-3
case 4 : 0.2945 $ PVAV-4
case 5 : 0.3051 $ PVAV-5
case 7 : 0.3283 $ PSZ-2
default : 0.2267 $ All other systems for which this expression is used
endswitch}
Regards,
~Bill
William Bishop, PE, BEMP, BEAP, CEM, LEED AP | Pathfinder Engineers & Architects LLP
Senior Energy Engineer
[cid:image022.jpg at 01D3174F.77238C70] [cid:image023.jpg at 01D3174F.77238C70]
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.
________________________________
You are receiving this communication because you are listed as a current WSP contact. Should you have any questions regarding WSP's electronic communications policy, please consult our Anti-Spam Commitment www.wsp.com/casl<http://www.wsp.com/casl>. For any concern or if you believe you should not be receiving this message, please forward this message to caslcompliance at wsp.com<mailto:caslcompliance at wsp.com> so that we can promptly address your request. This message is intended only for the addressee and may contain information which is privileged, confidential, proprietary, or exempt from disclosure under applicable law. If you are not the intended recipient, you are strictly prohibited from disclosing, distributing, copying, or in any way using this message. If you have received this communication in error, please notify the sender and delete any copies you may have received.
----------------------------------------------------------------------------------------------------------------------------------------
Vous recevez cette communication car vous faites partie des contacts de WSP. Si vous avez des questions concernant la politique de communications électroniques de WSP, veuillez consulter notre Engagement anti-pourriel www.wsp.com/lcap<http://www.wsp.com/casl>. Pour toute question ou si vous croyez que vous ne devriez pas recevoir ce message, prière de le transférer au conformitelcap at wsp.com<mailto:conformitelcap at wsp.com> afin que nous puissions rapidement traiter votre demande. Ce message est destiné uniquement au destinataire et il peut contenir des informations privilégiées, confidentielles ou non divulgables en vertu de la loi. Si vous n'êtes pas le destinataire du présent message, il vous est strictement interdit de le divulguer, de le distribuer, de le copier ou de l'utiliser de quelque façon que ce soit. Si vous avez reçu la présente communication par erreur, veuillez en aviser l'expéditeur et supprimer le message.
______________________________________________________________________
NOTICE: This communication and any attachments ("this message") may contain confidential information for the sole use of the intended recipient(s). Any unauthorized use, disclosure, viewing, copying, alteration, dissemination or distribution of, or reliance on this message is strictly prohibited. If you have received this message in error, or you are not an authorized recipient, please notify the sender immediately by replying to this message, delete this message and all copies from your e-mail system and destroy any printed copies.
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________
________________________________
You are receiving this communication because you are listed as a current WSP contact. Should you have any questions regarding WSP's electronic communications policy, please consult our Anti-Spam Commitment www.wsp.com/casl<http://www.wsp.com/casl>. For any concern or if you believe you should not be receiving this message, please forward this message to caslcompliance at wsp.com<mailto:caslcompliance at wsp.com> so that we can promptly address your request. This message is intended only for the addressee and may contain information which is privileged, confidential, proprietary, or exempt from disclosure under applicable law. If you are not the intended recipient, you are strictly prohibited from disclosing, distributing, copying, or in any way using this message. If you have received this communication in error, please notify the sender and delete any copies you may have received.
----------------------------------------------------------------------------------------------------------------------------------------
Vous recevez cette communication car vous faites partie des contacts de WSP. Si vous avez des questions concernant la politique de communications électroniques de WSP, veuillez consulter notre Engagement anti-pourriel www.wsp.com/lcap<http://www.wsp.com/casl>. Pour toute question ou si vous croyez que vous ne devriez pas recevoir ce message, prière de le transférer au conformitelcap at wsp.com<mailto:conformitelcap at wsp.com> afin que nous puissions rapidement traiter votre demande. Ce message est destiné uniquement au destinataire et il peut contenir des informations privilégiées, confidentielles ou non divulgables en vertu de la loi. Si vous n'êtes pas le destinataire du présent message, il vous est strictement interdit de le divulguer, de le distribuer, de le copier ou de l'utiliser de quelque façon que ce soit. Si vous avez reçu la présente communication par erreur, veuillez en aviser l'expéditeur et supprimer le message.
______________________________________________________________________
NOTICE: This communication and any attachments ("this message") may contain confidential information for the sole use of the intended recipient(s). Any unauthorized use, disclosure, viewing, copying, alteration, dissemination or distribution of, or reliance on this message is strictly prohibited. If you have received this message in error, or you are not an authorized recipient, please notify the sender immediately by replying to this message, delete this message and all copies from your e-mail system and destroy any printed copies.
______________________________________________________________________
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/20170817/685ea795/attachment-0004.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image016.png
Type: image/png
Size: 95789 bytes
Desc: image016.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170817/685ea795/attachment-0028.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image017.png
Type: image/png
Size: 27049 bytes
Desc: image017.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170817/685ea795/attachment-0029.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image018.png
Type: image/png
Size: 34450 bytes
Desc: image018.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170817/685ea795/attachment-0030.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image019.png
Type: image/png
Size: 255 bytes
Desc: image019.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170817/685ea795/attachment-0031.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image020.png
Type: image/png
Size: 8477 bytes
Desc: image020.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170817/685ea795/attachment-0032.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image021.png
Type: image/png
Size: 25844 bytes
Desc: image021.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170817/685ea795/attachment-0033.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image022.jpg
Type: image/jpeg
Size: 1240 bytes
Desc: image022.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170817/685ea795/attachment-0008.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image023.jpg
Type: image/jpeg
Size: 1309 bytes
Desc: image023.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170817/685ea795/attachment-0009.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image024.png
Type: image/png
Size: 2847 bytes
Desc: image024.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170817/685ea795/attachment-0034.png>
More information about the Equest-users
mailing list