On Thu, Mar 10, 2016 at 11:03 AM, Cody Permann <codyperm...@gmail.com>
wrote:
> "DistributedMesh" is good, but it might still have some of the same
> problems we encounter with the name "ParallelMesh": People might think. "Oh,
> I want distributed, I'm running on a distributed computer, or I'm running
> in distributed memory...".
>
> Perhaps half of the battle is really improving the documentation and even
> providing use cases for when you might move to "ParallelMesh".
>
Agreed, the documentation for both Serial and ParallelMesh is currently
very short, and what is there is misleading. I think we should take off
the "Don't use this class unless you're developing or debugging it." from
ParallelMesh, for example.
That being said, people sometimes don't read documentation at all...
> People often just don't have a good feel for what is big. Every once in
> awhile we get the my problem doesn't scale message on our list. Somebody is
> trying to scale a mesh with a thousand elements to several dozen
> processors... I have this link bookmarked for that case:
> http://www.mcs.anl.gov/petsc/documentation/faq.html#slowerparallel
>
> We need the same thing for when to use one mesh type over the other.
>
Yeah, at least a Wiki page discussing this would be cool.
--
John
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
