We currently have only one way to tell a mesh not to do renumbering:
pass in "true" to MeshBase::prepare_for_use(). Would it be reasonable
to replace this API with a direct public accessor for
MeshBase::_skip_renumber...? That way users would be able to control
renumbering even when the method c
Firstly, we heavily use this option - we _never_ renumber (when possible -
it's not possible with ParallelMesh for instance).
Secondly: Please, for the love of god, can we get rid of this being a
double negative?
I vote for:
MeshBase::allowNodeAndElemRenumbering(bool)
Or the like...
Derek
On
On Tue, 16 Oct 2012, Derek Gaston wrote:
> Firstly, we heavily use this option - we _never_ renumber (when
> possible - it's not possible with ParallelMesh for instance).
I'll take that as another vote for "don't remove the existing option
until the new option has been available for a couple rel
On Tue, Oct 16, 2012 at 10:01 AM, Roy Stogner wrote:
> I'll take that as another vote for "don't remove the existing option
> until the new option has been available for a couple releases".
Actually - it's fine with me if you want to change it immediately. I hate
not renumbering by passing True
I'm for the immediate change as well. Since I don't recall discussing this
option on list with anyone other that INL, I'd say of Derek is happy in this
case we are good to go.
-Ben
On Oct 16, 2012, at 11:07 AM, "Derek Gaston"
mailto:fried...@gmail.com>> wrote:
On Tue, Oct 16, 2012 at 10:01
