Open chaosphere2112 opened 7 years ago
some seem to be edge caes in the first example using:
line.y = [-60, 45]
works
The box plot isn't just the line anymore, that might an error too
I think we may not be data
having priority 0 in our pipelines, which is why the box plot isn't just the line anymore.
I'm playing with a technique to do a polar 1D plot in VCS, and I ran into some issues along the way. The biggest issue is that attempting to use a projection on a secondary object (which is something the API supports) doesn't really work, at all.
A simple test case:
which gives you a blank canvas.
This seemed odd to me, since we do essentially that exact line when plotting a polar plot of a 2D variable (via the template.box1 attribute).
I inserted some code to dump the attributes of the line object being generated for that template, and got this:
I tried assigning those exact values to a line and plotting it, but it still failed to produce any output.
I dug into the VTK objects actually being assembled, iterated across all of the points created, and still, everything was the same for both ways. After a bunch of spelunking through misc. VTK objects, I discovered the the bounds on the actors were set differently.
It turns out that the
plot
function will try and grab a "vtk_backend_grid" and pass it to this code infitToViewport
; when we plot the template,vtk_backend_grid
is passed as a kwarg, but when we plot the line straight-up, we use theXrg
andYrg
values derived from theworldcoordinate
attribute on theline
object.We definitely need to be able to correctly project stuff without plotting a variable as part of the process, so this is in the "bug" category.
Migrated from: https://github.com/UV-CDAT/uvcdat/issues/1965