Resident deaths during timestep throws exception and stop iteration

[GoogleCodeExporter]

I ran a test looking at resident mortality per timestep. In this run a 
bunch of animals set up HRs but are subject to 10% resident mortality per 
timestep. From this run I received a bunch of the same error message 
repeated over and over (dispersal_error.log attached). In addition, 
whenever a resident died, this caused the looping of residents to stop. So 
if we were looping through animals 0-39 and animals 0, 1, and 2 all 
survived but animal 3 died (roll of dice < 0.1) none of the animals after 
3 (i.e. 4-39) would be looped through and so would essentially have 0% 
mortality for that step. They would again be thrown in the mix for the 
next step but the process would again repeat. This means that animal 39 
could only die during a timestep when all other remaining residents 
survived. There also seems to be some confusing of animal numbers. For 
instance, animal #3 dies during a timestep but does not have that written 
out in the text file while #38 never dies but has the "died during 
timestep" line is its text file. I have attached the xml for this run as 
well.

Original issue reported on code.google.com by bpa...@purdue.edu on 16 Oct 2009 at 3:34

Attachments:

• DispersalError.log
• res_time_deathC.xml

[GoogleCodeExporter]

I reran the above test and did not observe any of the loop stopping or the 
above 
exceptions. There were E_FAIL errors but I included that in another issue's post

Original comment by bpa...@purdue.edu on 22 Oct 2009 at 2:05

• Changed state: Verified