Nice idea, <span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">Otto Schwieterman!</span><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br>
</span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;">I like your post but until now I have only merge inp file by the function of "import" in eQuest, which will be very useful when a huge building or a group of buildings are modeled.</span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse; "><u>Tips:</u></span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><u><br></u></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><u>At the model beginning, all of the shell and air-side system need to be specified to make sure there will no duplicate name for any component in the model. This is not hard: just edit it in wizard model, both the shell and system. And also make sure the coordination is also correct with the real design. </u></span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><u><br></u></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><u>There will be a most probability of duplicate name in water-side, so if the models do not share the same chilled / domestic / hot water loop, rename all of water side staff before merging the inp files.</u></span></font></div>
<div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><u><br></u></span></font></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><u>Before the merging, my suggestion is that editing or testing or debugging the model first, otherwise you will find that after merging the model becomes huge, very long time to run, and hard to edit, test, debug.</u></span><br>
</font><br></div><div>That's my tips ( not small ;) ), any corrections are welcome.</div><div><br></div><div>Regards,</div><div><br></div><div>Grammy</div><div><br><div class="gmail_quote">On Wed, Jan 12, 2011 at 6:48 AM, Nick Caton <span dir="ltr"><<a href="mailto:ncaton@smithboucher.com">ncaton@smithboucher.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="color:#1F497D">Great tip (and nice model)!
</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">The ability to turn on/off 3D
view surfaces is something I often catch myself forgetting when it could save
me time – it’s also something I wish I knew about for my first few tricky
models =).</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">A related timesaver/accuracy note
comes to mind from a question brought up recently on the lists: </span></p>
<p><span style="color:#1F497D"><span>-<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="color:#1F497D">A great/quick way to
check and correct if exterior roof/floor surfaces are defined (incorrectly) in-between
separate & stacked shells from the wizards is to go to the same location
and turn off all items except Roofs and Floors. You can then quickly identify,
highlight and remove any unwanted surfaces.</span></p>
<p><span style="color:#1F497D"><span>-<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="color:#1F497D">I might
intentionally do this in my own models when I have unique roofs on multiple
levels and will plan to remove the unwanted “sandwiched” surfaces
once in detailed in this fashion. </span></p>
<p><span style="color:#1F497D"><span>-<span style="font:7.0pt "Times New Roman"">
</span></span></span><span style="color:#1F497D">Notice how if you
hold ctrl to rotate/zoom the model, a reference wireframe pops up which can
make it easy to verify where such surfaces should/shouldn’t be located.
You don’t need to move the mouse for a quick reference.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">I like the idea of “share
a quick timesaver/accuracy tip” – hope this picks up!</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">~Nick </span></p>
<div>
<p class="MsoNormal"><span style="color:#1F497D"><img width="119" height="37" src="?ui=2&ik=7bdefaa71a&view=att&th=12d7744a7ed84bae&attid=0.0.1&disp=emb&zw" alt="cid:489575314@22072009-0ABB"></span><b><span style="color:#2D4D5E"></span></b></p>
<p class="MsoNormal"><b><span style="color:#2D4D5E"> </span></b></p>
<p class="MsoNormal"><b><span style="color:#2D4D5E">NICK CATON, E.I.T.</span></b><b><span style="font-size:12.0pt;color:#2D4D5E"></span></b></p>
<p class="MsoNormal"><span style="font-size:7.5pt;color:#CC9900">PROJECT ENGINEER</span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">Smith &
Boucher Engineers</span><span style="font-size:7.5pt;font-family:"Times New Roman","serif";color:#CC9900"></span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">25501 west
valley parkway</span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">olathe ks 66061</span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">direct 913
344.0036</span></p>
<p class="MsoNormal"><span style="font-size:10.0pt;color:#2D4D5E">fax 913
345.0617</span></p>
<p class="MsoNormal"><span style="color:#1F497D"><a href="http://www.smithboucher.com" title="blocked::www.smithboucher.com" target="_blank"><span style="font-size:10.0pt">www.smithboucher.com</span></a></span><u><span style="font-size:10.0pt;color:blue"> </span></u><span style="color:#1F497D"></span></p>
</div>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:10.0pt">From:</span></b><span style="font-size:10.0pt"> <a href="mailto:equest-users-bounces@lists.onebuilding.org" target="_blank">equest-users-bounces@lists.onebuilding.org</a>
[mailto:<a href="mailto:equest-users-bounces@lists.onebuilding.org" target="_blank">equest-users-bounces@lists.onebuilding.org</a>] <b>On Behalf Of </b>Otto
Schwieterman<br>
<b>Sent:</b> Tuesday, January 11, 2011 3:34 PM<br>
<b>To:</b> <a href="mailto:equest-users@lists.onebuilding.org" target="_blank">equest-users@lists.onebuilding.org</a><br>
<b>Subject:</b> [Equest-users] eQUEST Tips</span></p>
</div>
</div><div><div></div><div class="h5">
<p class="MsoNormal"> </p>
<p class="MsoNormal"><span style="color:#1F497D">I would like to start a
discussion about tips on how to create a better energy model with less time.
This is an easy example but it does save time if you currently do not turn off
the components.</span></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal">To make it easier to delete the extra exterior walls that are
created between shells in eQUEST, go to the Project Properties and remove the
roofs, ceilings and interior <span style="color:#1F497D">walls.</span></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><img border="0" width="624" height="412" src="?ui=2&ik=7bdefaa71a&view=att&th=12d7744a7ed84bae&attid=0.0.2&disp=emb&zw"></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><img border="0" width="624" height="338" src="?ui=2&ik=7bdefaa71a&view=att&th=12d7744a7ed84bae&attid=0.0.3&disp=emb&zw"></p>
<p class="MsoNormal"><span style="color:#1F497D"> </span></p>
<p class="MsoNormal"><span style="color:#1F497D">Otto</span></p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"> </p>
<pre>________________________________________________________________________________________</pre><pre>Fanning/Howey Associates, Inc. intends to send this transmission (including any attachments) only to the</pre><pre>designated individual or entity. If you received this message in error, please notify the sender by replying</pre>
<pre>to the electronic mail (if electronic) or by telephone at the number indicated on this document.</pre><pre>Fanning/Howey Associates, Inc. has taken reasonable precautions to ensure no viruses are present in the</pre>
<pre>electronic mail. Fanning/Howey Associates, Inc., will not accept responsibility for any loss or damage arising</pre><pre>from the use of this electronic mail or attachments. Use, disclosure, dissemination, distribution, or reproduction</pre>
<pre>of this message by unintended recipients is not authorized and maybe unlawful. Any information included in</pre><pre>this transmission that is not related to contracts with our authorization, verbal or written, by Fanning/Howey</pre>
<pre>Associates, Inc. may not be covered by our professional liability insurance. </pre><pre> </pre></div></div></div>
</div>
<br>_______________________________________________<br>
Equest-users mailing list<br>
<a href="http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org" target="_blank">http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org</a><br>
To unsubscribe from this mailing list send a blank message to <a href="mailto:EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG">EQUEST-USERS-UNSUBSCRIBE@ONEBUILDING.ORG</a><br>
<br></blockquote></div><br></div>