[Equest-users] Help - Parametric Run Issue

[Umesh Atre]

Robert,
I have experienced this too. What I have seen is that this issue is
dominant when working on Windows 7, and less frequent on XP, unless your
models are pretty large.
Here is a previous discussion on a related issue, in case you haven't
read this already.
 
 
 


________________________________

From: Maria Karpman [mailto:maria.karpman at karpmanconsulting.net] 
Sent: Thursday, September 22, 2011 11:47 AM
To: Umesh Atre; 'Pasha Korber-Gonzalez'; 'Walker, Matthew'
Cc: equest-users at lists.onebuilding.org
Subject: RE: [Equest-users] file format error! is all my work lost?



I had the same problem on Vista a few times. In my experience it only
happens with large projects that had parametric runs, which matches
Umesh's observation. The most unpleasant symptom was the loss of the
main inp file, with its size going to ~0. Overcoming initial shock, I
found that it is not too hard to recover from this by using one of the
inp files created during simulation. 

 

Let's say the lost project was named <MyProject>. To recover the inputs,
I'd go to the project folder and locate <MyProject>-Baseline.inp file.
If this file was not affected by the problem (has a reasonable file
size), I create a copy of the file and name it <MyProjectX>.inp. If
<MyProject>-Baseline.inp is also lost, I pick an inp file created by
eQUEST for a parametric run which has the most in common with the main
model and that was run recently, and create a copy of this file naming
it <MyProjectX>.inp. (The original file would be named
<MyProject>-<Parametric Run Label>.inp). When using  inp file for a
parametric run to recover a project, you need to remember to revert the
parameters that were changed in the parametric run back to the original
values once you are able to open the project in the detailed interface.
Note also that inp file for a parametric run is only generated when you
run calculations for this run, so when using this option you may have to
recapture all the changes that were made since the parametric run was
last calculated. To get a fresh start, I always create a new PD2 file
for the project following the steps described by Brian Fountain in the
post on 9/7/2011, and imports <MyProjectX>.inp into this new project. To
recover parametric runs, create a copy of <MyProject>.prd file naming if
<MyProjectX>.prd and place it in the folder with the rest of the
recovered files. I also always restart computer after a crash like that.


 

Good luck,  

 

Maria 

 

