# ParaView 6.2.0-RC1 throws errors for non unique nodes
**URL:** https://discourse.paraview.org/t/paraview-6-2-0-rc1-throws-errors-for-non-unique-nodes/17668
**Category:** In Situ Support
**Created:** [July 31, 2026, 4:30pm UTC](https://discourse.paraview.org/t/paraview-6-2-0-rc1-throws-errors-for-non-unique-nodes/17668 "2026-07-31T16:30:12Z")
**Posts on this page:** 11
**Page:** 1
### Author:  [@Alexandre\_Minot](https://discourse.paraview.org/u/Alexandre_Minot)
#### Post date: [July 31, 2026, 4:30pm UTC](https://discourse.paraview.org/t/paraview-6-2-0-rc1-throws-errors-for-non-unique-nodes/17668/1 "2026-07-31T16:30:13Z")
Hello,
I am getting this error while testing ParaView 6.2.0-RC1:
```auto
( 2.503s) [pvbatch] vtkDataAssembly.cxx:591 ERR| vtkDataAssembly (0x7c87cc2a7f40): A child node with name 'SIDEWALL' already exists under parent with id=4
( 2.504s) [pvbatch] vtkDataAssembly.cxx:591 ERR| vtkDataAssembly (0x7c87cc2cdda0): A child node with name 'STREAM_00_SIDEWALL' already exists under parent with id=0
( 2.505s) [pvbatch] vtkDataAssembly.cxx:591 ERR| vtkDataAssembly (0x7c87cc296820): A child node with name 'STREAM_00_SIDEWALL' already exists under parent with id=0
( 2.505s) [pvbatch] vtkDataAssembly.cxx:591 ERR| vtkDataAssembly (0x7c87cc296ac0): A child node with name 'STREAM_00_SIDEWALL' already exists under parent with id=0
( 2.511s) [pvbatch] vtkDataAssembly.cxx:591 ERR| vtkDataAssembly (0x7c87cc20a900): A child node with name 'STREAM_00_SIDEWALL' already exists under parent with id=0
```
My guess is that it coming from the Conduit Source. Has something changed there?
Thanks,
Alexandre
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [July 31, 2026, 8:33pm UTC](https://discourse.paraview.org/t/paraview-6-2-0-rc1-throws-errors-for-non-unique-nodes/17668/2 "2026-07-31T20:33:00Z")
Hi Alexandre,
Duplicate node names aren’t allowed among siblings sharing the same parent node in a `vtkDataAssembly`. This error message is new in ParaView 6.2, but it’s probably pointing out a problem with duplicate names that has existed in the data assembly construction for a while.
In fact, I just checked the CONVERGE CFD dataset in the VTK test data suite ([https://gitlab.kitware.com/vtk/vtk/-/tree/master/Testing/Data/CONVERGETimeSeries?ref\_type=heads](https://gitlab.kitware.com/vtk/vtk/-/tree/master/Testing/Data/CONVERGETimeSeries?ref_type=heads)) in ParaView 6.2.0-RC1, 6.1.1, 6.0.1, and 5.13, and I get errors similar to yours in 6.2.0-RC1 on startup, but in the other versions I don’t get error messages until I click on a SIDEWALL node in the Information Panel, when I get
```auto
Warning: In vtkSMOutputPort.cxx, line 95
vtkSMOutputPort (0x3027424c0): GetSubsetDataInformation selector matched multiple nodes. Only first one is used.
```
So this new error message is reporting a situation that will lead to the warning you could see in older versions of ParaView, namely, that there are two SIDEWALL siblings under a node - they should be named uniquely. Note that in the vtkCONVERGECFD reader, we are not doing anything to ensure sibling node names are unique - we should fix that. There is a secondary issue where we shouldn’t set the block meta information NAME() key in the partitioned dataset collection the reader produces.
Since you mentioned Conduit Source, the solution for this case is to ensure SIDEWALL and STREAM\_00\_SIDEWALL are not repeated among sibling nodes. Is that possible to do?
---
### Author:  [@Alexandre\_Minot](https://discourse.paraview.org/u/Alexandre_Minot)
#### Post date: [July 31, 2026, 8:39pm UTC](https://discourse.paraview.org/t/paraview-6-2-0-rc1-throws-errors-for-non-unique-nodes/17668/3 "2026-07-31T20:39:44Z")
Thanks for your answer. They are unique in the Conduit Source, but one is named SIDEWALL, and the other SIDEWALL@. ParaView strips the @ somewhere. We have stopped adding @ to our names, but we still have cases out there that have them.
My question was why is it an error now? But I guess the answer is simply that an error was added.
I’ll figure something out on our end, thanks.
Thanks
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [July 31, 2026, 8:57pm UTC](https://discourse.paraview.org/t/paraview-6-2-0-rc1-throws-errors-for-non-unique-nodes/17668/4 "2026-07-31T20:57:29Z")
The ‘@’ is not a valid character for selector expressions, so when the data assembly node is added, the ‘@’ is stripped away. Maybe not the most graceful thing to do, and it results in the duplication in question.
I am thinking the new error and discarding of the node with the duplicate name, may be too severe as it changes the tree structure constructed by different data sources later on. We should warn about that case for sure, but not adding the node to the data assembly likely goes too far. What do you think, @spyridon97 ?
---
### Author:  [@Alexandre\_Minot](https://discourse.paraview.org/u/Alexandre_Minot)
#### Post date: [July 31, 2026, 9:00pm UTC](https://discourse.paraview.org/t/paraview-6-2-0-rc1-throws-errors-for-non-unique-nodes/17668/5 "2026-07-31T21:00:34Z")
Yes, I think taking the first node rather than none makes sense. Especially since ParaView strips a lot of characters.
---
### Author:  [@spyridon97](https://discourse.paraview.org/u/spyridon97)
#### Post date: [August 3, 2026, 5:45pm UTC](https://discourse.paraview.org/t/paraview-6-2-0-rc1-throws-errors-for-non-unique-nodes/17668/6 "2026-08-03T17:45:28Z")
Adding 2 nodes with the same name can lead to several problems in paraview… metadata information is wrong, block selection is wrong. multiblock inspector not working. Many things are wrong in general.
Conforming by the requirements of what VTK instructs is the right call IMHO, i.e. not using invalid charachters.
As far as resolving name duplication, there are 2 solutions.
1. the user is responsible for providing unique names that abide by the VTK guidelines
2. the reader will make sure that each node will have a unique legal node name.
Personally, i think the first is the right solution, but if the second is needed, it could be implemented.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [September 1, 2026, 9:41pm UTC](https://discourse.paraview.org/t/paraview-6-2-0-rc1-throws-errors-for-non-unique-nodes/17668/7 "2026-09-01T21:41:33Z")
> [@spyridon97](#):
>
> Adding 2 nodes with the same name can lead to several problems in paraview… metadata information is wrong, block selection is wrong. multiblock inspector not working. Many things are wrong in general.
Very true.
> [@spyridon97](#):
>
> 1. the user is responsible for providing unique names that abide by the VTK guidelines
I’m not sure who the user is in this case - the writer of the file that VTK reads? VTK’s data assembly has the unique sibling name requirement, not a file format, so I don’t think this is practical.
> [@spyridon97](#):
>
> 1. the reader will make sure that each node will have a unique legal node name.
I have this MR up that ensures uniqueness in a bunch of readers in VTK and the `vtkConduitSource`. [https://gitlab.kitware.com/vtk/vtk/-/merge\_requests/13651](https://gitlab.kitware.com/vtk/vtk/-/merge_requests/13651)
Note that the MR doesn’t cover other VTK readers defined outside VTK. We should augment the error message to suggest how to create a unique node name, once there is a function available in `vtkDataAssembly` to determine one. I wonder if we should even downgrade the error behavior to a warning and add the duplicate-name child anyway for a release and change it to an error in the next release.
---
### Author:  [@Alexandre\_Minot](https://discourse.paraview.org/u/Alexandre_Minot)
#### Post date: [September 1, 2026, 10:14pm UTC](https://discourse.paraview.org/t/paraview-6-2-0-rc1-throws-errors-for-non-unique-nodes/17668/8 "2026-09-01T22:14:38Z")
Hey Cory,
I think this is a good change, thanks for working on it. I don’t see the change implemented in the CGNSReader. Did I miss it?
Alexandre
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [September 1, 2026, 10:23pm UTC](https://discourse.paraview.org/t/paraview-6-2-0-rc1-throws-errors-for-non-unique-nodes/17668/9 "2026-09-01T22:23:51Z")
`vtkCGNSReader` produces a `vtkMultiBlockDataSet`, so duplicate sibling names would come into play when creating a `vtkDataAssembly` from the `vtkMultiBlockDataSet` meta information. That’s handled by
```auto
bool vtkDataAssemblyUtilities::GenerateHierarchyInternal(
vtkMultiBlockDataSet* input, vtkDataAssembly* hierarchy, vtkPartitionedDataSetCollection* output)
```
and duplicate names are addressed there. So `vtkCGNSReader` should be covered.
---
### Author:  [@Alexandre\_Minot](https://discourse.paraview.org/u/Alexandre_Minot)
#### Post date: [September 1, 2026, 10:34pm UTC](https://discourse.paraview.org/t/paraview-6-2-0-rc1-throws-errors-for-non-unique-nodes/17668/10 "2026-09-01T22:34:13Z")
@gsabhishek , can you make a note to potentially implement Cory’s change in your new CGNS reader to partitioned datasets?
Thanks
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [September 9, 2026, 1:16pm UTC](https://discourse.paraview.org/t/paraview-6-2-0-rc1-throws-errors-for-non-unique-nodes/17668/11 "2026-09-09T13:16:41Z")
You can still make those changes, but we have realized that vtkDataAssembly never had a unique sibling node name requirement, and have instead addressed ParaView’s complaints related to selectors that select more than one node.
We have reverted the error message and the refusal of vtkDataAssembly to add nodes only if their name is unique in [https://gitlab.kitware.com/vtk/vtk/-/merge\_requests/13663](https://gitlab.kitware.com/vtk/vtk/-/merge_requests/13663). That fix for this issue will be i ParaView 6.2.0-RC2.