Ticket #1547 (closed assessed: open)
Forcing function application bug
Reported by: | joeb | Owned by: | |
---|---|---|---|
Priority: | NOT SET | Milestone: | Ecopath 6: Release 6.6 |
Component: | NOT SET | Version: | 6.5 |
Severity: | NOT SET | Keywords: | |
Cc: |
Description
Found a weird bug in both the trunk and the current release.
- Open the sample Georgia Strait model, Ecosim AllFit.
- Run Ecosim, it will have a primary production forcing function loaded and run with a bunch of variation.
- Remove the PP forcing function
- Run Ecosim, it will run flat(ish).
- Add a new forcing function, I created a linear 0-2 forcing function. DO NOT SAVE the model when prompted, also don't apply the new forcing function. Just let it sit there.
- Go back to Ecosim and run it. It will look like the original forcing function is still be applied.
If you apply the new forcing function they will both be applied.
If you save when prompted, or at any time, it will run correctly.
Change History
Note: See
TracTickets for help on using
tickets.
Adding (or removing) a shape will reload Ecosim as per protocol. If Ecosim was not saved, the PP interaction also returns. The bug here is that the interaction manager(s) are not refreshed to inform the UI that the PP application is back