On Thu, 14 Jan 2016, Salazar De Troya, Miguel wrote:
Sorry the last statement is wrong. Leaving partition_agnostic=true with a
SerialMesh doesn’t return the same assertion error, but the vector written
and the vector read are not the same when I print them. The values seem to
be in different order.
Yes, that's as expected. They're written out in a Hilbert
space-filling curve order, to make initial repartitioning easier when
they're read in again.
In that case, what would be the compatible way to restart the mesh if I
still leave partition_agnostic=false?
I'm not positive, since I don't use this myself. In general it's
*not* safe to have your code depend on indexing. We keep dof indices
contiguous on processors, which requires shifting every index with
every refinement/coarsening step, for example.
Probably set skip_renumbering on before reading the Mesh?
Leaving partition_agnostic=true doesn¹t avoid the assertion either
for me.
You know what? It doesn't for me either, my previous reports to the
contrary. But that use case *should* work, and does work on lots of
other meshes I've tried. I'll keep looking into it.
Thanks,
---
Roy
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users
