Comments (4)
I don't understand your question. But I will try to answer few of the points.
I don't know how you assigned "minimum spacing" as [16 16 16]. In the exampleRunFile, you can only assign the initial subset size (sSize). So did you change the subset size?
The final minimum subset spacing can be selected through choice of dm as preset condition in IDVC.m. Depending on dm and initial size of volume (I), the final size of each component of u, ie u{1,1}{1,1} will be: 1:dm:size(I,1)+dm. So dm decides the size of displacement grid.
Let me know if this helps or if you have more questions.
from fidvc.
Hello,
Many thanks for your help.
In checkConvergenceSSD function, sSize and sSpacing are refining until:
% window spacing refinement. Only do if the sSpacing > 8 voxels
if (sSpacing0 > 8), sSpacing1 = sSize1/2;
And then:
% if dSSE meets first convergence criteria then refine spacing
% to the minimum value, 8 voxels.
if dSSE(end) <= convergenceCrit(1)
sSize1 = sSize0; sSpacing1 = [8 8 8];
end
In DVC function, using the last step spacing (DVC(I,sSize(i,:),sSpacing(i,:),DVCPadSize,ccThreshold);), the correlation will compare subsets with spacing of sSpacing(i,:). As a result, the result will be the displacement of grids with the same spacing. And in order to be summed with du of the previous step, the displacement will be interpolated with spacing of dm.
So my question is that if in checkConvergenceSSD, I change the minimum sSpacing to [16 16 16] and initial subset size of [128 128 64], what should I choose for dm to get the right answer? Is there any criteria for choosing dm?
Many thanks for your kind consideration
Yours sincerely
from fidvc.
Hello,
I have the same question but I could not get the answer by reading the response. I am getting a large variation in displacement by changing the choice of dm. For instance, I have 50% difference in u{1}{1}(1,1,1) between dm=4 and dm=8. If the size of displacement u{1}{1} is "1:dm:size(I,1)+dm" then logicaly at least the first array u{1}{1}(1,1,1) should be independent of dm. I was wondering what is the reason for this large difference. Please correct me if I am getting something wrong.
I would appreciate your help.
Thanks
from fidvc.
Greetings, this is Alex Landauer, a PhD student in the Franck Lab. I realize itβs been a few months, but I noticed this was still an open question, so I will propose an answer.
You can think of the "dm" as a control in the spatial filtering operation, both as a parameter of filterDisplacements
and a refinement control. Thus, changing dm will change the noise content of the image, which should be particularly noticeable at the edges (i.e. u{1}{1}(1,1,1)) since the matching inversion is less well posed.
I would expect the displacement you reconstruct to change somewhat with choice of "dm" and with dm != sSpacing you will either subsample or supersample the actual interrogation points. This may lead to unpredictable behavior that is outside the scope of our typical validation procedures. I would suggest that interpolation on the displacement is more predictable and reliable, and to let dm and minimum subset spacing be equal.
One final point, the "right" answer from any physical measurement technique, particularly one as abstracted as DIC, depends on the what you need to measure. There is a balance between noise floor and resolution, and you need to know your problem and establish sensible measurement practices with respect to it.
Let us know if you still have questions.
from fidvc.
Related Issues (20)
- Error in x, y, and z dimensions HOT 1
- calculated surface HOT 4
- Does this code use input values of type unit8 or double for vol*.mat? HOT 1
- Can I have the analytical displacement in your example files HOT 1
- Problem regrding boundary of the image HOT 3
- Rigid Registration Pre-Processing HOT 1
- 3D TFM HOT 1
- Is the FIDVC can be used for the displacement analysis of a 3D surface? HOT 1
- Parseinput HOT 1
- Strain calculations, Total displacements from incremental analysis, and very small bug HOT 5
- Question towards the displacement grid positions (m) HOT 3
- Error using mex HOT 1
- error using MEX issue HOT 1
- Code update and strain map resolution of binary image volumes HOT 4
- Computing DVC displacements HOT 1
- Incremental to cumulative displacements follow up HOT 1
- Registration 3D images using FIDVC HOT 3
- acceleration using gpu HOT 3
- mex error with Xcode 13.2.1 HOT 1
- 3D visualization HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
π Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. πππ
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google β€οΈ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from fidvc.