<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:x =
"urn:schemas-microsoft-com:office:excel" xmlns:p =
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a =
"urn:schemas-microsoft-com:office:access" xmlns:dt =
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s =
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs =
"urn:schemas-microsoft-com:rowset" xmlns:z = "#RowsetSchema" xmlns:b =
"urn:schemas-microsoft-com:office:publisher" xmlns:ss =
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c =
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc =
"urn:schemas-microsoft-com:office:odc" xmlns:oa =
"urn:schemas-microsoft-com:office:activation" xmlns:html =
"http://www.w3.org/TR/REC-html40" xmlns:q =
"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc =
"http://microsoft.com/officenet/conferencing" XMLNS:D = "DAV:" XMLNS:Repl =
"http://schemas.microsoft.com/repl/" xmlns:mt =
"http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2 =
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda =
"http://www.passport.com/NameSpace.xsd" xmlns:ois =
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir =
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds =
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp =
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc =
"http://schemas.microsoft.com/data/udc" xmlns:xsd =
"http://www.w3.org/2001/XMLSchema" xmlns:sub =
"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec =
"http://www.w3.org/2001/04/xmlenc#" xmlns:sp =
"http://schemas.microsoft.com/sharepoint/" xmlns:sps =
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs =
"http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf =
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p =
"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf =
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss =
"http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi =
"http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi =
"http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver =
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels =
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp =
"http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t =
"http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m =
"http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl =
"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl =
"http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService"
XMLNS:Z = "urn:schemas-microsoft-com:" xmlns:st = ""><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.5848" name=GENERATOR>
<STYLE>@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Arial Narrow;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
LI.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
DIV.MsoNormal {
FONT-SIZE: 11pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Calibri","sans-serif"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: "Calibri","sans-serif"; mso-style-type: personal-compose
}
.MsoChpDefault {
mso-style-type: export-only
}
DIV.Section1 {
page: Section1
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=EN-US vLink=purple link=blue>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2>
<DIV><FONT color=#0000ff size=2><FONT color=#000000 size=3><FONT
face=Arial><SPAN class=551334819-15092009><FONT color=#0000ff
size=2>eQuesters,</FONT></SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT color=#0000ff size=2><FONT color=#000000 size=3><FONT
face=Arial><SPAN
class=551334819-15092009></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT color=#0000ff size=2><FONT color=#000000 size=3><FONT
face=Arial><SPAN class=551334819-15092009> <FONT
color=#0000ff size=2>Some of you might recall the e-mails (below, but probably
not necessary to re-read) from early August. Since then, my problem
has simplified, but the solution is not so clear to
me.</FONT></SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT color=#0000ff size=2><FONT color=#000000 size=3><FONT
face=Arial><SPAN class=551334819-15092009> <FONT
color=#0000ff size=2>Basically, I have exhaust fans for a particular shell
located in a "core" zone made of restrooms and an electrical
room. No supply or return air devices exist in this core zone.
Rather, the core zone gets its air from transfer through doorways (and maybe one
passive transfer duct) from a large open office zone. (Note: Insofar
as the core zone does not have an HVAC system, per se, Vikram's excellent
previous answer seems inapplicable
now.)</FONT></SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT color=#0000ff size=2><FONT color=#000000 size=3><FONT
face=Arial><SPAN class=551334819-15092009> <FONT color=#0000ff
size=2>Here are the questions:</FONT></SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=551334819-15092009>1. When using eQuest, shall I deem the core zone
"unconditioned" or "plenum" or "conditioned"?</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=551334819-15092009>2. What HVAC system, if any, shall I tell eQuest
that the core zone belongs to? Is there even a way, if appropriate, to
tell eQuest that a zone does not belong to an HVAC system?</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=551334819-15092009>3. How can I explain to eQuest that the office
zone exhausts (passively) to the core zone, which then exhausts via fans to the
outside?</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=551334819-15092009> Thank you all in advance for your
help - and to Vikram for his previous response.</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=551334819-15092009></SPAN></FONT> </DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=551334819-15092009>Lars
Fetzek, EI</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=551334819-15092009>Phoenix Engineering Group</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN class=551334819-15092009>Tampa,
Florida</SPAN></FONT></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=551334819-15092009></SPAN></FONT> </DIV>
<DIV><FONT color=#0000ff size=2><FONT color=#000000 size=3><FONT
face=Arial><SPAN
class=551334819-15092009></SPAN></FONT></FONT></FONT> </DIV>
<DIV><FONT color=#0000ff size=2><FONT color=#000000 size=3><FONT
face=Arial><SPAN class=551334819-15092009> </SPAN>Lars,<BR><BR>Not sure if
this is what you're looking to do. I haven't tried this for<BR>a chain of more
than two zones, but you can specify the outside air<BR>coming from a particular
zone in eQUEST using the "OA-FROM-SYSTEM"<BR>keyword. You have to be careful
with this to define the OA system before<BR>the system it feeds (i.e. if system
1 has an OA-FROM system2, but system<BR>2 has not been defined yet in the INP
file, you will get an error. <BR><BR><BR><BR>Another thing to watch out for is
that when you use the OA-FROM, I don't<BR>think eQUEST calculates the cooling
effect of the ventilation air. You<BR>might have to trick the program into
accounting for that using an<BR>internal energy source (process) with a negative
value. This is easier<BR>with a constant volume OA supply, but if you really
want to you could<BR>write a schedule for the VAV supply - it's pretty tricky.
<BR><BR><BR><BR>Vikram Sami, LEED AP <BR>Direct Phone 404-253-1466 | Direct Fax
404-253-1366 <BR><BR>LORD, AECK & SARGENT
ARCHITECTURE<BR><BR><BR><BR><BR><BR>From: </FONT></FONT><A
title=http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org
href="BLOCKED::http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org"><FONT
title=http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org
face=Arial size=3>equest-users-bounces at
lists.onebuilding.org</FONT></A><BR><FONT face=Arial color=#000000
size=3>[mailto:</FONT><A
title=http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org
href="BLOCKED::http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org"><FONT
title=http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org
face=Arial size=3>equest-users-bounces at lists.onebuilding.org</FONT></A><FONT
face=Arial color=#000000 size=3>] On Behalf Of Lars<BR>Fetzek<BR>Sent: Monday,
August 10, 2009 9:47 AM<BR>To: </FONT><A
title=http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org
href="BLOCKED::http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org"><FONT
title=http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org
face=Arial size=3>equest-users at lists.onebuilding.org</FONT></A><BR><FONT
face=Arial color=#000000 size=3>Subject: [Equest-users] Exhaust air
routes<BR><BR><BR><BR>Hello,<BR><BR><BR><BR> The building
floor that I am presently modeling has several<BR>conditioned zones and two
unconditioned zones. The conditioned zones<BR>are various offices.
The unconditioned zones are restrooms and an<BR>electrical room. The
conditioned zones exhaust to each other and,<BR>ultimately, to the unconditioned
zones via hallways, doorways, etc. The<BR>unconditioned zones exhaust to
the outside (via fans).<BR><BR> How can I explain to eQuest
that, for example, conditioned zone A<BR>exhausts to conditioned zone B?
Also, how can I explain to eQuest that<BR>conditioned zone D exhausts X% to the
electrical room (and thus to<BR>outdoor exhaust fans) and Y% to conditioned zone
C?<BR><BR> In case it matters, the ceiling is open and the
return ductwork<BR>terminates in one spot. Accordingly, even return air
must flow among<BR>the conditioned zones.<BR><BR> Thanks, as
always, for your helpful replies.<BR><BR><BR><BR>Lars Fetzek, EI<BR><BR>Phoenix
Engineering Group<BR><BR>Tampa, Florida<BR></DIV></FONT></FONT></FONT></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Lars Fetzek [mailto:lfetzek@phoenixeng.us]
<BR><B>Sent:</B> Tuesday, September 15, 2009 3:36 PM<BR><B>To:</B> 'Bach Tsan';
'equest-users@lists.onebuilding.org'<BR><B>Subject:</B> RE: [Equest-users]
Input/Schedules/Unused parameters ;what is ok to delete?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=ltr align=left><SPAN class=810563319-15092009><FONT face=Arial
color=#0000ff size=2>Bach,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=810563319-15092009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=810563319-15092009> <FONT
face=Arial color=#0000ff size=2>Yes, I have. However, the technique is
beyond explanation. Just trial-and-error, using the DOE2-2 dictionary, and
gradually learning and torchering yourself will lead you to successful .inp
editing. Nobody can really teach or explain this.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=810563319-15092009><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=810563319-15092009><FONT face=Arial
color=#0000ff size=2>Lars Fetzek, EI</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=810563319-15092009><FONT face=Arial
color=#0000ff size=2>Phoenix Engineering Group</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=810563319-15092009><FONT face=Arial
color=#0000ff size=2>Tampa, Florida</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> equest-users-bounces@lists.onebuilding.org
[mailto:equest-users-bounces@lists.onebuilding.org] <B>On Behalf Of </B>Bach
Tsan<BR><B>Sent:</B> Wednesday, August 19, 2009 11:58 AM<BR><B>To:</B>
equest-users@lists.onebuilding.org<BR><B>Subject:</B> [Equest-users]
Input/Schedules/Unused parameters ;what is ok to delete?<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal>Hello fellow equest users,<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>I was wondering if anyone has tried to clear out all unused
parameters prior to running the equest model?<o:p></o:p></P>
<P class=MsoNormal>I notice that the software “loads” all the schedules and
parameters; and if deleting them in the .inp file would speed things up.
<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>I tried it with a default sample model, but got various
errors since some items are required for the model to run. Has anyone generated
a script to run to clear all unnecessary items before running the
model?<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Thanks<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal><B><SPAN
style="COLOR: black; FONT-FAMILY: 'Arial Narrow','sans-serif'">Bach Tsan PE,
LEED AP</SPAN></B><SPAN
style="COLOR: black; FONT-FAMILY: 'Arial Narrow','sans-serif'"><o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="COLOR: black; FONT-FAMILY: 'Arial Narrow','sans-serif'"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><o:p> </o:p></P></DIV></BODY></HTML>