[Equest-users] Keyword Expression question
David Reddy
david at 360-analytics.com
Fri Mar 16 13:55:11 PDT 2018
Christopher,
I think you are looking for
#SV(#L("TYPE"))==XX,
Where XX corresponds to the integer symbol value assigned in BDL.
BDLKEY.OUT is where you can find what the symbol values are for a given
keyword.
Here is the section for the SYSTEM:TYPE command/keyword:
1> TYPE Symbolic Defined 1 100
(CODE-WORD ) TABLE =0 1 -9 (* Required * )
SYMBOL TABLE ENTRY
PSZ TYPE = 100 DEF/REF -1/ -1 VALUE
= 19
SYMBOL TABLE ENTRY
PMZS TYPE = 100 DEF/REF -1/ -1 VALUE
= 20
SYMBOL TABLE ENTRY
PVAVS TYPE = 100 DEF/REF -1/ -1 VALUE
= 21
SYMBOL TABLE ENTRY
PVVT TYPE = 100 DEF/REF -1/ -1 VALUE
= 28
SYMBOL TABLE ENTRY
PTAC TYPE = 100 DEF/REF -1/ -1 VALUE
= 22
SYMBOL TABLE ENTRY
HP TYPE = 100 DEF/REF -1/ -1 VALUE
= 15
SYMBOL TABLE ENTRY
SZRH TYPE = 100 DEF/REF -1/ -1 VALUE
= 2
SYMBOL TABLE ENTRY
VAVS TYPE = 100 DEF/REF -1/ -1 VALUE
= 13
SYMBOL TABLE ENTRY
RHFS TYPE = 100 DEF/REF -1/ -1 VALUE
= 14
SYMBOL TABLE ENTRY
DDS TYPE = 100 DEF/REF -1/ -1 VALUE
= 4
SYMBOL TABLE ENTRY
MZS TYPE = 100 DEF/REF -1/ -1 VALUE
= 3
SYMBOL TABLE ENTRY
PIU TYPE = 100 DEF/REF -1/ -1 VALUE
= 23
SYMBOL TABLE ENTRY
FC TYPE = 100 DEF/REF -1/ -1 VALUE
= 9
SYMBOL TABLE ENTRY
IU TYPE = 100 DEF/REF -1/ -1 VALUE
= 11
SYMBOL TABLE ENTRY
UVT TYPE = 100 DEF/REF -1/ -1 VALUE
= 6
SYMBOL TABLE ENTRY
UHT TYPE = 100 DEF/REF -1/ -1 VALUE
= 7
SYMBOL TABLE ENTRY
HVSYS TYPE = 100 DEF/REF -1/ -1 VALUE
= 16
SYMBOL TABLE ENTRY
EVAP-COOL TYPE = 100 DEF/REF -1/ -1 VALUE
= 26
SYMBOL TABLE ENTRY
RESYS2 TYPE = 100 DEF/REF -1/ -1 VALUE
= 29
SYMBOL TABLE ENTRY
RESVVT TYPE = 100 DEF/REF -1/ -1 VALUE
= 27
SYMBOL TABLE ENTRY
RESYS TYPE = 100 DEF/REF -1/ -1 VALUE
= 17
SYMBOL TABLE ENTRY
SZCI TYPE = 100 DEF/REF -1/ -1 VALUE
= 5
SYMBOL TABLE ENTRY
CBVAV TYPE = 100 DEF/REF -1/ -1 VALUE
= 18
SYMBOL TABLE ENTRY
FPH TYPE = 100 DEF/REF -1/ -1 VALUE
= 8
SYMBOL TABLE ENTRY
PTGSD TYPE = 100 DEF/REF -1/ -1 VALUE
= 25
SYMBOL TABLE ENTRY
SUM TYPE = 100 DEF/REF -1/ -1 VALUE
= 1
SYMBOL TABLE ENTRY
FNSYS1 TYPE = 100 DEF/REF -1/ -1 VALUE
= 24
SYMBOL TABLE ENTRY
*UNUSED-TYPE1 TYPE = 100 DEF/REF -1/ -1 VALUE
= 10
SYMBOL TABLE ENTRY
*UNUSED-TYPE2 TYPE = 100 DEF/REF -1/ -1 VALUE
= 12
SYMBOL TABLE ENTRY
*SYS-30 TYPE = 100 DEF/REF -1/ -1 VALUE
= 30
SYMBOL TABLE ENTRY
*SYS-31 TYPE = 100 DEF/REF -1/ -1 VALUE
= 31
SYMBOL TABLE ENTRY
*SYS-32 TYPE = 100 DEF/REF -1/ -1 VALUE
= 32
On 3/16/2018 1:46 PM, Jones, Christopher via Equest-users wrote:
>
> Hello Expressionistas,
>
> Is there a simpler way to achieve #L("TYPE")==#SI("PSZ","SYSTEM","TYPE")
>
> I was thinking there would be a way to return the TYPE number, ie. PSZ
> = 19, PVAVS = 21, etc.
>
> **
>
> *Christopher R. Jones*, P.Eng.
>
> Technical Specialist
>
> Sustainability & Energy
>
> 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:* Thursday, March 15, 2018 3:13 PM
> *To:* Nicholas Caton <Nicholas.Caton at schneider-electric.com>; Daric
> Adair <Daric.Adair at hendersonengineers.com>; Jones, Christopher
> <Christopher.r.Jones at wsp.com>; John Aulbach <jra_sac at yahoo.com>
> *Cc:* equest-users at onebuilding.org
> *Subject:* RE: [Equest-users] eQuest Generated EFLH
>
> Oh and hey, you can simplify the process I outlined by striking out
> Step #2 entirely… Custom reporting on the submeter isn’t necessary to
> generate the submeter PS-F report, but again may be necessary to cover
> FLEH for schedules and processes that aren’t related by a MULTIPLIER
> or FRACTION type schedule.
>
> *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
>
> *From:*Equest-users
> [mailto:equest-users-bounces at lists.onebuilding.org] *On Behalf Of
> *Nicholas Caton via Equest-users
> *Sent:* Thursday, March 15, 2018 2:01 PM
> *To:* Daric Adair <Daric.Adair at hendersonengineers.com
> <mailto:Daric.Adair at hendersonengineers.com>>; Jones, Christopher
> <Christopher.r.Jones at wsp.com <mailto:Christopher.r.Jones at wsp.com>>;
> John Aulbach <jra_sac at yahoo.com <mailto:jra_sac at yahoo.com>>
> *Cc:* equest-users at onebuilding.org <mailto:equest-users at onebuilding.org>
> *Subject:* Re: [Equest-users] eQuest Generated EFLH
>
> Inserting a general caution on leveraging peaks with the suggested
> consumption/peak PS-F approach…
>
> You would need at least one hour in every fractional schedule at 1.0
> to fully trust using the peak to derive FLEH from a meter report.
> That has been the root source of many LEED comments making incorrect
> conclusions based on FLEH “margin math.” You will also need to be
> mindful that each sub-meter is only covering the effects of a single
> schedule to ensure “coincident peaks” aren’t being conflated with
> actual peaks under a given end-use (like where you have 4 lighting
> schedules), similarly messing with your math later.
>
> My concern with “tons of meters” vs. “tons of hourly reports” is that
> you’re kinda robbing Peter to pay Paul. It’s a lot of extra reporting
> and time spent parsing the outputs either way. My gut likes the
> **idea** of a custom hourly report approach more, as if you could
> construct a series of report blocks to replicate every schedule of
> interest, then you could do all the math in one output file,
> minimizing hours required for documentation and number-crunching. My
> concern however is I don’t think there’s a report block option that
> lets you simply select the hourly schedule value for just any
> schedule… You’ll need to do it indirectly…
>
>
> So… here’s an idea that might combine the best potential of both
> approaches while minimizing error potential:
>
> 0. Save a separate copy/fork of your model – you’ll want to retain
> this work for later but you won’t want it in your final model…
> unless you do some extra legwork to “toggle/flag” these dummy
> loads into activity.
> 1. Set up a dummy elec meter under EM1 with up to 12 schedules for
> which you need to document FLEH. Give each schedule a 1kW Load,
> and a unique enduse.
>
> 2. Copy the EM1 report block, and reassign it to your dummy meter.
> You might actually untick “total end-use energy” as the 13^th
> entry as that’ll be meaningless later.
>
> 3. Now, if you sum annual kWh for each end-use of the meter (handily
> done for you within the SIM PS-F reports), it’s equivalently the
> FLEH (if rounded to the nearest integer):
>
> 4. Set up additional sub-meters to cover schedules in multiples of 12
> until you’ve covered every schedule for which you need to document
> FLEH.
>
> This would only work for annual schedules of type FRACTION and
> MULTIPLIER. If they’re asking for something like system runtime hours
> or snap temp loop operations you’ll need to be running custom
> hourlies, but those could be set up alongside this custom reporting
> structure as needed.
>
> For what it’s worth, I haven’t submitted a project for LEED v4 review
> yet, and neither have I seen or reviewed the context under which they
> are asking for FLEH documentation, but I’d be inclined with my first
> project to instead take a minimal documentation0 approach on this
> front and have the reviewer ask in commentary specifically for what
> they really need. Requiring FLEH for *everything* crosses the line of
> silly from a (this) reviewers’ perspective.
>
> ~Nick
>
> *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
>
> *From:*Equest-users
> [mailto:equest-users-bounces at lists.onebuilding.org] *On Behalf Of
> *Daric Adair via Equest-users
> *Sent:* Thursday, March 15, 2018 9:27 AM
> *To:* Jones, Christopher <Christopher.r.Jones at wsp.com
> <mailto:Christopher.r.Jones at wsp.com>>; John Aulbach <jra_sac at yahoo.com
> <mailto:jra_sac at yahoo.com>>
> *Cc:* equest-users at lists.onebuilding.org
> <mailto:equest-users at lists.onebuilding.org>
> *Subject:* Re: [Equest-users] eQuest Generated EFLH
>
> Oh, I agree, it’s screwy reporting requirements.
>
> The hard thing is its by annual schedule. Not necessarily by fan
> system or all lighting.
>
> I means around thing might – might be to set the meters based on
> annual schedule. Then use the PS-F reports to take the
> consumption/peak to get the EFLH. That avoids a tons of hourly reports
> but uses potentially a lot of meters. Though, was hoping to avoid this.
>
> Thanks,
>
> *DARIC R ADAIR*PE, CEM, BEMP
> Mechanical Engineer, Energy Analyst
>
> *Henderson Engineers*
> *Tel* (913) 742-5530
> daric.adair at hendersonengineers.com
> <mailto:daric.adair at hendersonengineers.com>
>
> *Licensed in*KS
>
> *From:*Jones, Christopher [mailto:Christopher.r.Jones at wsp.com]
> *Sent:* Thursday, March 15, 2018 9:11 AM
> *To:* Daric Adair <Daric.Adair at hendersonengineers.com
> <mailto:Daric.Adair at hendersonengineers.com>>; John Aulbach
> <jra_sac at yahoo.com <mailto:jra_sac at yahoo.com>>
> *Cc:* equest-users at lists.onebuilding.org
> <mailto:equest-users at lists.onebuilding.org>
> *Subject:* RE: [Equest-users] eQuest Generated EFLH
>
> What is the EFLH for lighting controlled by photo sensors? Fans that
> have VSDs? Etc.? To get accurate EFLH you would need hourly reports.
>
> LEED has some really goofy reporting requirements.
>
> **
>
> *Christopher R. Jones*, P.Eng.
>
> Technical Specialist
>
> Sustainability & Energy
>
> 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
> *Daric Adair via Equest-users
> *Sent:* Thursday, March 15, 2018 9:45 AM
> *To:* John Aulbach <jra_sac at yahoo.com <mailto:jra_sac at yahoo.com>>;
> equest-users at lists.onebuilding.org
> <mailto:equest-users at lists.onebuilding.org>
> *Subject:* Re: [Equest-users] eQuest Generated EFLH
>
> John & all;
>
> That could work for the plant equipment, but LEEDv4 is requesting EFLH
> for all annual schedules. We have a project that has 4 different main
> occupancy times/groups. Which cascades out to occupancy, lighting,
> fans, etc. Many, many schedules.
>
> I received a separate suggestion to check under File>Export, but none
> of the 3 options there had anything like the EFLH.
>
> LEED has a ‘calculator’ in their documentation, but its built arround
> different days/week (which also don’t align in this project).
> Something could be built in excel to handle this – but I saw little
> need to recreate the wheel if eQuest/DOE2 does this automatically.
>
> Thanks,
>
> *DARIC R ADAIR*PE, CEM, BEMP
> Mechanical Engineer, Energy Analyst
>
> *Henderson Engineers*
> *Tel* (913) 742-5530
> daric.adair at hendersonengineers.com
> <mailto:daric.adair at hendersonengineers.com>
>
> *Licensed in*KS
>
> *From:*John Aulbach [mailto:jra_sac at yahoo.com]
> *Sent:* Wednesday, March 14, 2018 7:52 PM
> *To:* equest-users at lists.onebuilding.org
> <mailto:equest-users at lists.onebuilding.org>
> *Subject:* Re: [Equest-users] eQuest Generated EFLH
>
> My best guess (assuming you want cooling for example) is to make a
> single chiller for your building (gotta be PLANT equipment). Figure
> out the peak cooling load from SS-D and size the chiller accordingly.
> Run the building. Look in PS-C, with 10% increments of load.
>
> Multiply each 10% load increment (say chiller is 1000 ton, so 100 tons
> for 10%, 200 tons for 20%, etc) by the number of hours shown for that
> increment. Take the total ton-hrs and divide by the 1000 ton (for this
> example).
>
> That should give you equivalent load hours.
>
> John Aulbach, PE
>
> On Wednesday, March 14, 2018, 2:27:48 PM PDT, Daric Adair via
> Equest-users <equest-users at lists.onebuilding.org
> <mailto:equest-users at lists.onebuilding.org>> wrote:
>
> Does anyone know if there is a report or means from eQuest to generate
> the EFLH (equivalent full load hours) for each schedule?
>
> Colleague of mine believes VistualDOE was able to complete and hoping
> there is a comparable tool/report.
>
> Thanks in advance.
>
> Thanks,
>
> *DARIC R ADAIR* PE, CEM, BEMP
> Mechanical Engineer, Energy Analyst
>
> *Henderson Engineers*
> 8345 Lenexa Drive, Suite 300 | Lenexa, KS 66214
> *Tel* (913) 742-5530
> daric.adair at hendersonengineers.com
> <mailto:daric.adair at hendersonengineers.com>
>
> hendersonengineers.com <http://www.hendersonengineers.com/>
>
> *Licensed in*KS
>
> *Sending me large files? Please use Henderson File Share
> <https://apps.hendersonengineers.com/FileShare/Upload?to=daric.adair@hendersonengineers.com>
> | TX ID #F-001236*
>
> ------------------------------------------------------------------------
>
>
> This email and any files transmitted with it are confidential and are
> intended solely for the use of the individual or entity to whom they
> are addressed. This communication represents the originator's personal
> views and opinions, which do not necessarily reflect those of
> Henderson Engineers, Inc. If you are not the original recipient or the
> person responsible for delivering the email to the intended recipient,
> be advised that you have received this email in error, and that any
> use, dissemination, forwarding, printing, or copying of this email is
> strictly prohibited. If you received this email in error, please
> immediately notify administrator at hendersonengineers.com
> <mailto:administrator at hendersonengineers.com>.
>
> _______________________________________________
> 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
> <mailto:EQUEST-USERS-UNSUBSCRIBE at ONEBUILDING.ORG>
>
> ------------------------------------------------------------------------
>
>
> This email and any files transmitted with it are confidential and are
> intended solely for the use of the individual or entity to whom they
> are addressed. This communication represents the originator's personal
> views and opinions, which do not necessarily reflect those of
> Henderson Engineers, Inc. If you are not the original recipient or the
> person responsible for delivering the email to the intended recipient,
> be advised that you have received this email in error, and that any
> use, dissemination, forwarding, printing, or copying of this email is
> strictly prohibited. If you received this email in error, please
> immediately notify administrator at hendersonengineers.com
> <mailto:administrator at hendersonengineers.com>.
>
> ------------------------------------------------------------------------
>
>
>
> NOTICE: This communication and any attachments ("this message") may
> contain information which is privileged, confidential, proprietary or
> otherwise subject to restricted disclosure under applicable law. This
> message is 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 or intended 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.
> 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 at 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. Note that not all messages sent by WSP qualify as commercial
> electronic messages.
>
> AVIS : Ce message, incluant tout fichier l'accompagnant (« le message
> »), peut contenir des renseignements ou de l'information privilégiés,
> confidentiels, propriétaires ou à divulgation restreinte en vertu de
> la loi. Ce message est destiné à l'usage exclusif du/des
> destinataire(s) voulu(s). Toute utilisation non permise, divulgation,
> lecture, reproduction, modification, diffusion ou distribution est
> interdite. Si vous avez reçu ce message par erreur, ou que vous n'êtes
> pas un destinataire autorisé ou voulu, veuillez en aviser l'expéditeur
> immédiatement et détruire le message et toute copie électronique ou
> imprimée. 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 au www.wsp.com/lcap
> <http://www.wsp.com/lcap>. 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. Notez que ce ne sont pas
> tous les messages transmis par WSP qui constituent des messages
> electroniques commerciaux.
>
>
>
> -LAEmHhHzdJzBlTWfa4Hgs7pbKl
>
> ------------------------------------------------------------------------
>
>
> This email and any files transmitted with it are confidential and are
> intended solely for the use of the individual or entity to whom they
> are addressed. This communication represents the originator's personal
> views and opinions, which do not necessarily reflect those of
> Henderson Engineers, Inc. If you are not the original recipient or the
> person responsible for delivering the email to the intended recipient,
> be advised that you have received this email in error, and that any
> use, dissemination, forwarding, printing, or copying of this email is
> strictly prohibited. If you received this email in error, please
> immediately notify administrator at hendersonengineers.com
> <mailto:administrator at hendersonengineers.com>.
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> ______________________________________________________________________
>
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> ______________________________________________________________________
>
>
>
> _______________________________________________
> 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/20180316/2e968bd0/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 25844 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20180316/2e968bd0/attachment.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/20180316/2e968bd0/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 8477 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20180316/2e968bd0/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 34745 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20180316/2e968bd0/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 43716 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20180316/2e968bd0/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 6644 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20180316/2e968bd0/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.jpg
Type: image/jpeg
Size: 11638 bytes
Desc: not available
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20180316/2e968bd0/attachment.jpg>
More information about the Equest-users
mailing list