`DataSet.vectors` does not work with cell data
See original GitHub issueDescribe the bug, what’s wrong, and what you expect:
DataSet.vectors
does not work with cell data as it adds to DataSet.point_arrays
.
This is easily fixed, but I would be in favor of totally deprecating this functionality as it duplicates the DataSet["my_vector_name"] = data
functionality. It is confusing to me why there is a special method here. It was also confusing in https://github.com/pyvista/pyvista-support/issues/448 and partially in https://github.com/pyvista/pyvista-support/issues/438.
To Reproduce
Please include a code snippet to reproduce the bug in the block below:
mesh = pv.Plane()
mesh.vectors = np.ones([mesh.n_cells, 3])
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Vector data not identified as VECTORS · Issue #1431 · pyvista ...
I was expecting a VECTOR dataset attribute with some kind of default name (I'm not sure how one assigns a name to vector...
Read more >Failed Build of R Data Package: Long vectors not supported yet
Any suggestions on how to build and install this data package? This code used to work; however, the data set has increased in...
Read more >Vector Data & Raster Data: Converting Between Different ...
Vector Data & Raster Data: Converting Between Different Geometry Models. Ready to learn about spatial data and how it all works together?
Read more >15 Easy Solutions To Your Data Frame Problems In R
Discover how to create a data frame in R, change column and row names, access values, attach data frames, apply functions and much...
Read more >Missing Values in R
Missing Values in R. Missing Values. A missing value is one whose value is unknown. Missing values are represented in R by the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I think #1431 should suffice for that. Lets continue moving that piece of the conversation there.
Yes! Thank you. I did mean #1431, and I agree that the information is best continued there (I didn’t realize at the time it had been transferred). I will edit my comment with the correct issue number, and try to clean things up a bit. I’ll also post my current work around in #1431.