Ticket #512 (closed assessed: fixed)

Opened 10 years ago

Last modified 8 years ago

Numerous error messages when model does not balance

Reported by: carieh Owned by: jeroens
Priority: normal Milestone: Ecopath 6: release 6.0.8
Component: Overall Logistics Version:
Severity: major Keywords:
Cc:

Description (last modified by shermanl) (diff)

Good Luck :-0)
Version 6.0.3.18
I opened Antarctic model (any should work)
-run in ecosim
-run fishing policy search (just to replicate)
-edit groups: add a group
-there were at least 10 pop-up screens to tell me my model was no longer balanced
I think one for every ecosim screen I had open :-)
Good lord, it took me 5 minutes to get out of that mess!!!

Change History

comment:1 Changed 10 years ago by jeroens

This needs to be solved in the core, as Villy originally requested with bug 492 (hence the relationship)

The core must withold duplicate messages until a significant change reuqires that the message is sent again. This functionality does not yet exist

comment:2 Changed 10 years ago by jeroens

After build 6.0.3.20 or so, the user can choose to suppress certain core messages.
the messages are valid though; after adding a group the model is no longer balanced.

comment:3 Changed 10 years ago by carieh

Ok the errors are not so bad, as long as you are not in an active Ecosim interface. If you run ecosim and go to Basic input and then try to add a group you dont get as many errors as if you were in the run ecosim interface and then just click edit groups.

So I know it is not the smartest to edit groups from an ecosim interface, but just thought I would let you know.

comment:4 Changed 10 years ago by jeroens

Hahaha, ok, I just have to try that now

comment:5 Changed 9 years ago by shermanl

  • Type set to not assessed
  • Description modified (diff)

comment:6 Changed 9 years ago by shermanl

  • Milestone changed from Ecopath 6: build 6.0.7 to Ecopath 6: build 6.0.8

comment:7 Changed 9 years ago by shermanl

  • Owner jeroens deleted

comment:8 Changed 8 years ago by jeroens

  • Type changed from not assessed to assessed
  • Severity changed from minor to crash

This crashes Ecosim, lovely.

comment:9 Changed 8 years ago by jeroens

  • Owner set to jeroens

comment:10 Changed 8 years ago by jeroens

  • Severity changed from crash to major

The core asserts when trying to re-run Ecopath after adding or removing groups. An Ecopath run is very likely to fail, the core should not throw an assertion but should exit gracefully.

After removing the assert a few errors pop up which make sense but should somehow be averted. Perhaps a change could be to stop the core from reloading Ecosim whenever Ecopath has been restructured, etc.

comment:11 Changed 8 years ago by jeroens

Implemented this: when restructuring a level (Ecopath < Ecosim < Ecospace), levels above the restructured level are no longer automatically reloaded since the altered level needs to be re-assessed and will probably not run correctly.

comment:12 Changed 8 years ago by jeroens

  • Status changed from assigned to closed
  • Resolution changed from repoened to open

comment:13 Changed 8 years ago by jeroens

  • Status changed from closed to reopened
  • Resolution open deleted

comment:14 Changed 8 years ago by jeroens

  • Status changed from reopened to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.