[Dune] [#499] mightVanish() on UGGrid buggy

[Dune]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#499 - mightVanish() on UGGrid buggy
User who did this - Ole Klein (oklein)

----------
@Oli: This never happened to me, I always had all relevant information transferred to coarser elements just by looking at the mightVanish flag. If an element without a marked sibling had vanished, I should have run into problems testing my adaptivity code for PDELab, since I only save the information that is absolutely necessary (the data on the leaf, and a local projection onto the father or grandfather if I find a mightVanish flag).
But then again, this also didn't happen before I locally applied the patch.
At least while using my test refinement scheme (random refinement) this should have cropped up sooner or later.
I may ask Stefan when I next see him.

The colors (or, more precisely, integer values) are simply the return values of the functions mentioned in the filenames called on the corresponding element, i.e.:

getMark:
-1 -- coarsening requested
 0 -- not marked
 1 -- refinement requested

mightVanish:
 0 -- Dune thinks this will not vanish
 1 -- Dune thinks this might vanish
----------

More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=499#comment2226

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.