[Bldg-sim] Importing a portion of one eQuest model intoanotherequest model

[Mark Nieman]

You can actually use the Import function in the File menu. It will ask
what *.inp file to import (needs to be done in Detailed Mode). If the
models were made in the SD Wizard, the last slide #41 has a field to
enter in a "Component Name Prefix" that you can tag components with
(i.e. F1 for floor 1 or whatever you like). Doing this prevents
components from colliding during the import process--much quicker than
merging the *.inp's manually! :-)
 

Mark Nieman, PE, CEM 
Sr. Energy Engineer 
McKinstry Essention 
Direct: (206) 832-8152 
Cell: (206) 510-4760 
FAX: (206) 832-8552 
http://www.mckinstry.com <http://www.mckinstry.com/>  
"For The Life Of Your Building" 

 

________________________________

From: bldg-sim-bounces at lists.onebuilding.org
[mailto:bldg-sim-bounces at lists.onebuilding.org] On Behalf Of Lynn
Qualmann
Sent: Thursday, January 10, 2008 1:22 PM
To: McCready, Jessica; bldg-sim at lists.onebuilding.org
Subject: Re: [Bldg-sim] Importing a portion of one eQuest model
intoanotherequest model



Jessica -

 

You can do this using the .inp files from the two models. If you have
some familiarity with the DOE2 building description language, you just
need to copy the portion(s) of the "from" file to the "to" file. I use
the word "just" advisedly because, depending on how much is to be
transferred and whether default naming schemes have been used, this can
become a fairly tedious process. You also have to take into
consideration all of the related portions of the contributing file. For
example, if you're adding a new zone, you need to be sure the associated
space is also entered, any applicable schedules are accounted for, etc.

 

Of course, the transferred information can be inserted into the
receiving file and it can replace portions of the receiving file.
Regardless, the final document will obviously have to adhere to all the
BDL requirements. You will find out if you have violated any BDL rules
when the BDL processor runs, but you may also have unintended errors
that do not violate any of those rules (e.g. incorrectly references to
schedules, circulations loops, whatever), so go through the added
portions carefully to make sure you are modeling what you intend.

 

Before undertaking this endeavor, BE SURE YOU HAVE A BACKUP of the
receiving file (I recommend backing up all the files associated with the
receiving model just to be sure you can restart if things don't go
well).

 

Good luck.

 

R. Lynn Qualmann, P.E.

SBW Consulting, Inc.

2820 Northup Way  #230

Bellevue, WA  98004

Phone:  (425) 827-0330

FAX:     (425) 822-8119

e-mail:  rlq at sbwconsulting.com

________________________________

From: bldg-sim-bounces at lists.onebuilding.org
[mailto:bldg-sim-bounces at lists.onebuilding.org] On Behalf Of McCready,
Jessica
Sent: Thursday, January 10, 2008 12:56 PM
To: bldg-sim at lists.onebuilding.org
Subject: [Bldg-sim] Importing a portion of one eQuest model into
anotherequest model

 

 

Hello and a happy new year to all. 

I am trying to import a portion of a building from one eQuest model into
another eQuest model. Is there a simple way of doing this that someone
can recommend? Or a manual you can refer me to that has this detail of
information?

Jessica E. McCready 
Energy Engineer 
KEMA Services Inc. 
492 Ninth Street, Suite 220 
Oakland, CA 94607 
T 510-891-0446 
F 510-891-0440 
jessica.mccready at kema.com 
Please visit our website www.kema.com <file:///\\www.kema.com>  


This email is the property of McKinstry or one of its affiliates and may contain confidential and/or privileged information. If you are not the intended recipient or have received this e-mail in error please notify the sender immediately and delete this e-mail. 
Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/bldg-sim-onebuilding.org/attachments/20080110/29983b4d/attachment-0002.htm>