-
Notifications
You must be signed in to change notification settings - Fork 7
Add high level methods for sliceplot and lineplot #65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
9de68e5 to
45c6eec
Compare
|
Ah cool - this seems to work without need to interfere with the plotting backend code. As for the naming: in fact, these are still scalarplots after all. An alternative would be to just use the scalarplot method and to add a |
|
Sorry for the late answer. I somehow missed it. Thanks for the positive feedback. I like your naming suggestion to keep it as I think the cleanest solution is |
|
IMHO "hyperplane" is the dimension independent name for an n-1 dimensional affine subspace. |
|
As for the naming: we could have a dimension type parameter in HyperPlane and make type aliases for Line and Plane. |
|
After thinking more about it: In principle it might be sufficient to pass a vector or tuple of the right dimension, What really would be quite helpful in the API would be the ability to say We could internally have something like these and call them wherever the slice data are accessed: and |
|
This also circumvents the problem of exporting the pretty ambiguous types I also like the idea to pass Another, maybe really clean approach would be to pass an expression What do you think about this one? |
|
To allow Symbols and strings is easy - the example above should already do this. |
|
From my POV, the PR is now feature complete. We need an downstream change for |
|
Could you also add line plot and a slice plot example to the docs ? Maybe in examples/plotting.jl ? |
|
Sure, I added some handy examples. Stupid question: How did you make the SVG files? |
|
This is via the |
|
Ah, I see. Still not used to the workflows of this package. |
|
Ok, I ran into some weird documenter issue with the doc strings of the new |
e6089bd to
e96d062
Compare
e96d062 to
c9fe6e7
Compare
|
Hugh. CI fails due to |
This is based on WIAS-PDELib/GridVisualizeTools.jl#20
Implementation of high level methods for line and slice plotting.
The user only has to provide a generic line or plane definition to obtain a plot.
The new coordinate systems are created by isometric rotation and therefore the angles are invariant.
Examples:
Note that the intersection is about of size 2 x 0.75 in the new transformed coordinates.
There is a bug in
marching_tetrahedra, creating some holes in the plot if the tetrahedra are sliced along the facets: