-
-
Notifications
You must be signed in to change notification settings - Fork 62
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
Added documentation for nearest-neighbor-gradient [cont] #169
Conversation
"There are three main variants of mapping" should become four I think. |
When using the `rowsFirst` parameter, the following format is required: | ||
|
||
```cpp | ||
( v0x_dx, v0y_dx, v1x_dx, v1y_dx, ... , vnx_dx, vny_dx, | ||
v0x_dy, v0y_dy, v1x_dy, v1y_dy, ... , vnx_dy, vny_dy ) | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This goes beyond the documentation part, but considering that the 'gradient matrix' is a Jacobian, I think the rowFirst
argument should be a column first, as the Jacobian contains the derivative in a particular direction in a column, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good to go except minor tweaks.
"There are three main variants of mapping" should become four I think.
yes 👍
When using the `rowsFirst` parameter, the following format is required: | ||
|
||
```cpp | ||
( v0x_dx, v0y_dx, v1x_dx, v1y_dx, ... , vnx_dx, vny_dx, | ||
v0x_dy, v0y_dy, v1x_dy, v1y_dy, ... , vnx_dy, vny_dy ) | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Co-authored-by: Benjamin Uekermann <benjamin.uekermann@gmail.com>
This is now ready to merge once #169 will be merged. |
Follow-up to #166