[Equest-users] Strange errors in file- HELP!

[Patrick J. O'Leary, Jr.]

actually this depends what editing mode you are in.

if your project is saved in detailed edit mode (ddedit) this is correct.

if your project is saved in wizard edit mode this is not correct.  
wizard mode writes to the pd2 file and overwrites any changes made in 
the .inp file every time you finish/exit the wizard.  this is why there 
is a warning dialog when switching to/from detailed edit mode that tells 
you changes you make in detailed mode will not be saved when entering 
wizard edit mode.

if your project is in wizard edit mode then you can modify the .pd2 file 
when you are not in equest and you will see those changes reflected next 
time you open equest and open the file.  i have added multiple ac-units 
to .pd2 files so they show up in wizard mode without my having to create 
them via the wizard, or copy one to create 5 more of the same packaged 
unit variety & then edit the tonnage or cfm.  i have also, when changing 
zones, copied and pasted from previous pd2 files the window code 
segments into the respective facets after the wizard erases all of the 
custom windows (like it tells you it will) when you modify a zone size 
(or a roof).

On 7/9/10 4:35 PM, John Aulbach wrote:
> Thank God a weekend is coming up. Everyone stop simulations and visit 
> their families.
> The .INP file is the raw data entry in DOE-2.,2 that the eQuest .PD2 
> recognizes to formulate a run. The .BDL file is the "digested" input 
> information after DOE-2.2 (the engine) error checks the input. The 
> core program actually uses the .BDL file for its input.
> I suppose you could change the .BDL file. But the eQuest front end 
> (.PD2) displays what is sees in the .INP files NOT the .PD2 file.
> It is finished....
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20100709/bc1a3bd6/attachment.htm>