Samples order in the SliceRequestTraces does not depend on axis direction.
We had used the "VolumeDataAccessManager::SliceRequestSamples" api for making slices this way:
- Obtaining number of samples for each axis via
axisDescriptors[i].GetNumSamples()
; - Obtaining min-max world coordinates of boundary points, i.e. at
0
andGetNumSamples() - 1
; - Creating grid of 3D slice world coordinates within the min and max;
- Translating them to Voxel indexes via
WorldCoordinatesToVoxelIndexFloat
; - Applying
RequestVolumeSamples
function.
Now we have migrated to SliceRequestTraces
along the traceDimension = 0
, i.e. vertical axis, let us name it "Z" axis. And we noticed in the RequestVolumeSamples
output a point with min world "Z" coordinate (for example, -1000
) corresponds to the bottom (deepest) point in the source seg-y, and max (for example,0
) corresponds to the top, i.e. the "Z" axis directed from deep to surface. But in the SlicRequestTraces
output the first point in the trace corresponds to the top (surface) sample, last one - to the bottom (deepest) one, as in the surce seg-y. So we have questions:
- Is the samples order same as in the source seg-y? If yes, are there seg-ys that store trace in inverse order (deepest point first);
- Is the samples number same as in the source seg-y? I.e. in all obtained by the "SliceRequestTraces" traces?
- Does the samples number along Z in the
RequestVolumeTraces
result always equal toaxisDescriptors[0].GetNumSamples()
?