[Equest-users] Parametric Runs with System Type Changes
Nicholas Caton
Nicholas.Caton at schneider-electric.com
Fri Feb 16 08:47:02 PST 2018
I think we’re on the same page.
There are multiple ways to skin this cat and arrive at the same correct end result, so what follows is just what I’d do intuitively as a general procedure:
* Finalize the following runs with your “base” project file
* Baseline
* Improve Envelope
* Improve Lighting Efficiency
* With each parametric building upon the last, use a copy of the “Improve Lighting Efficiency” run (which should end in “– 2.inp”) to generate your totally different HVAC state. This will be come your 2nd project file.
* Back in your “base” project file, your last parametric run for HVAC can enter “Run Based On:” as your lighting run, however tick the box for “based on separate building description” and select the .inp associated with the 2nd project file. This last parametric run doesn’t need any components. Something like this will work:
[cid:image001.png at 01D3A713.779B9AE0]
* Potential trip-ups:
* Be sure to choose an .inp which is >0kB when doing “based on separate building description”
* Be sure when generating a new project from a parametric .inp run that you set the weather file to the correct location – eQuest likes to assume California when not told otherwise and that has caused me to chase my tail more than once wondering how I saved a ton of energy!
In the end you’ll have all your parametric runs reporting together nicely in your SIM file, parametric reports and visuals.
~Nick
[cid:image002.png at 01D3A712.00C35E90]
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:image003.png at 01D3A712.00C35E90]
From: Welge, Sam [mailto:swelge at murphynet.com]
Sent: Friday, February 16, 2018 9:58 AM
To: Nicholas Caton <Nicholas.Caton at schneider-electric.com>
Cc: equest-users at onebuilding.org
Subject: RE: Parametric Runs with System Type Changes
Nick,
Thank you for the response. So my parametric runs look like this:
[cid:image007.png at 01D3A712.00C35E90]
I think what you are saying is that for Run #4 – Improved HVAC (this is actually a system change now); I will have the separate file with the different system and when creating the parametric run in there, point it to be “Based On” the input file from Run #2 – Improve Lighting Efficiency. Is that correct?
I was previously using Run #4 and having it do “Run Based on Separate Building Description…” and go to the file with the new HVAC system. Which then did not account for the previous changes (easy to notice in the lighting).
Thank you,
Sam
Sam Welge
Manager of Energy Solutions
MURPHY COMPANY, A Century of Solutions
Direct: 314-692-1162 | Main: 314-997-6600
Cell: 314-406-8828
E-Mail: swelge at murphynet.com<mailto:swelge at murphynet.com>
Website: www.murphynet.com<http://www.murphynet.com>
Follow us: [facebook] <https://www.facebook.com/MurphyCompanyMechanicalContractorandEngineers/> [Linked In] <https://www.linkedin.com/company/murphy-company> [Twitter] <https://twitter.com/_MurphCo>
From: Nicholas Caton [mailto:Nicholas.Caton at schneider-electric.com]
Sent: Thursday, February 8, 2018 12:02 PM
To: Welge, Sam
Cc: equest-users at onebuilding.org<mailto:equest-users at onebuilding.org>
Subject: RE: Parametric Runs with System Type Changes
Each time you execute a parametric simulation, an INP file is generated with the same label (number) in the directory containing the base project. Typically you’ll see something like the following in your project directory after a few simulations:
PROJECT_NAME.inp
PROJECT_NAME – Baseline Design.inp
PROJECT_NAME – 1.inp
PROJECT_NAME – 2.inp
etc…
You can point a parametric run to be based off of the inp with a label corresponding to the “final” parametric. That file should contain all of the cumulative parametric changes to the baseline model.
Does that help?
~Nick
[cid:image002.png at 01D3A712.00C35E90]
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:image003.png at 01D3A712.00C35E90]
From: Equest-users [mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of Welge, Sam via Equest-users
Sent: Wednesday, February 07, 2018 11:06 AM
To: equest-users at lists.onebuilding.org<mailto:equest-users at lists.onebuilding.org>
Subject: [Equest-users] Parametric Runs with System Type Changes
Hello all,
I am hoping someone can help me with this topic. I am using Parametric runs to make changes to a building’s envelope, insulation, etc. The last run I want to make is a system change, using a different file. When I do this, the final run is not based on the previous parametric runs, but rather reverts to the original baseline even though I have selected the run to be based on the final parametric. Do I have to input all parametric runs in both files in order to model the system change? Or is there a different way to do this?
Thank you,
Sam
Sam Welge
Manager of Energy Solutions
MURPHY COMPANY, A Century of Solutions
Direct: 314-692-1162 | Main: 314-997-6600
Cell: 314-406-8828
E-Mail: swelge at murphynet.com<mailto:swelge at murphynet.com>
Website: www.murphynet.com<http://www.murphynet.com>
Follow us: [facebook] <https://www.facebook.com/MurphyCompanyMechanicalContractorandEngineers/> [Linked In] <https://www.linkedin.com/company/murphy-company> [Twitter] <https://twitter.com/_MurphCo>
______________________________________________________________________
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/20180216/c3ee36dc/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 255 bytes
Desc: image002.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20180216/c3ee36dc/attachment-0028.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 8477 bytes
Desc: image003.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20180216/c3ee36dc/attachment-0029.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 35652 bytes
Desc: image007.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20180216/c3ee36dc/attachment-0030.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image008.png
Type: image/png
Size: 738 bytes
Desc: image008.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20180216/c3ee36dc/attachment-0031.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image009.png
Type: image/png
Size: 834 bytes
Desc: image009.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20180216/c3ee36dc/attachment-0032.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image010.png
Type: image/png
Size: 629 bytes
Desc: image010.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20180216/c3ee36dc/attachment-0033.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: oledata.mso
Type: application/octet-stream
Size: 7119 bytes
Desc: oledata.mso
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20180216/c3ee36dc/attachment-0004.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 12833 bytes
Desc: image001.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20180216/c3ee36dc/attachment-0034.png>
More information about the Equest-users
mailing list