Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Don't merge this yet! I've been playing around to simplify the python syntax when working with vectors. The changes here are a bit of a hack, but they allow the user to set and get params that are 3-vectors in a nicer way:
Instead of
This would allow you to do
Similarly, getter returns a Vec3d:
No changes on the c side are necessary but one could implement the same hack there.
We've talked about this sort of thing many times before. So I'm probably ignoring a ton of side effects.
Can you remind me, what was the reason not to implement a three vector type as an option for a param?
Side note: Unfortunately numpy doesn't convert Vec3d to a sensible numpy array when using
np.array(v)
, so it can't easily be used in assignments. I have narrowed down the issue, but can't seem to find a workaround. The getter could just return a python list instead of a Vec3d to fix that.