Ticket #30 (closed: fixed)

Opened 11 years ago

Last modified 10 years ago

Ecospace Define Habitats Fraction variable not exposed by core.

Reported by: user8 Owned by: administrator
Priority: high Milestone: Ecopath 6: build 6.0.7
Component: Database / Import Version:
Severity: major Keywords:
Cc:

Description

This variable is used in both EwE5 and EwE6 Ecospace Define habitats UI.

Joe or Jeroen, Who?

Change History

comment:1 Changed 11 years ago by administrator

has duplicate #422

comment:2 Changed 11 years ago by jeroens

Jeroen

comment:3 Changed 11 years ago by jeroens

cEcospaceHabitat exposes HabAreaProportion?, which is the ecospace area ratio for a given habitat. The Ecopath area has not yet been exposed

comment:4 Changed 11 years ago by jeroens

Done

comment:5 Changed 10 years ago by carieh

version 6.0.3.7
I am not sure if I understand this bug correctly, but...
the fraction of habitats in assign habitats is not correct. If I create 5 habitats, and assign each groups to a different habitat, they should have an ecospace area less than 1, but all groups have an ecospace area=1. I believe this feature used to work correctly.

comment:6 Changed 10 years ago by jeroens

EwE6 is consistent with EwE5 after comparing various existing models. However, live data changed were not reflected correctly. I've fixed this after build 6.0.3.7

comment:7 Changed 10 years ago by carieh

Almost there... Version 6.0.3.11
The vales are all now over 1. If I select all the habitats individually (1,2,3,4 out of 4) instead of clicking the all button, the total habitat is 2 not 1. I think a 1 is getting added in somewhere here.

Also If I choose 5 habitats with the same area and I go into assign habitats, the values that get spit back out are not consistent. I have chosen 5 habitats with the same # of cells shaded in the basemap so each should represent 0.2 of the habitat. However, I get values ranging from 1-1.99 when I only have one habitat selected.

So basically the numbers are all out of whack. Sorry

comment:8 Changed 10 years ago by jeroens

6.0.3.11: yes, it is definitely screwed-up. It seems that the All [X] checkbox is not properly handled. I'm on it

comment:9 Changed 10 years ago by jeroens

Great catch, Carie. Another elemental bug solved. Fixed after build 6.0.3.11

comment:10 Changed 10 years ago by carieh

version 6.0.3.14 fixed

Note: See TracTickets for help on using tickets.