Dear Roy,
On Mon, 16 Mar 2009, Roy Stogner wrote:
> Anyway, I've checked the fixes into SVN; now might be a good time for
> those of us on the bleeding edge to update.
Great work! Thank you very much!
My application does not crash any more. Well, at least it didn't
crash at the `usual' point, and it's still running now, and up to now
the results are more or less equal to those with non-ghosted vectors.
If this remains to be true until the application finishes, I think
that we can consider the ghosted vectors as finished and enable them
on default; wouldn't you agree?
Of course, my residuals are again slightly off (fifth version now).
I think I should try out what happens when I switch back to
non-ghosted vectors now. I will do that as soon as the current run
has finished (which will not be before tomorrow).
>> By the way, I observed another very strange thing: If I change the values
>> of {x,y,z}{min,max} of the start grid (as in the comments of the test
>> program), it crashes already on the first refinement step and at a
>> completely different point, that is in elem.h, line 1744. (That's the
>> assert in Elem::compute_key() with four arguments.) That does not make any
>> sense at all to me.
>
> The error doesn't seem to make sense, but then neither does your
> function call. ;-) You got confused about parameter order, and
> passed in xmin=xmax=0.0 and zmin=zmax=1.0.
Oh, I should have known this since I ran into that pitfall at least
once before. I somehow find the required parameter order
counterintuitive, but I can't state any reason why.
>> Anyway, complete confusion is a good state to start vacations with, isn't
>> it?
>
> Well, I hope "it's probably fixed now" is a good way to come back.
Well, it's actually one of the best ways to come back, which does,
however, not mean that it's a good way. I mean, "come back from a
vacation" and "good way" kind of contradict each other, don't they?
Best Regards,
Tim
--
Dr. Tim Kroeger
tim.kroeger@... Phone +49-421-218-7710
tim.kroeger@... Fax +49-421-218-4236
Fraunhofer MEVIS, Institute for Medical Image Computing
Universitaetsallee 29, 28359 Bremen, Germany
|