Ticket #1645 (new not assessed)
Ecotracer banded results
Reported by: | joeb | Owned by: | joeb |
---|---|---|---|
Priority: | urgent | Milestone: | 6.7 release |
Component: | Contaminant tracing | Version: | 6.7 beta |
Severity: | major | Keywords: | |
Cc: |
Description
Ecotracer contaminant maps display bands when run on multiple threads.
Version 6.7.0.18580
Attachments
Change History
Changed 14 months ago by joeb
- Attachment Ecotracer with Banding.png added
comment:1 Changed 14 months ago by joeb
Fixxed in version 6.7.0.18590
In the original version of Ecotracer it was coupled to the Ecospace food web model calculations for each cell/thread. This meant it could access Ecospace state variables for the current cell on the same thread as the food web model i.e. consumption, loss…
When Ecotracer was changed to run in its own spatial and temporal integration routine, to account for faster radionuclide decay rates and better spatial distributions, these state variables were no longer valid for the current Ecotracer thread or cell. The fix was to save the state variables out to an array by cell that could be accessed in a thread safe manner.
During the debugging we also changed the Run Ecospace maps legends to do a better job of getting the correct max across the contaminant maps for display.
Also added the contaminant maps to the .csv output maps. This option saves one file for each group across time steps. This can be used by the EcospaceCSVDif project to debug changes to the code across versions to make sure nothing is broken by the current change.
Joe
Changed 14 months ago by joeb
- Attachment Ecotracer Contaminants Fixed .png added
Ecotracer output with multithreading bug fixed
Ecotracer map showing banding of contaminant results