Closed GoogleCodeExporter closed 9 years ago
Keep our eye on it
Original comment by ran...@mwwb.net
on 6 Aug 2009 at 10:33
I am not going to look at this one unless it starts up again. If so you can
change
the status back.
Original comment by ran...@mwwb.net
on 7 Aug 2009 at 3:49
I am again getting HRESULT errors (no popups just in the dispersal error log).
In
this run I was swapping out risk maps multiple times per day. I seem to get the
error when animals are trying to get risk values from the new map during their
first
step after the swap. Animals seem to get the value correctly, however, since
the
output is correct and some animals die as expected.
Original comment by bpa...@purdue.edu
on 24 Aug 2009 at 3:50
Attachments:
Also occuring with daily movement swaps.
Original comment by bpa...@purdue.edu
on 24 Aug 2009 at 4:38
Attachments:
Nick set up a long run where he recieved the HRESULT popup and dispersal error
message. I believe he was running on an earlier version and that is why the
popup
still occurs. I have posted the maps and xml, the output and the logs on the
FTP
site (under MartesMtg1.zip) for you to look at. We currently have this run
going on
a number of machines and will post whether or not the HRESULT error pops up in
these
runs with the newest version.
Original comment by bpa...@purdue.edu
on 4 Sep 2009 at 4:59
I had a run with the newest version with multiple swaps and some modifiers that
received the HRESULT error message in the dispersal error log (but no pop ups).
As I
stated before, this seems to be related to animals getting values off newly
swapped
maps (move in this case) based on the time of error. This run was done on a
version
with a fixed random number (of 1) so it should be easy to reproduce the error
quickly. I have attached the results and xml as well as the maps used.
Original comment by bpa...@purdue.edu
on 9 Sep 2009 at 2:23
Attachments:
I had a 3 year run with 5 days per year. Relevant maps and xml are attached.
(The
XML is in the maps folder.) The Logs were too big, and the FTP is down, so I
will
try to post them later to the FTP.
Midway through year 2 the sim quit. No pop-ups were produced. However,
several 'HRESULT' and 'Object reference not set to an instance of an object'
errors
were produced in the DispersalError log. At first look, the sim was working
fine
until it quit (i.e. no obvious big errors in output).
Note that this run did not have any swaps, but did have a lot of offspring in
year 2
(50 per females * 8 surviving females = 400 dispersers in year 2).
Thanks,
Nick
Original comment by nmcc...@purdue.edu
on 28 Sep 2009 at 12:21
Attachments:
Files for 'v88_time_test1' are now posted to the FTP.
-Nick
Original comment by nmcc...@purdue.edu
on 28 Sep 2009 at 4:46
Stopped HResult Error. Used v88_time_test1 xml. Did not study the xml too
well. but
first two generations bred and then in gen 3 they died from predation.
Please test version 92 and report back.
cheers
Original comment by ran...@mwwb.net
on 30 Sep 2009 at 1:48
In one of the runs that I did testing the annual social map swap I received a
dispersal error log with a single HResult error. I have attached that log and
the
xml. The random number was set to 1.
Original comment by bpa...@purdue.edu
on 30 Sep 2009 at 3:27
Attachments:
Ok I had the compision backwards I think. What was happening is if the animal
was in
polygon 21 and we switched out the maps to one that only had 5 polygons total
when
we tried to see if the animal had moved we could not get polygon number 21
anymore.
good testing and catch.
Original comment by ran...@mwwb.net
on 1 Oct 2009 at 6:54
The fix seems to be working for my annual social map swaps that were throwing
the
Hresult error in earlier versions. I am going to leave this issue open for a
while
since I think we have a number of untested (retested) scenarios that caused
this
error in the past.
Original comment by bpa...@purdue.edu
on 2 Oct 2009 at 3:21
Original comment by ran...@mwwb.net
on 5 Dec 2013 at 12:51
Original issue reported on code.google.com by
bpa...@purdue.edu
on 5 Aug 2009 at 3:36Attachments: