On Thu, Mar 10, 2016 at 2:31 PM, John Peterson <jwpeter...@gmail.com> wrote:
>
>
> On Thu, Mar 10, 2016 at 11:44 AM, Derek Gaston <fried...@gmail.com> wrote:
>
>> I do really think the classes should be renamed. Coming from the outside
>> I would totally think that I need to use SerialMesh when running in serial
>> and ParallelMesh when running in parallel. No amount of documentation
>> could stop me from trying it that way first ;-)
>>
>> I do somewhat agree with your reservations about "DistributedMesh"
>> though... but I still think it will be way better than what we have. It
>> doesn't necessarily map directly to something they know of... so at least
>> it will make them pause and try to understand what it means / implies and
>> read the (hopefully improved) documentation.
>>
>> From that standpoint I still kind of think "DecomposedMesh" is maybe a
>> little better... it lets people know right away that the mesh is being
>> split up. For instance: ReplicatedMesh vs. DecomposedMesh would have made
>> perfect sense to the guy that emailed libmesh-users today. He would have
>> immediately known that since he wants a copy of the mesh on every processor
>> that he wants to use ReplicatedMesh.
>>
>> We could also go even simpler:
>>
>> SerialMesh -> BasicMesh
>>
>> ParallelMesh -> AdvancedMesh
>>
>> That way it's obvious that one is going to be more complicated than the
>> other... and you should really use BasicMesh until you really have a need
>> to go with the more "Advanced" option...
>>
>
> Basic/Advanced isn't bad actually.
>
I don't like this, I still much prefer "Replicated/Distributed".
Replicated/Distributed indicates the mesh is being replicated/distributed
pretty clearly, I think.
> It's enough to make it obvious what Mesh you should start with as a
> beginner,
>
Sure, but so does a Wiki page.
> but not enough to imply anything about how it actually works or anything
> about serial vs. parallel
>
Which is terrible, I think. I think the names should be as self-documenting
as possible, not catering to someone whose inclination is the completely
ignore the docs.
> , and thereby forces you to read the docs if you want to know more (which
> is what we want).
>
Is this the type of user that we want to cater to when naming things? I
would rather things be more self-documenting.
My two cents anyway.
> There's also always "ExascaleMesh" instead of ParallelMesh... ;-)
>
:)
------------------------------------------------------------------------------
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
