I missed you guys and I feel like sharing - NAME as BDL function argument?

4 posts / 0 new
Last post

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

via Equest-users's picture
Joined: 2016-07-15
Reputation: 400

Paging Scott Criswell???

I think we might on the verge of learning something here...

Why does this work for a ZONE input (even when OA-FROM-SYSTEM is not present):
if(#PS()==#SI("Sys1","SYSTEM","OA-FROM-SYSTEM"))
then 2
else 1
endif
...And this does not work, resulting in the following error?
if(#PS()==#SI("Sys1","SYSTEM","TYPE"))
then 2
else 1
endif
[cid:image010.png at 01D3174F.28EAAD40]

Similarly, the following expression does *not* work for a SPACE input, returning the same error ("BDL symbol not found")... but perhaps some keyword other than POLYGON *would* work?
if(#PS()==#SI("1STFLOORNAME","FLOOR","POLYGON"))
then 1.85
else 1.50
endif
[cid:image011.png at 01D3174F.28EAAD40]

And since we're posing questions nobody may have a ready answer to... shouldn't *all* of the above examples for #SI be able to function without a command/keyword pair? If this isn't a bug that's readily-fixable within the next eQUEST release, would someone consider updating the doe2 reference manual to at least strike out those false options (and maybe even add some working examples)?
[cid:image012.png at 01D31750.AEE93D20]

[cid:image001.png at 01D3174D.682DD0B0]
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

15200 Santa Fe Trail Drive
Suite 204
Lenexa, KS 66219
United States

[cid:image002.png at 01D3174D.682DD0B0]

via Equest-users's picture
Joined: 2016-07-15
Reputation: 400

Nick,
The first expression works because OA-FROM-SYSTEM is one of the few (only?) keywords for which a system NAME is a valid argument. You get an error in the second case because "Sys1" is not a system TYPE. The second expression will "work" (not cause an error) if you replace "Sys1" with "PSZ" but it doesn't do what you want it to do.

~Bill

via Equest-users's picture
Joined: 2016-07-15
Reputation: 400

Ahhh...

So if FLOORs had an keyword accepting the U-name of another FLOOR as a valid input (in the fashion OA-FROM-SYSTEM does, uniquely), then SPACE expressions allowing for FLOOR identification via #PS()==#SI() would be a possibility.

But they don't, so we can't. =/

That ties this up pretty neatly though, and I did learn something!

Thanks,

~Nick

[cid:image001.png at 01D3175D.7935E950]
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

15200 Santa Fe Trail Drive
Suite 204
Lenexa, KS 66219
United States

[cid:image002.png at 01D3175D.7935E950]

via Equest-users's picture
Joined: 2016-07-15
Reputation: 400