[Equest-users] User Expressions in Schedules eQuest
Joel Travis
joel at andelmanlelek.com
Mon Feb 23 12:10:04 PST 2009
Todd,
This may be more than you bargained for but here is some sample INP code
that will achieve what you're looking for:
**
$ ---------------------------------------------------------
$ Global Parameters
$ ---------------------------------------------------------
PARAMETER
"setback_hr" = 6 ..
$ ---------------------------------------------------------
$ Day Schedules
$ ---------------------------------------------------------
" Sample_Cool_SB" = DAY-SCHEDULE-PD
TYPE = TEMPERATURE
VALUES = (
{if(0> parameter("setback_hr")) then 72 else 80 endif},
{if(1> parameter("setback_hr")) then 72 else 80 endif},
{if(2> parameter("setback_hr")) then 72 else 80 endif},
{if(3> parameter("setback_hr")) then 72 else 80 endif},
{if(4> parameter("setback_hr")) then 72 else 80 endif},
{if(5> parameter("setback_hr")) then 72 else 80 endif},
{if(6> parameter("setback_hr")) then 72 else 80 endif},
{if(7> parameter("setback_hr")) then 72 else 80 endif},
{if(8> parameter("setback_hr")) then 72 else 80 endif},
{if(9> parameter("setback_hr")) then 72 else 80 endif},
{if(10> parameter("setback_hr")) then 72 else 80 endif},
{if(11> parameter("setback_hr")) then 72 else 80 endif},
{if(12> parameter("setback_hr")) then 72 else 80 endif},
{if(13> parameter("setback_hr")) then 72 else 80 endif},
{if(14> parameter("setback_hr")) then 72 else 80 endif},
{if(15> parameter("setback_hr")) then 72 else 80 endif},
{if(16> parameter("setback_hr")) then 72 else 80 endif},
{if(17> parameter("setback_hr")) then 72 else 80 endif},
{if(18> parameter("setback_hr")) then 72 else 80 endif},
{if(19> parameter("setback_hr")) then 72 else 80 endif},
{if(20> parameter("setback_hr")) then 72 else 80 endif},
{if(21> parameter("setback_hr")) then 72 else 80 endif},
{if(22> parameter("setback_hr")) then 72 else 80 endif},
{if(23> parameter("setback_hr")) then 72 else 80 endif} )
..
This allows the schedule "Sample_Cool_SB" to be linked to whatever week and
annual schedule and it sets the daily hours less than 6am to be 80F and the
daily hours greater than 6am to be 72F.
To add an ending condition (reset back to 80 at 8pm), you would need a
second parameter and a second if loop for each hour to achieve this.
*Note - if you don't feel like touching the *.inp file, manually add the
parameter and then add each if statement to the respective hours in the day
schedule you want to change.
Cheers,
Joel Travis, LEED AP
Project Engineer
781-769-8773
1408 Providence Hwy
Norwood, MA 02062
joel at andelmanlelek.com
From: equest-users-bounces at lists.onebuilding.org
[mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of Todd Lagus
Sent: Monday, February 23, 2009 12:44 PM
To: equest-users at lists.onebuilding.org
Subject: [Equest-users] User Expressions in Schedules eQuest
Is there a way to modify day schedules using global parameters. For
example, say I want to compare the difference between having a setback start
at 6 pm instead of 10 pm. I know how to create two different schedules and
change them in the parametric run to get the difference.
However, let's say I want to use a single schedule to save time if I want to
run many different parametric runs. In pseudo code, I would say something
like-
Global parameter - Setback Hour (6 pm or 10 pm)
If time < "Setback Hour", then cooling setpoint is 72, else cooling setpoint
is 80
There would be a similar code to bring the setpoint back to occupied.
Is it at all possible to create a User expression in the schedules that
would to this? I could not find a keyword that corresponds to a time of
day, so I think this all may be in vain.
Thanks,
Todd
Todd Lagus, EIT
Mechanical Engineer
Sebesta Blomberg
sebesta.com | P 651.634.7236 | F 651.634.7400
This message has been sent via the Internet. Internet communications are not
secure against interception or modification. Sebesta Blomberg therefore can
not guarantee that this message has not been modified in transit. This
message and any files transmitted with it are confidential and intended
solely for the use of the addressee. If you have received this message in
error please notify the sender and destroy your copies of the message and
any attached files.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20090223/e8166189/attachment-0001.htm>
More information about the Equest-users
mailing list