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
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.
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
I need to follow up on my previous e-mail re: importing a portion of one
eQuest model into another. Cutting and pasting between *.inp files can
work, but you need to be careful to get all the pertinent information.
There are so many possibilities of what is intended that it is beyond my
resources and knowledge to begin addressing even a small portion of
them. As Mark points out, an entire model can be incorporated into
another model with the import function. If the intent is to create a
campus situation, this works just fine. If the intent is to end up with
a single building (i.e. the two parts are meant to have thermal
connections via internal surfaces), I don't think importing alone will
provide that functionality. Depending on the intentions of the modeling
effort, you may be able to omit any common surfaces from the thermal
model if conditions are essentially the same on both sides and
reflectivity is not an issue for potential daylighting.
If the concept is to "plug" a space from one building into a second
building, to the best of my knowledge you will be in for a grueling
battle (unless the two models are of the same building and the space to
be imported has the same geometry and location as that of the space
being replaced - in which case I would recommend just changing the
features of the existing space to mimic the desired space). I have
wrestled with locating spaces in an existing model in Detailed Design
mode and trust me, it is neither fun nor sufficiently rewarding.
Hopefully you have enough information to accomplish what you want
without falling into any traps.
R. Lynn Qualmann, P.E.