Comments you submit will be routed for moderation. If you have an account, please log in first.
Modify

Ticket #4208 (closed defect: fixed)

Opened 3 years ago

Last modified 2 years ago

runef has trouble with unused variable

Reported by: dlwoodruff@… Owned by: jdsiiro
Priority: normal Milestone: Coopr 3.2
Component: Configuration Version:
Keywords: Cc:

Description

see text file in the attached zip file for details, but basically
I get an error from runef due to an unused variable. Here is the error:

Queuing extensive form solve
Waiting for extensive form solve
VALUE ERROR: No value for uninitialized NumericValue? object z['Block7',3]

Attachments

Uninitbug.zip Download (12.8 KB) - added by dlwoodruff@… 3 years ago.
zip file with model, data and txt file describing troubles
Uninitbug-3x.zip Download (8.2 KB) - added by jdsiiro 2 years ago.
Updated version of the model for Coopr 3.x

Change History

Changed 3 years ago by dlwoodruff@…

zip file with model, data and txt file describing troubles

comment:1 Changed 3 years ago by wehart

  • Milestone set to Coopr 3.1

comment:2 Changed 2 years ago by wehart

  • Owner changed from wehart to jdsiiro
  • Status changed from new to assigned

comment:3 Changed 2 years ago by jwatson

  • Milestone changed from Coopr 3.1 to Coopr 3.2

Changed 2 years ago by jdsiiro

Updated version of the model for Coopr 3.x

comment:4 Changed 2 years ago by jdsiiro

After converting the example to Coopr 3.x format (model-first rules; zipfile attached), it appears that this bug has been "fixed": runef now returns non-fatal warnings for unused variables:

WARNING: Encountered variable=z['Block7',3] that is not in use within scenario=Scen1, but the scenario tree specification indicates that non-anticipativity is to be enforced; the variable should either be eliminated from the model or from the scenario tree specification.

If you don't have any objection, we can close this ticket.

comment:5 Changed 2 years ago by jdsiiro

  • Status changed from assigned to closed
  • Resolution set to fixed

Closed with the (email) consent of the original reporter.

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.