[esp-r] Re: plant configuration file error with new development_branch code

[Jon Hand]

The FAILURE: in ../zones/coridor.geo is giving the wrong file name because
the code has not set the currently read file name varuable currentfile.

The phrase "plant db ointer" is found in the source file esrucom/pltcfg.F
near line 374.  It is a read statment attempting to fill the variable NPREF.
It read a zero which is out of range.  It is the plant network file that it is
trying to read when it faults.  To confirm that your plant template database
is ok you need to separately open it.

It is possible that the exemplar component based HVAC network file
has gotten corrupted.  Do you get an issue with other plant network
files?

Regards, Jon Hand

________________________________________
From: esp-r-bounces at lists.strath.ac.uk [esp-r-bounces at lists.strath.ac.uk] On Behalf Of Dimitrios Sfakianakis [dimitrios.sfakianakis at strath.ac.uk]
Sent: 29 May 2013 17:44
To: esp-r at lists.strath.ac.uk
Subject: [esp-r] plant configuration file error with new development_branch     code

Dear list,

Today I downloaded and compiled the source code from the development branch (development_branch at r9237) in Ubuntu ran through VMware virtual player in Windows, and started having some problems with editing plant configuration files. At first I thought it was a compatibility issue since my models were created with a different version of esp-r however I get the same problems with newly created models and exemplars.

For an existing plant configuration file (e.g. the exemplar component based HVAC system) when I try to modify the plant network the first time, I get an indication of "error reading plant data base" for each component defined and when I exit and try to modify it again I get the following error

"FAILURE: in ../zones/coridor.geo: the plant db pointer value (0) < allowable minimum 1!"

Is anyone else experiencing any similar problems? Any ideas about what might be causing the problem? I am also attaching a screenshot of the problem. Everything was working fine with the previous version I was using.

Thanks for the help and support.

Dimitris