Behavior for files with irregular inlines/crosslines
(sorry, I will try to divide issue into parts, as for some reason it gets constantly marked as spam)
While playing with openvds we accidentally created synthetic segy files which are imported into vds incorrectly (roundtrip breaks). We are not sure how likely files like that can appear in reality, but our domain knowledge source tells us that it is possible in theory.
- File broken1.segy with ilines
[1, 6, 11, 15]
(Stride is 5, last element is at distance 4) - File broken2.segy with ilines
[1, 6, 11, 16, 21, 26, 27]
(Stride is 5, last element is at distance 1)
Some rows just get lost, never to be found in vds.
Main observation is that as openvds for some reason on purpose ignores the distance between two last values, we need to supply a different distance to last element to reproduce this behavior.
How short/long is the distance of the last element might also matter as changing this suspicious piece of code (as it seems that a + (a-b)%c - b
is not divisible by c
) fixed only one of those cases for me.