It seems to me that once the Control vectors are sent to the AffineWarper that a single Affine transform could be calculated and applied to all Observed Features as they come through.
Solved
Is there a way to trick (or configure) the AffineWarper into non blocking?
+2- Contributor
Best answer by fmelizard
Sounds like we need a "Control Vectors Come First" mode on that baby. Then we could do as Reed would like. I'll post an idea.
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
+2- Contributor
hi Annabelle, performance. Yes. It seems like it should not need to block if all Control vectors are supplied before Observed features. @DaveAtSafe gave me a tip to use the 3DAffineWarper. So will try that. Thanks for the help.
+21- Safer
- Best Answer
Sounds like we need a "Control Vectors Come First" mode on that baby. Then we could do as Reed would like. I'll post an idea.
+21- Safer
Sounds like we need a "Control Vectors Come First" mode on that baby. Then we could do as Reed would like. I'll post an idea.