[Equest-users] Copy Parametric Runs Between Models

[Nick Caton]

I think I tried a simple copy/paste at one point and found it didn't
work initially - I speculate there's some trigger in the .pd2 file or
elsewhere that tells eQuest you have a .prd to be looking for at all (it
doesn't just know)... you might need to open the model first and create
a "dummy" .prd by saving a single parametric item you won't be using
before trying the copy/paste/rename approach?

 

If anyone can patch together a brief "how-to" for cleanly "importing"
parametric .prd items, it would be much appreciated =).  Until now, I
haven't given the idea much thought, and I'm curious if others have
added this strategy to their modeling toolbox as a timesaving
venture...?

 

~Nick

 

 

 

NICK CATON, P.E.

SENIOR ENGINEER

 

Smith & Boucher Engineers

25501 west valley parkway, suite 200

olathe, ks 66061

direct 913.344.0036

fax 913.345.0617

www.smithboucher.com 

 

From: equest-users-bounces at lists.onebuilding.org
[mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of Paul
Riemer
Sent: Friday, June 24, 2011 9:51 AM
To: 'Brian Fountain'; Jonathan Smith
Cc: equest-users at lists.onebuilding.org
Subject: Re: [Equest-users] Copy Parametric Runs Between Models

 

Agreed.  It can be carried from project to project and even edited as
text file, though you have to infer the syntax.  I don't simply drop an
old one into a new project, I create a parametric run in the target
project and then replace it with the prd file from the source project.
I recall hitting snags if the projects were from different eQUEST
versions or in trying to change a subset of something rather than all of
the instances (to which Brian alluded).  A fix is have the moved PRD
file change all of something (i.e. all windows) and then open the new
project and revisit the checkbox list in the parametric run dialogue
(i.e. check only south windows).

 

Back up your files and give it a try, starting with the something simple
like building azimuth rotation. 

 

Paul Riemer, PE, LEED AP 

DUNHAM

 

From: equest-users-bounces at lists.onebuilding.org
[mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of Brian
Fountain
Sent: Friday, June 24, 2011 9:31 AM
To: Jonathan Smith
Cc: equest-users at lists.onebuilding.org
Subject: Re: [Equest-users] Copy Parametric Runs Between Models

 

It is the .prd file which is a text file that defines parametric runs.

The answer to whether it can be copied to other models -- the answer is
a very cautious yes.   You simply rename the old .prd file with the new
project name and pow, you have a series of parametric runs to start with
in the new model.  However, parametric runs use the u-value names to
identify model components to be changed.  Thus, as long as your zone
names or AHU names or whatever are the same, then, yes, you could use
the .prd file from one model to another.  However, as you can imagine --
once things change, it is very challenging to realign them.

Good luck.

On 6/24/2011 10:21 AM, Jonathan Smith wrote: 

Which file contains the script for the parametric runs? 

Can the parametric scripts be copied in a text editor from one model to
another?

 

Jonathan R. Smith AIA LEED(r)AP

 

 

40 Beaver Street
Albany, New York 12207
p: 518.463.8068 x268
f: 518.463.8069 
www.csarchpc.com <http://www.csarchpc.com/> 

 

 
 
_______________________________________________
Equest-users mailing list
http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org
To unsubscribe from this mailing list send  a blank message to 
EQUEST-USERS-UNSUBSCRIBE at ONEBUILDING.ORG





No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1388 / Virus Database: 1513/3723 - Release Date: 06/24/11

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20110624/88055a6d/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1459 bytes
Desc: image002.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20110624/88055a6d/attachment.jpeg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 11096 bytes
Desc: image003.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20110624/88055a6d/attachment-0001.jpeg>