Unique name requirement for nodesets and sidesets

It appears that in 5.10.0-RC1, it is now required that names are unique across nodesets and sidesets:

ERROR: Duplicate names detected.
       The name 'bottom' was found for both SideSet 0 and NodeSet 0.
       Names must be unique over all types in a finite element model.

Can someone please explain the rationality for this? Within MOOSE (GitHub - idaholab/moose: Multiphysics Object Oriented Simulation Environment) we rely significantly on consistency in naming between nodesets and sidesets.

Hi Logan,

This restriction comes from the IOSS library. You might want to inquire over at GitHub - gsjaardema/seacas: The Sandia Engineering Analysis Code Access System (SEACAS) is a suite of preprocessing, postprocessing, translation, and utility applications supporting finite element analysis software using the Exodus database file format..

Will do. Thanks for the quick response.

EDIT: See Unique name requirement for nodesets and sidesets · Issue #251 · gsjaardema/seacas · GitHub for the continued conversation.

Pinging here because last week’s response on the GitHub discussion seems too good to be true:

You should not need any changes since the default IOSS now allows duplicate names.

It would be fantastic if this IOSS update could be incorporated into 5.10.0-RC2 when that comes out.

Right now, working around this problem after encountering it requires loading the Legacy Exodus Reader plugin, avoiding the “File / Recent” menu (which seems to encode what loader was used to attempt to load a recent file, even if the load failed!?), and selecting legacy from the popup each time we do a “File / Open” … which isn’t too hard to do, but which is a disaster to figure out how to do based on nothing more than a “Duplicate names detected” error message.

Closing the loop here. The IOSS update that supports duplicate names has been included in 5.10.0-RC2.

1 Like

Thanks for the quick turnaround!