Ticket #1134 (closed assessed: fixed)

Opened 12 years ago

Last modified 12 years ago

Ecospace throws an exception if Ecosim Reset all has been clicked

Reported by: joeb Owned by:
Priority: normal Milestone: Ecopath 6: release 6.3 BETA
Component: Ecospace Version:
Severity: crash Keywords:

Description (last modified by jeroens) (diff)

  1. Load a model with more Ecosim time steps than Ecospace time steps.
  2. Run Ecosim and Ecospace.
  3. Alter the Ecosim fishing effort.
  4. Run Ecospace.
  5. Click the Ecosim Reset all button, to clear the fishing effort changes.
  6. Run Ecospace

RunEcospace.ClearResults() will throw an exception when trying to clear m_RelBiomassResults(,). nEcospaceTimeSteps will be equal to the number of Ecosim time steps not the original number of Ecospace time steps from the last run. nEcospaceTimeSteps must have gotten changed by the core but the interface never update m_RelBiomassResults()

Change History

comment:1 Changed 12 years ago by jeroens

  • Description modified (diff)

comment:2 Changed 12 years ago by jeroens

  • Description modified (diff)

comment:3 Changed 12 years ago by jeroens

This change should invalidate the loaded Ecospace scenario via the state monitor.

jb The Ecospace interface should be more robust to changes in the Core. So we need to make sure the core has not incorrectly set the number of time steps and the interface knows the correct number and can respond correctly. Just bluntly reloading the scenario make it hard to use Ecospace. It is legitimate to make changes in Ecosim then go directly to Ecospace and run it expecting the changes to be reflected.

Last edited 12 years ago by joeb (previous) (diff)

comment:4 Changed 12 years ago by joeb

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

The Ecospace interface was missing the eMessageType.EcosimNYearsChanged message. Once that was fixed it could re-init itself to the new number of years.

Note: See TracTickets for help on using tickets.