I am attempting to turn on/off daylighting control in a large model via a user expression, referencing a global parameter.
I have read the "Topics" entry on syntax for expressions, but I'm still stuck. Here's my entry (in the "DAYLIGHTING" field)
if (#PA("InclDaylight")==1)
then ("Yes")
else ("No")
endif
I have tried a number of formulations; the error message I get each time is
[cid:image003.jpg at 01CD5546.0C4A9AE0]
Any advice?
Aaron Dahlstrom , PE, LEED(r) AP
In Posse - A subsidiary of AKF| 1500 Walnut Street, Suite 1414, Philadelphia, PA 19102
d: 215-282-6753| m: | In Posse: 215-282-6800| AKF: 215-735-7290
e: ADahlstrom at in-posse.com | in posse web: www.in-posse.com
This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unintended recipients are prohibited from taking action on the basis of information in this e-mail. E-mail messages may contain computer viruses or other defects, may not be accurately replicated on other systems, or may be intercepted, deleted or interfered without the knowledge of the sender or the intended recipient. If you are not comfortable with the risks associated with e-mail messages, you may decide not to use e-mail to communicate with In Posse.
You could turn off the daylighting parametrically without using global parameters - why wouldn't you do it that way?
Vikram Sami, LEED AP BD+C
I have 300 zones in my model; not all perimeter zones will receive daylighting.
Doing it in detailed data interface allows me to see the zone I'm picking and cross-verify.
Doing in it Parametric Run components would require me to distinguish between zones in a list.
A matter of convenience, I guess, since it is technically possible to do as you say.
Aaron
Aaron Dahlstrom , PE, LEED(r) AP
...
then #si("YES","SPACE","DAYLIGHTING")
else #si("NO","SPACE","DAYLIGHTING")
endif
... anytime you are trying to set a keyword with a symbolic data type,
you must use the SymbolIndex() or #si() function. Symbolic keywords are
those that take text inputs, either as a user defined command such as a
schedule (e.g. SPACE:LIGHTING-SCHEDUL) or a BDL pre-defined symbol (e.g.
SPACE:DAYLIGHTING or SYSTEM:OA-CONTROL)
You also have to make sure you are using the proper DOE-2 symbol value,
not the eQUEST detailed interface value. To identify the correct DOE-2
symbol value you can usually right click and look at the DOE-2 item help
for that keyword and it will show you the valid inputs. Or, look at the
.inp file and see what actually shows up for the input to a particular
symbolic keyword.
Have fun.
- Kevin
Kevin Madison PE
Beat me to it... here's an alternative.
If you set your global parameter to symbolic you can use this at the daylight dropdown:
#SI(#PA("GLOBAL PARAMETER NAME"),"SPACE","DAYLIGHTING")
Your parameter becomes "YES" or "NO".
-Dana
Dana Etherington, LEED AP BD+C
Aaron,
The global parameter does not need to be a number. It can be a symbol, like "Yes" or "No" in the case of daylighting. You need to use the SymIndex function. See Parametric Example 4 (pp. 5.15-5.21) in the Modeling Procedures Quick Reference. Click on "Help," then "Tutorials and Reference," then "Modeling Procedures Quick Reference (pdf)."
[cid:image003.jpg at 01CD55FE.FA256020]
The basic format is SymIndex(parameter("Parameter Name"),"A","B")
where "A" is the BDL command and "B" is the BDL keyword. These things can be found by right-clicking on the field of interest and selecting "View Default/Range..."
[cid:image007.jpg at 01CD55FE.FA256020]
The command and keyword are given at the top.
[cid:image008.jpg at 01CD55FE.FA256020]
Keith Swartz, PE, LEED AP