|
Notes |
|
|
(0034591)
|
|
Utkarsh Ayachit
|
|
2015-06-22 09:13
|
|
|
|
|
(0034615)
|
|
Alan Scott
|
|
2015-06-25 21:53
|
|
|
Note - Following Utkarsh's fix, this appears incorrect parallel server. |
|
|
|
(0034730)
|
|
Alan Scott
|
|
2015-07-09 20:58
|
|
|
See e-mail notes sent to Utkarsh. |
|
|
|
(0034774)
|
|
Alan Scott
|
|
2015-07-14 12:49
|
|
There are two issues here - is the AMR selection fixed, and is the Hierarchical Fractal working correctly in parallel.
We believe there is a problem with the Hierarchical fractal code in parallel. This isn't this bug.
We believe that the AMR selection is fixed (which is this bug).
From an e-mail from Utkarsh:
So the issue is weird. It so happens that the Hierarchical Fractals produces incorrect image extents on the last rank when running in parallel. Consequently, when ExtractSurface it applied, it produces the lowest res grid to cover all partitions on the last rank (see attached image).
When selecting, the last process wins and hence it selects the lower-res cell from the rank #3 (I was running 4 procs here, but same is true for 2 procs).
If you don't apply "Extract Surface" but directly switch to "Surface" representation on the Fractal itself and then select it doesn't run into this issue.
Closing the bug. |
|