<BODY contentEditable=true onload=parent.init()><P></P>
<P style="LINE-HEIGHT: normal; MARGIN: 0in 0in 8.1pt" class=MsoNormal><SPAN style="COLOR: black; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin"><FONT face=Calibri>Nick,<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /><o:p></o:p></FONT></SPAN></P>
<P style="LINE-HEIGHT: normal; MARGIN: 0in 0in 8.1pt" class=MsoNormal><SPAN style="COLOR: black; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin"><FONT face=Calibri>I inserted <SPAN style="mso-spacerun: yes"> </SPAN>“DIAGNOSTIC<SPAN style="mso-spacerun: yes"> </SPAN>ERRORS<SPAN style="mso-spacerun: yes"> </SPAN>WARNINGS<SPAN style="mso-spacerun: yes"> </SPAN>..”<SPAN style="mso-spacerun: yes"> </SPAN>into the “.inp” file it is ignored when eQUEST runs it.<SPAN style="mso-spacerun: yes"> </SPAN>It works with DOE21E. <o:p></o:p></FONT></SPAN></P>
<P style="LINE-HEIGHT: normal; MARGIN: 0in 0in 8.1pt" class=MsoNormal><SPAN style="COLOR: black; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin"><FONT face=Calibri>Varkie<o:p></o:p></FONT></SPAN></P>
<P style="LINE-HEIGHT: normal; MARGIN: 0in 0in 8.1pt" class=MsoNormal><SPAN style="COLOR: black; FONT-SIZE: 14pt; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin"><STRONG><FONT face=Calibri>eQUEST Issues<o:p></o:p></FONT></STRONG></SPAN></P>
<P style="LINE-HEIGHT: normal; MARGIN: 0in 0in 8.1pt" class=MsoNormal><SPAN style="COLOR: black; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin"><FONT face=Calibri>The advantage of creating the Building and Spaces in eQUEST by tracing ACAD drawings is nullified by what eQUEST does next.<SPAN style="mso-spacerun: yes"> </SPAN>In fact to custom build your project using what you see on the drawings, schedules and specifications is next to impossible.<SPAN style="mso-spacerun: yes"> </SPAN>You spend a couple of hours building the architectural model (which can take days with other programs) and then weeks fixing to display what you want so that you can understand what’s going on in the reports.<o:p></o:p></FONT></SPAN></P>
<P style="LINE-HEIGHT: normal; MARGIN: 0in 0in 8.1pt" class=MsoNormal><FONT face=Calibri><SPAN><FONT color=firebrick><STRONG>The attached 7-Zone typical-floor high-rise building is an example</STRONG>.</FONT> It took a few minutes to create the model and a few days to make it look like what’s in the construction documents.<SPAN style="mso-spacerun: yes"> </SPAN>It was done global-replace in DOE22 using a text editor.<SPAN style="mso-spacerun: yes"> </SPAN>The Ground and Top floors were removed.<SPAN style="mso-spacerun: yes"> </SPAN>The process has to repeated several times because you can’t get it right the first time.<SPAN style="mso-spacerun: yes"> </SPAN>The attached example changed all the eQUEST names and defaults and the OA-FROM-SYSTEM feature.<SPAN style="mso-spacerun: yes"> </SPAN><STRONG><FONT color=firebrick>There are no CAUTION or WARNING messages.<SPAN style="mso-spacerun: yes"> </SPAN>
I must have created it several months ago using eQUEST 3.61</FONT>.</STRONG></SPAN><SPAN style="COLOR: black; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin"><o:p></o:p></SPAN></FONT></P>
<P style="LINE-HEIGHT: normal; MARGIN: 0in 0in 8.1pt" class=MsoNormal><SPAN style="COLOR: black; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin"><FONT face=Calibri>eQUEST assumes default values and design decisions for different types of Buildings Spaces, <SPAN style="mso-spacerun: yes"> </SPAN>Zones, Systems & Plants, Schedules, and Constructions.<SPAN style="mso-spacerun: yes"> </SPAN>It also assigns its own names to all these components.<SPAN style="mso-spacerun: yes"> </SPAN>It creates Schedules and Constructions for every Space and its Walls & Windows.<SPAN style="mso-spacerun: yes"> </SPAN>This is for every Shell.<SPAN style="mso-spacerun: yes"> </SPAN>In the case of Infiltration there is one the Perimeter and one for the Core of each type-of-Space of in each Shell.<SPAN style="mso-spacerun: yes">
</SPAN>For Shells/Floors with 3 or more floors, eQUEST creates a Ground, Middle and Top for these 3 identical Floors/Spaces and creates new Walls, Windows, Schedules, and Constructions.<SPAN style="mso-spacerun: yes"> </SPAN>I don’t think I have covered all the unnecessary repetitions by eQUEST.<o:p></o:p></FONT></SPAN></P>
<P style="LINE-HEIGHT: normal; MARGIN: 0in 0in 8.1pt" class=MsoNormal><FONT face=Calibri><SPAN style="COLOR: black; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin">In the case of typical floors of a high rise bldg (eQ default = high-rise, 8 floors or more) there is no Ground or Top.<SPAN style="mso-spacerun: yes"> </SPAN>Below the Ground there is always another floor (underground floors, Lobby, Retail, etc).<SPAN style="mso-spacerun: yes"> </SPAN>Typically above the Top floor there is another floor such as a Mechanical.</SPAN><SPAN style="COLOR: #999999; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin"><o:p></o:p></SPAN></FONT></P>
<P style="LINE-HEIGHT: normal; MARGIN: 0in 0in 8.1pt" class=MsoNormal><FONT face=Calibri><SPAN style="COLOR: black; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin">In the case of large projects the results of every zone and system has to be examined to make sure that there were no accidental input errors. If a zone result does not look right based on engineering experience, then the sub-components must be checked. If this does not produce a satisfactory answer then it is possible to examine the hourly values of a variable in the case of the DOE2 based programs. There are no “Check” figures in the DOE2 reports such as btu/sf, cfm/sf and sf/ton.</SPAN>
<SPAN style="COLOR: #999999; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin"><o:p></o:p></SPAN></FONT></P>
<P style="LINE-HEIGHT: normal; MARGIN: 0in 0in 8.1pt" class=MsoNormal><FONT face=Calibri><SPAN style="COLOR: black; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin">It is difficult and tedious to recognize every layer, construction, schedule, zone and system name assumed by eQUEST and change them to the ones you see on the drawings. Some projects have over 1000 zones and nearly 100 systems. The project cannot be broken up into smaller pieces because it affects the demand cost and there is still only one plant. The user should be able to enter the names of every component as with DOE2.2. </SPAN><SPAN style="COLOR: #999999; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin"><o:p></o:p></SPAN></FONT></P>
<P style="LINE-HEIGHT: normal; MARGIN: 0in 0in 8.1pt" class=MsoNormal><FONT face=Calibri><SPAN style="COLOR: black; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin">The result of all this is several pages of indecipherable text. Except for plant and economics reports, it is difficult to check the other reports. eQUEST allows you to use your own names when you create building shell components and air side system types. However, it is not appear anywhere else except in DD wizard where you created it. The reports do not show these names. </SPAN><SPAN style="COLOR: #999999; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin"><o:p></o:p></SPAN></FONT></P>
<P style="LINE-HEIGHT: normal; MARGIN: 0in 0in 8.1pt" class=MsoNormal><FONT face=Calibri><SPAN style="COLOR: black; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin">The eQUEST program assumes all the “design-criteria” given building and component type and we have to check each form and cell to see what was assumed. It should show, the default, minimum and maximum values for the cell entry and the user should be able to enter the value. A document listing the defaults, minimum, maximum values (like the DOE21E BDL Summary document) and other assumptions will be helpful. The “Activity Areas Allocation” form should allow the creation of user </SPAN>
<SPAN style="mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin">named activity instead of having to use “Unknown”.<o:p></o:p></SPAN></FONT></P>
<P style="LINE-HEIGHT: normal; MARGIN: 0in 0in 8.1pt" class=MsoNormal><SPAN style="mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin"><FONT face=Calibri>One of the best features is being able to trace AutoCAD drawings to create shells, floor plans, zones, and spaces and check that is done right by viewing it in 2D and 3D.<SPAN style="mso-spacerun: yes"> </SPAN>It can only be done SD and DD.<SPAN style="mso-spacerun: yes"> </SPAN>Entering the details and replacing all the eQUEST given names and assumptions to match the drawings, schedules and specifications have to be done Detailed Edit (DE).<SPAN style="mso-spacerun: yes"> </SPAN>The spreadsheets are convenient for this. You cannot go back to DD from DE without losing all the information created in DE.<SPAN style="mso-spacerun: yes"> </SPAN>
During the design process the architectural plans change frequently.<SPAN style="mso-spacerun: yes"> </SPAN>You cannot make these changes without starting all over again.<o:p></o:p></FONT></SPAN></P>
<P style="LINE-HEIGHT: normal; MARGIN: 0in 0in 8.1pt" class=MsoNormal><SPAN style="mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin"><FONT face=Calibri>I<SPAN style="COLOR: black"> tried creating DOE2.1E and eQUEST models of a 50 zone project but because of the numerous default values and assumptions made by eQUEST (even with building type = Unknown) and the difficulty of fixing every design criteria value and schedule to match client specifications, it is difficult to get the results of DOE2.1E and eQUEST to match. It took a day to create DOE21E model using my own component names a data. It took several days to create the same model by changing the eQUEST names and defaults to match the names and values in the construction drawings, schedules and specifications. See project "High-Rise Mixed-Use Bldg"</SPAN>
<SPAN style="COLOR: #999999"><o:p></o:p></SPAN></FONT></SPAN></P>
<P style="LINE-HEIGHT: normal; MARGIN: 0in 0in 8.1pt" class=MsoNormal><FONT face=Calibri><SPAN style="COLOR: black; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin"> In the case of such large projects with 100 or more zones, it helps to first create Master (or Global as in TRACE which can be used on all projects) and Project (created by editing a copy of Master) data for different types of Buildings, Zones, Systems & Plants, first. Individual Spaces, Zones and assumes the master and change only what is different from the Project. This can be done with most programs such as TRACE and even the APEC MEP programs that were first developed in the 1960s. </SPAN>
<SPAN style="COLOR: #999999; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin"><o:p></o:p></SPAN></FONT></P>
<P style="LINE-HEIGHT: normal; MARGIN: 0in 0in 8.1pt" class=MsoNormal><FONT face=Calibri><SPAN style="COLOR: black; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin">In the case of DOE2.1E the Master, Project and Component override can done with design criteria assignments under PARAMETER, then with commands and keywords such “Space-Type1-Name” = SPACE-CONDITIONS, “Zone-Type1-Name” = ZONE- (CONTROL, AIR, FANS), “System-Type1-Name”<SPAN style="mso-spacerun: yes"> </SPAN>= SYSTEM- (CONTROL, AIR,-FANS, TERMINAL, FLUID, EQUIPMENT), PLANT- (PARAMETERS), etc, . SET-DEFAULT-FOR-SPACE (WALL, WINDOW, ZONE, SYSTEM, etc) in DOE21E also exist in DOE22.<SPAN style="mso-spacerun: yes"> </SPAN>The Min-Max range and Default is published in the manuals and BDL Summary for DOE21E but not for DOE22. </SPAN>
<SPAN style="COLOR: #999999; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin"><o:p></o:p></SPAN></FONT></P>
<P style="LINE-HEIGHT: normal; MARGIN: 0in 0in 8.1pt" class=MsoNormal><SPAN style="COLOR: black; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin"><FONT face=Calibri>I have created and saved a library of design standards for different types Spaces, Zones, Systems, Plant equipment and Rate structures (for different Utilities) with DOE21E - BDL.<SPAN style="mso-spacerun: yes"> </SPAN>I edit them for new projects and copy and paste into the new project. It can be done in DOE22 also and used as templates (libraries) that can be copied into other projects. But when eQUEST reads the “.ip” file, it scrambles the BDL and scatters it all over the place.<SPAN style="mso-spacerun: yes"> </SPAN>
This is particularly annoying with Schedules associated with Utility Rates which are separated from the Utility BDL and placed in another place and separated again by Day, Week and Annual.<SPAN style="mso-spacerun: yes"> </SPAN>It is difficult to assemble all this again and use it on another project.<o:p></o:p></FONT></SPAN></P>
<P style="LINE-HEIGHT: normal; MARGIN: 0in 0in 8.1pt" class=MsoNormal><SPAN style="COLOR: black; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin"><FONT face=Calibri>The Loads, Systems and Plant are in separate time loops in DOE21E.<SPAN style="mso-spacerun: yes"> </SPAN>This very convenient in the case of large project where you run the sections independently and check the results before going on to the next section.<SPAN style="mso-spacerun: yes"> </SPAN>In DOE22 the Loads, Systems and Plant are in same time loop.<SPAN style="mso-spacerun: yes"> </SPAN>The real-time theoretical accuracy of this on a real project is insignificant.<o:p></o:p></FONT></SPAN></P>
<P style="LINE-HEIGHT: normal; MARGIN: 0in 0in 8.1pt" class=MsoNormal><SPAN style="COLOR: black; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin"><FONT face=Calibri>eQUEST defaults assume that building construction, operation and use in Iceland is exactly the same as in Madagascar.<o:p></o:p></FONT></SPAN></P>
<P style="LINE-HEIGHT: normal; MARGIN: 0in 0in 8.1pt" class=MsoNormal><SPAN style="COLOR: black; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin"><FONT face=Calibri>I don’t think eQUEST has an advantage over DOE21E but that can be easily changed.<SPAN style="mso-spacerun: yes"> </SPAN>The obstacle is that developers and users of the program feel very satisfied with the “ergonomics” of the program.<o:p></o:p></FONT></SPAN></P>
<P style="LINE-HEIGHT: normal; MARGIN: 0in 0in 8.1pt" class=MsoNormal><SPAN style="COLOR: #999999; mso-ascii-font-family: Calibri; mso-ascii-theme-font: minor-latin; mso-fareast-font-family: 'Times New Roman'; mso-hansi-font-family: Calibri; mso-hansi-theme-font: minor-latin"><o:p><FONT face=Calibri> </FONT></o:p></SPAN></P>
<P>
<P><B></B> </P>
<P><B>----- Original Message -----</B> </P>
<P></P></P><B>From</B>: Nick Caton <ncaton@smithboucher.com>
<P></P><B>Date</B>: Monday, July 19, 2010 9:28 am
<P></P><B>Subject</B>: RE: [Equest-users] CAUTION and WARNING Messages
<P></P>
<P></P>> Varkie, <BR>> <BR>> <BR>> <BR>> If it’s any consolation, I’ve dug deep at this CAUTION and come up <BR>> with little. There’s an extended discussion between myself and <BR>> others on the list trying to determine the root of these FPLR <BR>> cautions, but to the best of my knowledge it’s a mystery. I can <BR>> say these cautions appear erroneous, as the CFM’s modeled by the <BR>> corresponding fans appear to remain within expected ranges. For <BR>> further reading, search for “CAUTION: Variable Speed Drive FPLR” <BR>> in the archives. <BR>> <BR>> <BR>> <BR>> Once I determined the cautions were erroneous, I went on to try <BR>> and figure out how to have eQuest not report cautions, so I could <BR>> get a clean ATTN report, but I’ve yet to successfully use the line <BR>> DIAGNOSTIC WARNINGS .. within an *.inp (I’m not sure it’s <BR>
> possible, actually). I’d be interested to hear if you can come up <BR>> with any new information… <BR>> <BR>> Best of luck! <BR>> <BR>> <BR>> <BR>> ~Nick <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> NICK CATON, E.I.T. <BR>> <BR>> PROJECT ENGINEER <BR>> <BR>> 25501 west valley parkway <BR>> <BR>> olathe ks 66061 <BR>> <BR>> direct 913 344.0036 <BR>> <BR>> fax 913 345.0617 <BR>> <BR>> Check out our new web-site @ www.smithboucher.com <BR>> <BR>> <BR>> <BR>> From: equest-users-bounces@lists.onebuilding.org [mailto:equest- <BR>> users-bounces@lists.onebuilding.org] On Behalf Of Varkie C Thomas <BR>> Sent: Monday, July 19, 2010 9:18 AM <BR>> To: Carol Gardner <BR>> Cc: equest-users@onebuilding.org <BR>> Subject: Re: [Equest-users] CAUTION and WARNING Messages <BR>> <BR>> <BR>> <BR>> Carol. <BR>> <BR>> <BR>> <BR>
> There were no changes to the FPLR curve data. I am trying to <BR>> create case studies for teaching based on projects that were <BR>> modeled with DOE21E. It could be any program. The buildings are <BR>> modified and simplified to eliminate repetitive details and to <BR>> demonstrate design issues. With eQ the building and the envelope <BR>> (even complex ones) can be created within a couple of hours by <BR>> tracing ACAD drawings. But on large project you cannot recognize <BR>> any of the components names in the reports. The DOE2 programs <BR>> require a component name before entering the data. eQ should make <BR>> this a priority in future versions. I think I will continue <BR>> creating the building model in eQ and use the dimensional data in <BR>> eQ (azimuths, coordinates, lengths, areas, etc) in creating DOE21E <BR>> models and analyze the options in DOE21E. <BR>> <BR>
> <BR>> <BR>> Varkie <BR>> <BR>> <BR>> <BR>> ----- Original Message ----- <BR>> <BR>> From: Carol Gardner <cmg750@gmail.com> <BR>> <BR>> Date: Monday, July 19, 2010 0:58 am <BR>> <BR>> Subject: Re: [Equest-users] CAUTION and WARNING Messages <BR>> <BR>> Varkie, <BR>> <BR>> I took a quick look at this and I don't see the problem either. <BR>> Did you make any changes to the FPLR curve data? <BR>> <BR>> Carol <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> I hope someone can help me. I am getting CAUTION messages � In <BR>> curve: Variable Speed Drive FPLR the dependent value is exceeding <BR>> the limits. Etc.,� <BR>> <BR>> <BR>> <BR>> The first one (my attempt at modeling the baseline without WSE <BR>> that I enquired about earlier) used all eQUEST defaults for the <BR>
> bldg type �High-Tech & Bio-Tech� including dimensions. Only the <BR>> Misc-Eqp was changed to 5 watts/sf. The attached eQ inp-pd2 files <BR>> are in Detailed-Edit. There were about 20 pages of �curve� CAUTION <BR>> messages. <BR>> <BR>> <BR>> The second is for a hotel bldg. The attached eQ inp-pd2 files are <BR>> In Design-Development. You can view them in DD. Except for minor <BR>> changes, the input for all Shells used eQ defaults. The component <BR>> names (schedules, spaces, zones, etc) are also eQ defaults. There <BR>> were about 2000 pages of �curve� CAUTION messages. <BR>> <BR>> <BR>> <BR>> The third is for an office bldg. <BR>> <BR>> In Run-1, except for changing the component names, the input for <BR>> all Shells used eQ defaults. There were about 2000 pages of <BR>> �curve� CAUTION messages. No WARNING messages <BR>> <BR>
> Run-2 used OA-FROM-SYSTEM. There were several WARNING regarding <BR>> heat capacity and the CAUTION messages of Run-1. <BR>> <BR>> <BR>> <BR>> I have attached (1) the eQ inp & pd2 files ; (2) the CAUTION & <BR>> WARNING messages; and (3) the project descriptions of all the <BR>> examples. <BR>> <BR>> <BR>> Varkie. <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> <BR>> </BODY>