Ticket #951 (closed assessed: fixed)
Ecospace throw exception when run after Fishing Policy search
| Reported by: | joeb | Owned by: | |
|---|---|---|---|
| Priority: | high | Milestone: | Ecopath 6: release 6.2 |
| Component: | Ecospace | Version: | |
| Severity: | major | Keywords: | |
| Cc: |
Description
Open Ecosim and reduce the run length.
Run the Fishing Policy search.
Open Ecospace and run it.
Ecosim variables indexed by time that are used by Ecospace i.e. FishRateGear?(fleets,time) will not be dimensioned properly and will throw an exception when the time index is exceeded.
Change History
comment:1 Changed 14 years ago by jeroens
- Milestone changed from Ecopath 6: release 6.3 to Ecopath 6: release 6.2
comment:3 Changed 14 years ago by joeb
- Status changed from new to closed
- Resolution set to fixed
This was happening because Ecopace can not run for longer than Ecosim. This is sync from the core but could get out of sync when the user reduced the length of an Ecosim run then loaded an Ecospace scenario. Ecospace now checks to make sure its run length is not greater then Ecosim. Kind of hack but works for now...
Note: See
TracTickets for help on using
tickets.
