I’ve noticed that ParaView renumbers points and cells from imported data in such a way that they start from 0. So, for example, it shows cells 0 and 1 when my elements are originally named 1 and 2. This can be quite troublesome when exporting data together with IDs for further use. Thus, it would be great if you could add an option to disable this renumbering and use original numbers for imported data.
This cannot ba a global option, however when origin Id matter, the reader could provide the original ids as a field on the data. Which file format are you looking at @FEngineer ?
I’m using CalculiX results files (.frd) converted to .vtk. I also have input files for that solver and nodes are defined there in order using the following syntax:
But I don’t know if those could be used to create fields with proper names (starting from 1). It would be best to take the numbering from .frd if possible.
All right, I’ll contact its provider. I thought that ParaView renumbers the nodes so that they always start from 0. Is there a workaround for that in ParaView ?
I see. But I don’t know if and when this will be changed in the converter so it would be good to have an option to create a field with IDs starting from 1 if possible.
@mwestphal I got the reply from the developer of this .frd to .vtk converter. He said that, according to VTK User’s Guide (19.3 VTK File Formats chapter), IDs have to start from 0 in vtk files. And indeed there’s such information in that document:
Indices are 0-offset. Thus the first point is point id 0.
Does it mean that converters to .vtk have to obey this rule (also for cells) and that’s why IDs in ParaView always start from 0 ?