Ticket #711 (closed assessed: fixed)

Opened 14 years ago

Last modified 14 years ago

Discards within MPAs in the Gulf of Carpentaria - Northern Australia

Reported by: rodrigob Owned by: shermanl
Priority: normal Milestone: NOT SET
Component: Ecospace Version:
Severity: major Keywords: Discards out of control
Cc: nick.ellis@…, beth.fulton@…, hector.lozano-montes@…, rodrigo.bustamante@…



We stumbled with the strage fact that Discards (a non-dynamic/pool FG) is showing up within a mocked up MPA.

I did check that fishing is excluded from the MPA (viewing in Ecospace while running). Hector thinks that we may have not propoerly link the discards to the fisheries, but I am not sure of that. All seem in place.

Change History

comment:1 Changed 14 years ago by rodrigob

  • Cc rodrigo.bustamante@… added
  • Severity changed from NOT SET to tweak

comment:2 Changed 14 years ago by shermanl


I'm trying to help a guy in Brisbane diagnose some ecospace weirdness. He has an mpa with no fishing allowed, but discards in it are turning up as non-zero. He has the habitat type ticked for discards as fishing grounds and mpa are on same habitat type, but he has dispersal rate set as zero. Would he still be getting "movement" between cells even with dispersal set to zero given that the MPA is on a preferred habitat? Or is there something else he needs to change taht I've missed?



comment:3 Changed 14 years ago by joeb

  • Status changed from new to closed
  • Type changed from NOT SET to assessed
  • Resolution set to fixed
  • Severity changed from tweak to major

Ecospace was not setting Fishing effort used by the detritus calculation properly. Detritus is calculated by Ecosim in SimDetritusMT(...) which gets fishing effort from EcosimDataStructures.FishRateGear(fleet, t=0). Ecospace was setting it's own copy of EcosimDataStructures.FishRateGear() to avoid a threading conflict but never setting that to be used by SimDetritusMT(...). I change SimDetritusMT(...) to take fishing effort as a argument instead of reading it from memory this avoids all threading conflicts as each thread can pass in its own value.

Note: See TracTickets for help on using tickets.