Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Inconsistent assumptions about vector space (dimension)
See original GitHub issueThe vector operations on compas.geometry.basic (source) are inconsistent in the way they assume the vector space. Some of them work on arbitrary length vectors, while others are hard-coded to 3D vectors, and documentation only refers to support of 3D vectors, even in the cases where the function support arbitrary length.
For example, dot_vectors, add_vectors, subtract_vectors, scale_vector and many others work on any length, but cross_vectors, length_vector, normalize_vector and others are hard-coded to 3D.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
was hoping you would say that. alright, will do!
perhaps we should just remove
norm_vector(s)power_vector(s)as these are functions that make more sense in a general vector calculus context and not so much in a geometrical one.