You are here

PEST error for parameter estimation

Dear Jasper,

As I would like to use PEST to calibrate my model, I encounter an error everytime I try it:
"can't read "runData(node00000,bestPhi)": no such element in array"

LOG:

can't read "runData(node00000,bestPhi)": no such element in array
can't read "runData(node00000,bestPhi)": no such element in array
    while executing
"set closish $runData($myNode,bestPhi)"
    (procedure "FixPredWindow" line 6)
    invoked from within
"FixPredWindow $useNodes($winId,pfit)"
    (procedure "Optimize" line 244)
    invoked from within
"Optimize $winId"
    (procedure "Go" line 27)
    invoked from within
"Go .mre1.mainpw.mainDisplayPane.notebook.fpage0.panedwindow.pane0.container"
    (in namespace inscope "::pest20050803" script line 1)
    invoked from within
"::namespace inscope ::pest20050803 {Go .mre1.mainpw.mainDisplayPane.notebook.fpage0.panedwindow.pane0.container}"
    invoked from within
".mre1.mainpw.mainDisplayPane.notebook.fpage0.panedwindow.pane0.container.notebook.results.lbf.upper.start invoke "
    invoked from within
".mre1.mainpw.mainDisplayPane.notebook.fpage0.panedwindow.pane0.container.notebook.results.lbf.upper.start instate !disabled { .mre1.mainpw.mainDisplay..."
    invoked from within
".mre1.mainpw.mainDisplayPane.notebook.fpage0.panedwindow.pane0.container.notebook.results.lbf.upper.start instate pressed { .mre1.mainpw.mainDisplayPa..."
    (command bound to event)

Below are screenshots of the different PEST settings.
For the model used here, it is very simple:
output=inone*intwo
intwo is set to 4 as a fixed parameter, and inone (another fixed parameter) is the one to find (solution should be 5 as it is calibrated on ouput=20)

Also, I already tried re-installing the program, re-setting the PATH variable etc...

So would you know how I could fix this?

I also contacted people from PEST, as I don't know where the error comes from (Simile or PEST..).

Thanks in advance,

Ben

 

Reporter: 
benedetto.rugani
Created: 
Mon, 08/02/2016 - 13:31
Updated: 
Tue, 09/02/2016 - 12:04

Comments

Hi Benedetto,

You have to run PEST at least once in optimization mode before you can turn on prediction. This is because it needs a set of already calculated parameter estimates before it can generate predictions based on the current estimates.

In the next Simile version I will make sure this requirement is reported properly if someone attempts to run a prediction before doing a parameter estimation run. Thanks for reporting this mistake.

    --Jasper

Hi Jasper,

Ideed it works if first running an optimization. The result of this is in fact the node0000 variable PEST could not find I suppose.

Thank you

Benedetto