Ticket #94 (closed: open)

Opened 11 years ago

Last modified 11 years ago

Model balancing- biomass in habitat area reading incorrect values

Reported by: carieh Owned by: administrator
Priority: normal Milestone: Ecopath 6: build 6.0.7
Component: Database / Import Version:
Severity: minor Keywords:


Sorry you get the long version.....
So in the process of balancing a model. These are models from Villy's class that he has set up to be unbalanced, so the imported version needs to be adjusted before balancing. In this model I have made a few changes to the whale, seal, and phytoplankton groups. I have altered the biomass of seals from 0.01 to 0.02, the P/B for whales form 2 to 0.08, and deleted the phytoplankton biomass. This is where I get the problem. The altering of parameters seems to be fine (whales and seals) as in the EE estimated by the model, but the phytoplankton is where I have the problem. Also the EE for every group comes out correctly (so the model seems to be balancing correctly).

Where I have the problem is when I delete the biomass for phytoplankton.

When I move to the basic estimates the biomass of phytoplankton is calculated correctly at 12, in the biomass column, however the biomass in habitat area remains at 0.(it should be 12, and all other groups are correct). I am not sure if this is an actual bug, as the values for EE and biomass are being caluclated correctly or if there is a problem in the calculation.

Model 2a june 15th. on ftp site

related to bug 95 (the issues with the 0 value in the cell as opposed to a blank cell.

Change History

comment:1 Changed 11 years ago by jeroens

Carie, please retest this. Two bugs that I solved my have provided a solution for this issue as well:

  1. Cells can now be blanked-out which will help in estimating them.
  2. PP status (Producer/consumer/detritus status) changes did not get saved to the core.

When retesting, please check first the PP status of Phytoplankton in your model in the EditGroups? interface. Then clear the cells to estimate and it should work.

comment:2 Changed 11 years ago by carieh

Yep works fine in the new version :-)
At least so far with 2 different models.

Note: See TracTickets for help on using tickets.