[Equest-users] Parametric Runs with System Type Changes

[Welge, Sam]

Nick,

Thank you for the response.  So my parametric runs look like this:

[cid:image001.png at 01D3A70C.50827750]

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
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
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 01D3A70C.50827750]
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 01D3A70C.50827750]



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.
______________________________________________________________________

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20180216/ada26491/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 35652 bytes
Desc: image001.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20180216/ada26491/attachment-0024.png>
-------------- 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/ada26491/attachment-0025.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/ada26491/attachment-0026.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 738 bytes
Desc: image004.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20180216/ada26491/attachment-0027.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 834 bytes
Desc: image005.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20180216/ada26491/attachment-0028.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 629 bytes
Desc: image006.png
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20180216/ada26491/attachment-0029.png>