Ticket #649 (closed assessed: fixed)

Opened 9 years ago

Last modified 6 years ago

Ecospace has problems with big basemaps

Reported by: martac Owned by: jeroens
Priority: urgent Milestone: Ecopath 6: release 6.3 BETA
Component: Ecospace Version:
Severity: crash Keywords: basemap
Cc:

Description (last modified by jeroens) (diff)

Hello team
I'm trying to create a basemap in Ecospace of 252 * 300 cells and ecospace was doing very weird stuff. It crashed after 10 mins of thinking and then when I would open the model again it would take 20 mins to load the scenario and then the map would be there, but it would be extremely difficult to edit the habitat preferences because it would crash again. So a bit difficult all together.
I would like to know how realistic is to do this in v6.
Thanks!

Change History

comment:1 Changed 9 years ago by jeroens

  • Owner set to jeroens
  • Status changed from new to assigned

Speed issue solved with bug #416
Memory leaks and crashes to be investigated further...

comment:2 Changed 9 years ago by jeroens

  • Description modified (diff)

comment:3 Changed 9 years ago by joeb

  • Priority changed from urgent to immediate

comment:4 Changed 9 years ago by joeb

  • Priority changed from immediate to urgent

comment:5 Changed 9 years ago by shermanl

  • Type set to not assessed

comment:6 Changed 9 years ago by jeroens

  • Type changed from not assessed to assessed
  • Milestone set to Ecopath 6

comment:7 Changed 9 years ago by shermanl

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

comment:8 Changed 9 years ago by joeb

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

comment:9 Changed 9 years ago by jeroens

Speed issue has been significantly optimized by computing habitat gradient only before a run. However, this logic needs to be revised and seriously optimized. Maybe Carl could help?

comment:10 Changed 9 years ago by jeroens

CalcPrefHabGradient? needs to be optimized

comment:11 Changed 8 years ago by jeroens

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

comment:12 Changed 8 years ago by jeroens

  • Milestone changed from Ecopath 6: release 6.1.1 to Ecopath 6: release 6.2

comment:13 Changed 8 years ago by jeroens

  • Milestone changed from Ecopath 6: release 6.2 to NOT SET

Have not yet had the time to assess this. Ecospace is getting connected to spatial data which will not be released until fall 2011; this issue should be addressed by then

comment:14 Changed 8 years ago by jeroens

  • Milestone changed from NOT SET to Ecopath 6: release 6.3

comment:15 Changed 6 years ago by jeroens

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

Ecospace has been refactored

Note: See TracTickets for help on using tickets.