Re: [Libmesh-users] !libmesh_assert_pass' failed during an AMR operation

[Stogner, R. H <roy...@ic...>]

On Tue, 5 Feb 2019, Salazar De Troya, Miguel wrote:

> What's the motivation to have the option unique_id enabled? Speed? Consistency?

Paranoia.  If you don't have a unique_id build then it should
probably be fine to use plain ids and disable renumbering in the read
code, I'd just like to have one less possible discrepancy to worry about.
---
Roy

> Thanks
> Miguel
>
> On 2/5/19, 1:53 PM, "Stogner, Roy H" <roy...@ic...> wrote:
>
>
>    On Tue, 5 Feb 2019, Salazar De Troya, Miguel wrote:
>
>    > How can I save the mesh with unique_ids?
>
>    If you have unique_id enabled at configure time then it'll be
>    automatically saved when you write out xda/xdr/cpa/cpr.
>
>    > Which format would be the best to save the refinement flags?
>
>    ASCII, with one unique_id+refinement flag pair on each line.
>    ---
>    Roy
>
>    > Thanks
>    > Miguel
>    >
>    > On 1/31/19, 12:10 PM, "Stogner, Roy H" <roy...@ic...> wrote:
>    >
>    >
>    >    On Thu, 31 Jan 2019, Salazar De Troya, Miguel wrote:
>    >
>    >    > Would it be possible for me to send you the mesh in CPR format just
>    >    > right before calling test_unflagged() in
>    >    > MeshRefinement::refine_and_coarsen_elements()? Would that help to
>    >    > debug this issue? Not sure if the mesh in CPR actually stores the
>    >    > flags for refinement.
>    >
>    >    It doesn't, I'm afraid.  I'd love it if you could send me something
>    >    that reproduces the problem, but it wouldn't be that easy.  Maybe save
>    >    a .cpa (for ease of examination) with unique_ids and manually write
>    >    out a separate file with refinement flags?
>    >    ---
>    >    Roy
>    >
>    >
>    >
>
>