[Equest-users] User-Defined Default Expressions
Michael Campbell via Equest-users
equest-users at lists.onebuilding.org
Wed Mar 8 13:51:11 PST 2017
Ok, to follow up on my last e-mail...
I was able to get it to work but I'm still not sure where the error is in
the expression that i posted.
On Wed, Mar 8, 2017 at 4:19 PM, Michael Campbell <mcamp1206 at gmail.com>
wrote:
> OK, I am now trying to create a default expression for occupancy schedule
> and I am running into more issues.
> I used the same statement from my lighting schedule but here I am getting
> an error "UNKNOWN KEYWORD or PREVIOUS .. MISSING"
>
> Here is my expression I am using:
>
> SET-DEFAULT FOR SPACE
> PEOPLE-SCHEDULE = (
> {switch(Local("C-ACTIVITY-DESC",0)+Local("C-ACTIVITY-DESC",1))
> case "Apartmen" : #SI("ASHRAE MultiFam Occ Sched", "SPACE",
> "PEOPLE-SCHEDULE")
> default : no_default
> endswitch
> } )
>
> I must be missing something because it seems to me like this should work
> the same as it did for the lighting schedule.
>
> Thank you,
>
> On Tue, Mar 7, 2017 at 2:35 PM, Michael Campbell <mcamp1206 at gmail.com>
> wrote:
>
>> Ok - I am now trying to set up default expressions to auto-populate 2nd,
>> 3rd, 4th, and 5th values for plug loads.
>>
>> I have the following which is working for inputting the plug load
>> schedule in EQUIP-SCHEDULE 1, but how can I specify the equipment schedule
>> for Equipment Load #2/3/4/5?
>>
>> I've tried using the BDLDFT document as reference but was unable to get
>> anything to work.
>>
>> EQUIP-SCHEDULE = (
>> {switch(Local("C-ACTIVITY-DESC",0)+Local("C-ACTIVITY-DESC",1))
>> case "Apartmen" : #SI("ESMFHR Unit Eqp Sched", "SPACE", "EQUIP-SCHEDULE")
>> default : #SI("ESMFHR Non-Res Eqp Sched", "SPACE", "EQUIP-SCHEDULE")
>> endswitch
>> } )
>>
>> Thank you,
>>
>> On Fri, Mar 3, 2017 at 6:41 PM, Nicholas Caton <
>> Nicholas.Caton at schneider-electric.com> wrote:
>>
>>> Stop asking me hard questions! It’s a Friday!
>>>
>>>
>>>
>>> If I had to guess I would likely credit David Reddy & the rest of crew
>>> at 360 Analytics… but honestly I can’t recall (could have been you,
>>> Bill?).
>>>
>>>
>>>
>>> More constructively and to your point however, this optional argument
>>> however is what the doe2 reference manual is generally referring to when it
>>> lists “i" or “i1, i2” in its syntax / explanations of the BDL functions.
>>> Example:
>>>
>>>
>>>
>>>
>>>
>>> These inputs can become very important if you are trying to set up user
>>> defaults for, say, the 2nd or 3rd plug load entries. Study the doe2
>>> defaults expressions in that area for further reference material. That’s
>>> how the 3rd inputs know to be “n/a” before you entered at least the 1st
>>> and 2nd entries for a given field.
>>>
>>>
>>>
>>> ~Nick
>>>
>>>
>>>
>>> *Nick Caton, P.E., BEMP*
>>>
>>> Senior Energy Engineer
>>> Regional Energy Engineering Manager
>>>
>>> Energy and Sustainability Services
>>> Schneider Electric
>>>
>>> D 913.564.6361 <(913)%20564-6361>
>>> M 785.410.3317 <(785)%20410-3317>
>>> F 913.564.6380 <(913)%20564-6380>
>>> E nicholas.caton at schneider-electric.com
>>>
>>> 15200 Santa Fe Trail Drive
>>> Suite 204
>>> Lenexa, KS 66219
>>> United States
>>>
>>>
>>>
>>>
>>>
>>> *From:* Bishop, Bill [mailto:bbishop at pathfinder-ea.com]
>>> *Sent:* Friday, March 03, 2017 3:14 PM
>>> *To:* Nicholas Caton <Nicholas.Caton at schneider-electric.com>; Chris
>>> Jones <Christopher.Jones at RWDI.com>; Michael Campbell <
>>> mcamp1206 at gmail.com>
>>>
>>> *Cc:* equest-users at onebuilding.org
>>> *Subject:* RE: [Equest-users] User-Defined Default Expressions
>>>
>>>
>>>
>>> Nick,
>>>
>>> Where did you find that little gem of BDL?
>>>
>>> ~Bill
>>>
>>>
>>>
>>> *From:* Nicholas Caton [mailto:Nicholas.Caton at schneider-electric.com
>>> <Nicholas.Caton at schneider-electric.com>]
>>> *Sent:* Friday, March 03, 2017 4:04 PM
>>> *To:* Bishop, Bill <bbishop at pathfinder-ea.com>; Chris Jones <
>>> Christopher.Jones at RWDI.com>; Michael Campbell <mcamp1206 at gmail.com>
>>> *Cc:* equest-users at onebuilding.org
>>> *Subject:* RE: [Equest-users] User-Defined Default Expressions
>>>
>>>
>>>
>>> Appending to this, while ("C-ACTIVITY-DESC") returns the first 4
>>> characters by default, if you ever need to further distinguish inputs
>>> within spaces sharing the same/similar activity descriptors, you can also
>>> reference the 2nd set of 4 characters (or the 3rd set, or the 4th set…).
>>>
>>>
>>>
>>> To do this, append the optional argument “,#” wherever you’d normally
>>> specify “C-ACTIVITY-DESC.”
>>>
>>>
>>>
>>> To build on the running example, say you had 2 tenants to distinguish in
>>> a building with “Retail” space, but they had two different occupancy
>>> densities. You could handle that by first adding to their descriptors,
>>> such as follows:
>>>
>>> Retail_–_Best Buy
>>>
>>> Retail_–_Home Depot
>>>
>>>
>>>
>>> The first 4 characters for each case are the same: “RETA” (list
>>> position 0). The second set of 4 is “IL_–“ (list position 1). The third
>>> set is finally distinguishable: “_BES” and “_HOM” (list position 2).
>>>
>>>
>>>
>>> From here you could either insert an if/then statement for the “Reta”
>>> case, or just nest another switch statement. Added some formatting for
>>> clarity, but highlighted the new addition:
>>>
>>>
>>>
>>> AREA/PERSON =
>>>
>>> {if(#SV(#L("ZONE-TYPE"))==2) then no_def else
>>>
>>> if(#RV(#L("PEOPLE-SCHEDULE"))!=0) then unused else
>>>
>>> switch (#L("C-ACTIVITY-DESC"))
>>>
>>> case "Reta": switch (#L("C-ACTIVITY-DESC",2))
>>>
>>> case “_Bes” : 67
>>>
>>> case “_Hom” : 67*2
>>>
>>> default : 500
>>>
>>> endswitch
>>>
>>> case "Lobb": 150
>>>
>>> case "Clas": 100
>>>
>>> default: 500
>>>
>>> endswitch
>>>
>>> endif
>>>
>>> endif}
>>>
>>>
>>>
>>> ~Nick
>>>
>>>
>>>
>>> *Nick Caton, P.E., BEMP*
>>>
>>> Senior Energy Engineer
>>> Regional Energy Engineering Manager
>>>
>>> Energy and Sustainability Services
>>> Schneider Electric
>>>
>>> D 913.564.6361 <(913)%20564-6361>
>>> M 785.410.3317 <(785)%20410-3317>
>>> F 913.564.6380 <(913)%20564-6380>
>>> E nicholas.caton at schneider-electric.com
>>>
>>> 15200 Santa Fe Trail Drive
>>> Suite 204
>>> Lenexa, KS 66219
>>> United States
>>>
>>>
>>>
>>>
>>>
>>> *From:* Equest-users [mailto:equest-users-bounces at lists.onebuilding.org
>>> <equest-users-bounces at lists.onebuilding.org>] *On Behalf Of *Bishop,
>>> Bill via Equest-users
>>> *Sent:* Friday, March 03, 2017 12:24 PM
>>> *To:* Chris Jones <Christopher.Jones at RWDI.com>; Michael Campbell <
>>> mcamp1206 at gmail.com>
>>> *Cc:* equest-users at onebuilding.org
>>> *Subject:* Re: [Equest-users] User-Defined Default Expressions
>>>
>>>
>>>
>>> Mike,
>>>
>>> You can start with the expression below. Paste only the text between the
>>> brackets if you are pasting within the interface. If pasting into the input
>>> file, this would go after “SET-DEFAULT FOR SPACE”. Like Chris said, the
>>> case statement names should be four characters or less. However, they are
>>> not case sensitive, so upper/lower case doesn’t matter.
>>>
>>> ~Bill
>>>
>>>
>>>
>>> AREA/PERSON =
>>>
>>> {if(#SV(#L("ZONE-TYPE"))==2) then no_def else
>>>
>>> if(#RV(#L("PEOPLE-SCHEDULE"))!=0) then unused else
>>>
>>> switch (#L("C-ACTIVITY-DESC"))
>>>
>>> case "Reta": 67
>>>
>>> case "Lobb": 150
>>>
>>> case "Clas": 100
>>>
>>> default: 500
>>>
>>> endswitch
>>>
>>> endif
>>>
>>> endif}
>>>
>>>
>>>
>>> *William Bishop, PE, BEMP, BEAP, CEM, LEED AP **|** Pathfinder
>>> Engineers & Architects LLP*
>>>
>>> *Senior Energy Engineer*
>>>
>>>
>>>
>>>
>>>
>>> 134 South Fitzhugh Street Rochester, NY 14608
>>>
>>> *T: (585) 698-1956 <(585)%20698-1956>* F: (585)
>>> 325-6005
>>>
>>> bbishop at pathfinder-ea.com <wbishop at pathfinder-ea.com>
>>> www.pathfinder-ea.com
>>>
>>> [image: 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
>>> <equest-users-bounces at lists.onebuilding.org>] *On Behalf Of *Chris
>>> Jones via Equest-users
>>> *Sent:* Friday, March 03, 2017 12:52 PM
>>> *To:* Michael Campbell <mcamp1206 at gmail.com>
>>> *Cc:* equest-users at onebuilding.org
>>> *Subject:* Re: [Equest-users] User-Defined Default Expressions
>>>
>>>
>>>
>>> Note, only the first 4 characters of the C-ACTIVITY-DESC field are
>>> recognized in user defined expressions. Therefore, if your UDF uses
>>> “RETAIL” as the test, it may fail because only “RETA” is used.
>>>
>>>
>>>
>>> Other than that, I suggest reviewing the BDLDFT.TXT file in the eQUEST
>>> 3-65 Data folder. It is full of example default expressions.
>>>
>>>
>>>
>>>
>>>
>>> [image: Title: RWDI - Description: RWDI logo]
>>> <http://www.rwdi.com/assets/logos/RWDI-logo.gif>
>>>
>>> *Christopher Jones, **P.Eng. *| Senior Energy Analyst
>>> *RWDI*
>>> 901 King Street West, Suite 400, Toronto, ON M5V 3H5 Canada
>>> Tel: (519) 823-1311 ext 2052 <(519)%20823-1311>
>>> rwdi.com <http://www.rwdi.com/>
>>>
>>>
>>>
>>>
>>>
>>> *From:* Equest-users [mailto:equest-users-bounces at lists.onebuilding.org
>>> <equest-users-bounces at lists.onebuilding.org>] *On Behalf Of *Michael
>>> Campbell via Equest-users
>>> *Sent:* Friday, March 03, 2017 12:32 PM
>>> *To:* equest-users
>>> *Subject:* [Equest-users] User-Defined Default Expressions
>>>
>>>
>>>
>>> Hi eQUEST Users,
>>>
>>> I'm trying to create default user expressions in an effort to
>>> auto-populate certain fields in my models.
>>>
>>> I want to reference the activity description (C-ACTIVITY-DESC) have it
>>> automatically fill in fields such as Area/Person.
>>>
>>> So for this example, I'm trying to make all spaces that have Activity
>>> Description of "RETAIL" to be populated with a Area/Person value of 67.
>>>
>>> I've tried using the "Switch" function and if-then statements but
>>> haven't been able to get it to work.
>>>
>>> Any assistance is appreciated.
>>>
>>> Thank you,
>>>
>>> Mike Campbell
>>> ------------------------------
>>>
>>> *RWDI - A Platinum Member of Canada's 50 Best Managed Companies*
>>> This communication is intended for the sole use of the party to whom it
>>> was addressed and may contain information that is privileged and/or
>>> confidential. Any other distribution, copying or disclosure is strictly
>>> prohibited. If you received this email in error, please notify us
>>> immediately by replying to this email and delete the message without
>>> retaining any hard or electronic copies of same. Outgoing emails are
>>> scanned for viruses, but no warranty is made to their absence in this email
>>> or attachments. If you require any information supplied by RWDI in a
>>> different format to facilitate accessibility, contact the sender of the
>>> email, email solutions at rwdi.com or call +1.519.823.1311
>>> <(519)%20823-1311>.
>>> ------------------------------
>>>
>>>
>>> ______________________________________________________________________
>>> This email has been scanned by the Symantec Email Security.cloud service.
>>> ______________________________________________________________________
>>>
>>>
>>> ______________________________________________________________________
>>> 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/20170308/0016bd38/attachment-0005.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.jpg
Type: image/jpeg
Size: 1240 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170308/0016bd38/attachment-0015.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 255 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170308/0016bd38/attachment-0020.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 2227 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170308/0016bd38/attachment-0016.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 2844 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170308/0016bd38/attachment-0021.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 9020 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170308/0016bd38/attachment-0022.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 8477 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170308/0016bd38/attachment-0023.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.jpg
Type: image/jpeg
Size: 1309 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170308/0016bd38/attachment-0017.jpg>
More information about the Equest-users
mailing list