Ticket #624 (closed assessed: fixed)

Opened 9 years ago

Last modified 8 years ago

Multi-Stanza Hatchery Stocking forcing function not imported

Reported by: joeb Owned by: jeroens
Priority: normal Milestone: Ecopath 6: release 6.1.1
Component: Database / Import Version:
Severity: minor Keywords:
Cc:

Description

In the EwE6 'Edit Multi-Stanza Groups' interface the 'Forcing function for hatchery stocking:' forcing function number/id is not imported from 5 (cStanzaDatastructures.HatchCode?(Nsplit)). The forcing function itself gets imported but the HatchCode? does not.

Change History

comment:1 Changed 9 years ago by jeroens

This issue has been known since 2007. There is no direct solution for this:

  • EwE5 links stanza configurations (which are not Ecosim scenario dependent) to forcing shapes (which are Ecosim scenario dept) via an index that is only meaningful from the context of a loaded scenario.
  • EwE6 instead loads shapes as being Ecosim scenario independent, and hatchery functions must be hard-tied to forcing shapes. The EwE5 relative index is thus meaningless to the importer: it cannot know how to substitute the EwE5 function index with a forcing function ID.

We need to come up with some kind of strategy. Villy, perhaps the hatchery shape index should be tied to the very first forcing function that matches the EwE5 index, thus ignoring the scenario parameter?

comment:2 Changed 9 years ago by jeroens

We have to discuss how to address this

comment:3 Changed 8 years ago by shermanl

  • Type set to not assessed

comment:4 Changed 8 years ago by shermanl

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

comment:5 Changed 8 years ago by shermanl

  • Owner villyc deleted

comment:6 Changed 8 years ago by jeroens

  • Summary changed from Mulit Stanza Hatchery Stocking forcing function not imported to Multi-Stanza Hatchery Stocking forcing function not imported

comment:7 Changed 8 years ago by jeroens

  • Owner set to jeroens
  • Type changed from not assessed to assessed

Add warning status message

comment:8 Changed 8 years ago by jeroens

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

comment:9 Changed 8 years ago by jeroens

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

In EwE5, the hatchery index is specified in Ecopath, while the actual functions are loaded in Ecosim. EwE5 does not validate whether entered hatchery indexes are valid, making this a quite fragile system.

In EwE6, the hatchery index is translated to the corresponding function imported for each individual scenario. Since forcing shapes are shared between scenarios, all Ecosim scenarios will thus receive a link to the same hatchery function IF the hatchery index turned out to be valid.

After import users can assign a different hatchery function to a stanza configuration for each Ecosim scenario. This was not possible under EwE5.

Note: See TracTickets for help on using tickets.