Hello,
i would like to ask for the homogenization of what we ‘see’ on the spreadsheet and what we ‘use’ in python (regarding the names of fields). one example of this is ‘Point Id’, i wanted to use it:
but instead it one should use “id”
same thing when trying to extract specific data in python using fetch, if one wants to get any field of the spreadsheet one would use:
fieldData=data.PointData[field]
but for specific filters this can be called differently such as points/pointsLocations which in practice are the same (coordinates of the points on the filter), but to get them in fetch we need to use completly different things:
fieldData=data.PointData['PointLocations']
or
fiedlData=data.Points[:]
I understand that in the ‘back’ are not the same, but for the user they are. would be nice that this small discrepancies would be homogenized, to smooth out the GUI to python transitions sometimes.
sorry if i was not clear. the issue itself is concerning what we ‘see’ in the spreadsheet view (in regards to the column names) and how to acces this data in python
for example:
when you want to select using QuerySelect if you have your filter that in the spreadsheet you see the column Point ID, and you want to select the ids [4,19,99], one would think to use:
when we want to extract an array of a filter in paraview we need to:
data=dsa.WrapDataObject(servermanager.Fetch(filter)) #get the data of the filter
fieldData=data.PointData[field] #get the specific array that we are looking for (ie., field)
what I was pointing with my original post, is that the line of fieldData will work for every field that is shown in a filter (so each column of the spreadsheet view of the filter), but there are some columns on the spreadsheet that are not accessible using this, (as they are not data arrays) such as Point ID, Points, Points_Magnitude, among others, that for example, they will be accessible using fiedlData=data.Points[:] instead.
Specially as the data.PointData[field] does not give any warning in case of giving a wrong field and return simply a paraview.vtk.numpy_interface.dataset_adapter.VTKNoneArray this is sometimes quite annoying (as it is not evident why your script is not working and it is because you have a NoneArray as you tried to recover a column of the spreadsheet with the wrong command and can make crash one’s script easily.
my post was to be able to unify this, ie., be able for example to do: fieldData=data.PointData['Points'] and get the corresponding array. basically be able to access everything we see on the spreadsheet by using the name of the specific column in the spreadsheet.
be able to use this names directly:
