Skip to content
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

Control over boundary conditions on cubic splines. #32

Closed
fryguybob opened this issue Aug 4, 2012 · 3 comments
Closed

Control over boundary conditions on cubic splines. #32

fryguybob opened this issue Aug 4, 2012 · 3 comments

Comments

@fryguybob
Copy link
Member

(Imported from http://code.google.com/p/diagrams/issues/detail?id=66. Original issue from fryguy...@gmail.com on February 16, 2012, 01:36:31 PM UTC)

In some cases it would be nice to combine cubic splines with other shapes and retain some degree of smoothness. For instance, you might want a specific segment to be straight. Metapost, NURBS, and Spiro, all allow for building curves like this, but I think that cubic splines could also be formulated with boundary conditions much like how the join in a closed cubic spline is solved with a fully symmetric tri-diagonal matrix.

@ghost ghost assigned fryguybob Aug 4, 2012
@bergey
Copy link
Member

bergey commented Sep 21, 2013

The metafont code in -contrib at least partially addresses this. It's allows making segments straight, or specifying tangent direction at either end. It still needs work to connect smoothly with the rest of diagrams.

@byorgey
Copy link
Member

byorgey commented Sep 22, 2013

@fryguybob, did you have other ideas on what this might mean, which is not addressed by the metafont stuff? Maybe this is another one of those tickets that we should either close or make more specific.

@fryguybob
Copy link
Member Author

I think my original opening of the issue was for a "nice thing to have" but I've never worked out what it would take in the particular cubic splines that we have. Metapost clearly has worked out the details so if that is working we should just close this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants