[Equest-users] (no subject)

Fri Apr 28 08:22:45 PDT 2017

“Negative types?”  That’s a new one to me!

The expression I composed is working fine using version 3.65 build 7163, but I can recreate your error using build 7173.

Looks like the doe2 default within build 7173 looks like this – 2 things catch my eye:

if (#RV(#L("COGEN-TRACK-SCH")) == 0)
    then unused
    else #SIT("TRACK-ELEC","ELEC-METER","COGEN-TRACK-MODE",#L("TYPE"))
   endif

What’s #SIT?   Lo and behold there’s a new doe-2 reference manual entry explaining this is a thing now:
Volume 3: Topics > Building Description Language > Keyword Expressions > BDL Functions > SymIndexType or #SIT

Would you believe they use COGEN-TRACK-MODE as an example to explain this new(?) #SIT function?

On my first reading – it looks like #SIT is now supposed to be required of all “negative TYPE commands.”  ELEC-METER has been crowned one of those “negative TYPEs” for DOE-2.2/2.3.

Do I fully understand/appreciate why our expressions are now that much longer & more complex to type out?  No… No I do not… (it might take me a few more readings of that entry)... but in any case here’s a modified version for build 7173+ that looks to be in working order.  All I did was add that 4th argument and update #SI to #SIT:

if (#RV(#L("COGEN-TRACK-SCH")) == 0)
then unused
else switch(#PA("Tracking Mode"))
     case 1 : #SIT("DONT-RUN","ELEC-METER","COGEN-TRACK-MODE",#L("TYPE"))
     case 2 : #SIT ("TRACK-THERMAL","ELEC-METER","COGEN-TRACK-MODE",#L("TYPE"))
     case 3 : #SIT ("TRACK-LESSER","ELEC-METER","COGEN-TRACK-MODE",#L("TYPE"))
     case 4 : #SIT("TRACK-GREATER","ELEC-METER","COGEN-TRACK-MODE",#L("TYPE"))
     case 5 : #SIT("MAX-OUTPUT","ELEC-METER","COGEN-TRACK-MODE",#L("TYPE"))
     default : #SIT("TRACK-ELEC","ELEC-METER","COGEN-TRACK-MODE",#L("TYPE"))
     endswitch
endif

~Nick
[cid:image001.png at 01D2C009.5D02D0F0]
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 01D2C009.5D02D0F0]

From: siddharth patil [mailto:patilsiddharth5 at gmail.com]
Sent: Thursday, April 27, 2017 7:17 PM
To: Nicholas Caton <Nicholas.Caton at schneider-electric.com<mailto:Nicholas.Caton at schneider-electric.com>>
Subject: Re: [Equest-users] (no subject)

Thank you Nicholas for prompt reply.

I did that and encountered an error.

[Inline image 2]
[https://mailfoogae.appspot.com/t?sender=acGF0aWxzaWRkaGFydGg1QGdtYWlsLmNvbQ%3D%3D&type=zerocontent&guid=83c35b55-0e1a-4174-bc7f-acc90ac815c5]ᐧ

Siddharth S. Patil
Mechanical Engineer(MS)
Arizona State University,Tempe
Email: sspatil8 at asu.edu<mailto:sspatil8 at asu.edu>, patilsiddharth5 at gmail.com<mailto:patilsiddharth5 at gmail.com>
Contact: +1 (480)-465-1540

On Thu, Apr 27, 2017 at 4:46 PM, Nicholas Caton <Nicholas.Caton at schneider-electric.com<mailto:Nicholas.Caton at schneider-electric.com>> wrote:

1.       Create a global parameter – I chose to call it “Tracking Mode” and to use numeric values to toggle the setting.

[cid:image004.png at 01D2C009.5D02D0F0]

2.       Add an expression to the tracking mode dropdown in the meter(s) of interest by right-clicking and selecting the option in the context menu:

[cid:image005.png at 01D2C009.5D02D0F0]

3.       I used the doe2 default expression (what determines the green text) as the starting point, so if you opt to specify a tracking schedule of any kind this input will default to “n/a” (unused).  My additions to the default expression are highlighted for clarity, for anyone interested:

if (#RV(#L("COGEN-TRACK-SCH")) == 0)

then unused

else switch(#PA("Tracking Mode"))

     case 1 : #SI("DONT-RUN","ELEC-METER","COGEN-TRACK-MODE")

     case 2 : #SI("TRACK-THERMAL","ELEC-METER","COGEN-TRACK-MODE")

     case 3 : #SI("TRACK-LESSER","ELEC-METER","COGEN-TRACK-MODE")

     case 4 : #SI("TRACK-GREATER","ELEC-METER","COGEN-TRACK-MODE")

     case 5 : #SI("MAX-OUTPUT","ELEC-METER","COGEN-TRACK-MODE")

     default : #SI("TRACK-ELEC","ELEC-METER","COGEN-TRACK-MODE")

     endswitch

endif

4.       Now if in a parametric run you change the global parameter “Tracking Mode” to any of the values 1 through 5, it will switch the meter’s tracking mode to the corresponding setting in the highlighted switch statement above (i.e. 2 will result in the Track Thermal option):

[cid:image006.png at 01D2C009.5D02D0F0]

~Nick
[cid:image001.png at 01D2C009.5D02D0F0]
Nick Caton, P.E., BEMP
  Senior Energy Engineer
  Regional Energy Engineering Manager
  Energy and Sustainability Services
  Schneider Electric

D  913.564.6361<tel:(913)%20564-6361>
M  785.410.3317<tel:(785)%20410-3317>
F  913.564.6380<tel:(913)%20564-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 01D2C009.5D02D0F0]

From: Equest-users [mailto:equest-users-bounces at lists.onebuilding.org<mailto:equest-users-bounces at lists.onebuilding.org>] On Behalf Of siddharth patil via Equest-users
Sent: Thursday, April 27, 2017 5:25 PM
To: equest-users at lists.onebuilding.org<mailto:equest-users at lists.onebuilding.org>
Subject: [Equest-users] (no subject)

Hello, I am modeling PV system into my eQuest model. I want to run it over my baseline model and see how much savings I get. For this I am trying to set a global parameter or the command-keyword method for parametric run. How can I set a global parameter for Electric meter - Cogeneration - Track Mode parameter?

Thanks in advance!

Siddharth S. Patil

______________________________________________________________________
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/20170428/cd829388/attachment-0005.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/20170428/cd829388/attachment-0030.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/20170428/cd829388/attachment-0031.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 108928 bytes
Desc: image003.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170428/cd829388/attachment-0032.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 38186 bytes
Desc: image004.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170428/cd829388/attachment-0033.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 43968 bytes
Desc: image005.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170428/cd829388/attachment-0034.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 35285 bytes
Desc: image006.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20170428/cd829388/attachment-0035.png>