From: equest-users-bounces at lists.onebuilding.org
[mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of Umesh
Atre
Sent: Thursday, September 22, 2011 10:14 AM
To: Pasha Korber-Gonzalez; Walker, Matthew
Cc: equest-users at lists.onebuilding.org
Subject: Re: [Equest-users] file format error! is all my work lost?

 

Thanks Pasha. Let me try this on the Windows 7 machine. But I am getting
the same errors on XP too. My models keep disappearing.

What I have noticed though is that this problem might be somehow tied to
parametric runs. I have not lost any data from models

that did not have any parametric runs. Any ideas?

 

 

________________________________

From: equest-users-bounces at lists.onebuilding.org
[mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of Pasha
Korber-Gonzalez
Sent: Wednesday, September 21, 2011 6:19 PM
To: Walker, Matthew
Cc: equest-users at lists.onebuilding.org
Subject: Re: [Equest-users] file format error! is all my work lost?

 

For those of you that are using Windows 7, have you set the
"compatibility" settings within eQuest?  If you set eQuest to be
compatible with XP Service Pack 3 (or 2) this will help eQuest to work
smoothly within Windows 7 operating system and against all other
programs that you might have running at the same time as eQuest.

If you need to be talked through the steps to get this set feel free to
give me a call at 308-763-1593--it will take 3 minutes to talk you
through it and do some checks on your files.

I run 3.64 on both a Windows XP laptop and Windows 7 laptop, and I
haven't encountered these issues anymore.

Cheers,
Pasha

 

On Wed, Sep 21, 2011 at 3:46 PM, Walker, Matthew <
Matthew.Walker at tetratech.com
<blocked::mailto:Matthew.Walker at tetratech.com> > wrote:

 

 

A fellow co-worker and I have also experienced this frustrating message
a few times now.  

Both of our computers are less than 2 weeks old with windows 7, and we
downloaded eQUEST 3.64 last week.  

 

The problem is happening on new projects that we started last week, so
it's not an issue with old and new versions... just this new version.

 

 

Please let me know if anyone is finding a solution to this.

 

Matthew Walker, PE, LEED AP | Energy Management Consultant

 
 
 
 
 
 
 
 
 
 
 

________________________________

From: Robert Stephenson [mailto:rstephenson at southface.org] 
Sent: Thursday, January 19, 2012 3:28 PM
To: Umesh Atre; equest-users at lists.onebuilding.org
Subject: RE: [Equest-users] Help - Parametric Run Issue



Thank you for the assistance. I deleted the .prd  reloaded my .inp and
redid the parametric runs one run at a time. I lost an hour of work but
luckily not the whole model.

 

Initially I tried running all six runs at once. My coworker mentioned
that version 3.64 has issues crashing when running multiple parametric
runs. Has anyone else experienced this?

 

Robert Stephenson, LEED AP 

Research Engineer

Tel: 404-604-3589

Fax: 404-872-5009
Email: rstephenson at southface.org <mailto:username at southface.org> 

Web: www.southface.org <http://www.southface.org/> 

241 Pine Street NE, Atlanta, GA 30308

 

  <http://www.southface.org/> 

Building know-how for a sustainable future

 

Get involved with Southface
<http://www.southface.org/get-involved/become-a-member/>  today!

  <http://www.twitter.com/southfaceenergy>   
<http://www.linkedin.com/companies/southface>   
<http://www.facebook.com/pages/Southface/92291631957> 

 

From: Umesh Atre [mailto:umesh at innovativedesign.net] 
Sent: Wednesday, January 18, 2012 2:39 PM
To: Robert Stephenson; equest-users at lists.onebuilding.org
Subject: RE: [Equest-users] Help - Parametric Run Issue

 

Robert,

After opening eQUEST, select the *.inp file and try loading that. 

This model might not have your parametric runs, but hopefully you could
at least salvage your base model.

 

 

 

 

________________________________

From: equest-users-bounces at lists.onebuilding.org 
[mailto:equest-users-bounces at lists.onebuilding.org] On Behalf Of Robert
Stephenson
Sent: Wednesday, January 18, 2012 2:10 PM
To: equest-users at lists.onebuilding.org
Subject: [Equest-users] Help - Parametric Run Issue

I am having an issue loading my model after attempting to complete a
series of parametric runs. I have attached my .inp, .bdl, and .prd (the
txt file) files. 

 

The model ran through the first parametric run successfully and then
stopped. Therefore I have a resulting .sim file for the baseline and
first parametric run.

 

After receiving an error about expecting a character vs. numeric value
in the .prd file, I shutdown eQUEST and attempted to restart my model.
Now it will not load and my .bdl file contains the following error:

 

"ERROR: Cannot open a required file: 

USER LIBRARY FILE NAME WAS NOT SPECIFIED

It does not exist or is in use. Correct this and retry."

 

I could really use some assistance.

 

Thanks,

 

 

Robert Stephenson, LEED AP 

Research Engineer

Tel: 404-604-3589

Fax: 404-872-5009
Email: rstephenson at southface.org <mailto:username at southface.org> 

Web: www.southface.org <http://www.southface.org/> 

241 Pine Street NE, Atlanta, GA 30308

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20120119/edbf7bdd/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 1631 bytes
Desc: image001.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20120119/edbf7bdd/attachment-0008.jpeg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 785 bytes
Desc: image002.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20120119/edbf7bdd/attachment-0009.jpeg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 839 bytes
Desc: image003.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20120119/edbf7bdd/attachment-0010.jpeg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 821 bytes
Desc: image004.jpg
URL: <http://lists.onebuilding.org/pipermail/equest-users-onebuilding.org/attachments/20120119/edbf7bdd/attachment-0011.jpeg>