On Thu, 22 Dec 2011, Vetter Roman wrote: > please consider adding the attached patch (for r5017) to the trunk. > It adds the possibility to specify a custom random seed for the mesh > distortion in MeshTools:Modification::distort in a > backwards-compatible way. This is useful for solving the same > problem with differently distorted meshes (e.g., for statistics).
This looks decent to me, but with one big concern: I'd like MeshTools::Modification::distort() to be made ParallelMesh-compatible eventually, and it's going to be really hard to do so in a way that doesn't break the new implicit "same-seed-gives-same-results" guarantee here. Would it make sense to parallelize it now (breaking the consistency with previous distort() results) *before* anyone has a bunch of differently-seeded distorted meshes depending on that consistency? --- Roy ------------------------------------------------------------------------------ Write once. Port to many. Get the SDK and tools to simplify cross-platform app development. Create new or port existing apps to sell to consumers worldwide. Explore the Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join http://p.sf.net/sfu/intel-appdev _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
