Extract control points for elastic random deformations
See original GitHub issue🚀 Feature
Extract transformation parameters for random deformations
Motivation (and Pitch)
Like in @fepegar gist, we want to be able to observe the control points(xx, yy
), as well as the deformation vectors u, v
.
That being said, ideally I’ve been thinking about something like -
import torchio as tio
transform = tio.RandomElasticDeformation(...)
u, v = transform.get_deformation_vectors()
x, y = transform.get_control_points()
Alternatives
I’ve already seen that there is a get_params
method in RandomElasticDeformation
, but I think that it generates new parameters for each method call. am I right? This method seems to provide a solution for u, v
but not x, y
.
Additional context
I mainly wondered if I miss anything, I really went into the documentation, source code and the gist but wasn’t 100% sure the feature is really missing.
If it does miss, I would love to help with a pull request.
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Deformation - elasticdeform documentation - Read the Docs
Elastic deformation with a deformation grid. The procedure generates a coarse displacement grid with a random displacement for each grid point.
Read more >On the Extraction of Elastic–Plastic Constitutive Properties ...
This method proves to be a powerful tool for calibration of material models. The final parameters produce a simulation that tracks the local...
Read more >Bayesian Estimation of Deformation and Elastic Parameters in ...
In this work we include elastography in the registration process by formulating these parameters as unknown random variables with associated ...
Read more >Real-Time Surface Deformation Recovery from Stereo Videos
We first use a stereo matching method to extract depth ... (d) Dense connections between control points with a silicon heart phantom.
Read more >Mesh Deformation, a Unity C# Tutorial - Catlike Coding
Once we have the mesh, we can extract the original vertex positions. We also have to keep track of the displaced vertices during...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks! good to know about the LPS orientation. I close this to not confuse anyone.
Looks good to me 😃
Just one small comment. LPS orientation is because ITK uses that convention (which DICOM also uses). In e.g. the VTK world, the coordinates would be RAS (I think. Orientation stuff is confusing!).
Displacement at the borders are zero because of the
locked_borders
kwarg inRandomElasticDeformation
.