Ticket #623 (closed assessed: not an issue)
Timeseries datasets with forcing function data (eTimeSeriesType.TimeForcing) are not applied when timeseries dataset is loaded
|Reported by:||joeb||Owned by:||villyc|
|Priority:||normal||Milestone:||Ecopath 6: release 6.2|
Description (last modified by jeroens) (diff)
In EwE5 when a timeseries dataset is loaded that contains type 2 data (in EwE5 time forcing in EwE6 TimeSeriesType?.TimeForcing?) this data will overwrite any existing forcing function data in memory. In EwE6 when the database is imported timeseries data of type 2 data (time forcing) are striped out of the timeseries dataset and loaded into the forcing function data. Then if the timeseries dataset is loaded/applied the forcing function data never gets applied so the in memory forcing function data does not contain the timeseries data from the dataset.
This creates differences in the Ecosim output if timeseries data that includes forcing function data are loaded
In EwE5 once timeseries data that contains forcing function data is loaded that data stays in memory until a new model is loaded, even if another timeseries dataset is loaded. This effectively corrupts forcing function data that has been applied.
- Owner set to jeroens
- Status changed from new to assigned
- Description modified (diff)
- Milestone changed from Ecopath 6: build 6.0.7 to Ecopath 6: build 6.0.8
comment:10 Changed 3 years ago by jeroens
- Milestone changed from Ecopath 6: build 6.0.8 to Ecopath 6: build 6.1.1
comment:11 Changed 3 years ago by jeroens
- Milestone changed from Ecopath 6: release 6.1.1 to Ecopath 6: release 6.2