[Equest-users] Equest-users Digest, Vol 75, Issue 11-Weather Normalizing an eQuest Model

[Ranojoy Dutta]

 Jacob

Did you try changing the file extension to .ft and then running the weather utility. However my bigger concern is that your txt file only has one col of Temp values . This is not going to give you a complete weather file.

Ronny


Ranojoy Dutta | Energy Analyst | Tempe , AZ
 

________________________________
 From: "equest-users-request at lists.onebuilding.org" <equest-users-request at lists.onebuilding.org>
To: equest-users at lists.onebuilding.org 
Sent: Saturday, 14 June 2014 1:03 PM
Subject: Equest-users Digest, Vol 75, Issue 11
  

----- Forwarded Message -----

Send Equest-users mailing list submissions to
    equest-users at lists.onebuilding.org

To subscribe or unsubscribe via the World Wide Web, visit
    http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org

or, via email, send a message with subject or body 'help' to
    equest-users-request at lists.onebuilding.org

You can reach the person managing the list at
    equest-users-owner at lists.onebuilding.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Equest-users digest..."

Today's Topics:

   1. Re: Zone and activity Allocation? (Nick Caton)
   2. Weather Normalizing an eQuest Model (Jacob Goodman)

 
Interesting question, I’ll answer with how I use this screens, and maybe learn something in the process! 
  
Myself – I only use screen 13 for a given shell to ensure I have all the space types I need to account for (sometimes reselecting some of the dropdowns to different options available).  I will then leverage screen 14 to assign those types to each specific zone – typically allocating 100% of one space type (creating a zone group) to each specific zone, but sometimes splitting the space types up if the zone encompasses multiple area types.  I’ll also leverage screen 14 to define zonal exhaust, as occurring. 
  
When it comes to inputting actual (designed) space occupancies and ventilation rates, I allow the wizards to stick to the library values until I get into detailed mode, where you can enter those things with hard figures, typically to synchronize with actual equipment scheduling and/or design calculations. 
  
Nothing in screens 13/14 directly affects the HVAC systems you define in wizards.  Often, I’ll define all my shells (including inputs for screens 13/14) before even beginning to define HVAC systems.  If I am defining multiple distinct system types, I’ll go back to screens 14 for my shells to ensure all spaces are assigned appropriately before finishing wizard level edits. 
  
That’s just how I use these screens – hope that helps =)! 
  
~Nick 
  
 
  
NICK CATON, P.E. 
SENIOR ENGINEER 
  
Smith & Boucher Engineers 
25501 west valley parkway, suite 200 
olathe, ks 66061 
direct 913.344.0036 
fax 913.345.0617 
www.smithboucher.com  
  
From:Equest-users [mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of Donald Hay
Sent: Friday, June 13, 2014 2:57 PM
To: equest-users at lists.onebuilding.org
Subject: [Equest-users] Zone and activity Allocation?   
  
Hello,  
  
Looking back over archived emails on the list, it seems like the preferred method for zone and activity allocation (screens 13 and 14 in the dd wizard shell definition dialogs) is to sum the square footages of each HVAC zone and allocate the spaces based on percentages in screen 14. This seems somewhat counter-intuitive. Is there a method, in ddedit or otherwise, to just assign activity classifications space-by-space, without affecting their HVAC system parent?  
  
Thank you.  
  
Donald Hay, E.I.T. 
Stridde, Callins & Associates
(361) 883-9199 
    
Dear List,

After much googleing I found some close answers, but not exact. My
    task this weekend is to take an eQuest model and "Weather normalize"
    it. To do this I need to create a .bin weather file for San Diego
    for the full year 2013 and then run the model using that weather. My
    approach so far is to download a .txt file from:

 https://gis.ncdc.noaa.gov/map/viewer/#app=cdo&cfg=cdo&theme=hourly&layers=1

Then selecting only "Air Temperature Observations" (do I want other
    variables?) and generating the output sent to me as:

http://www1.ncdc.noaa.gov/pub/orders/3303657117758dat.txt

Then I tried to convert "SanDiegoTemp.txt" to a .bin file using the
    PKAFT command to call the TXT2BIN application from the DOE2 website.
    I edited the PKAFT batch file to change the directory path from
    "C:/doe22" (that was the default) to point to my weather directory
    that containd the .txt file that I got from NOAA. I then typed
    "PKAFT SandDiego" hit enter got a message:


This shell file packs an unpacked DOE-2 weather file.
The file was unpacked wth wthfmt2 and has an .ft extension
(which is not included in the call to this procedure.)
Param 1 is file name.  Param 2 is S or NS for solar or nonsolar.
S for TMY, WYEC; NS for TRY.
If Param 2 is not specified the type found on the .ft file will be used.
A WTH stat run is also made on the file and all output
 is moved into the INPUT directory.

Then hit continue and got the error:

ERROR:missing input data file - c:\Users....the path...\weather\SanDiegotemp.ft

No .bin file was produced and it looks to me like the program is looking for a .ft file not a .txt file. Any advice? Is there an easier way to get a 2013 San Diego .bin file?

Thanks much and hope everyone is having a great weekend,
Jacob


 
_______________________________________________
Equest-users mailing list
Equest-users at lists.onebuilding.org
http://lists.onebuilding.org/listinfo.cgi/equest-users-onebuilding.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20140615/75b79ccb/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 1459 bytes
Desc: image001.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20140615/75b79ccb/attachment.jpg>