`get_header` on container and block gives different results

[kerim371]

Hi,

I just encountered a situation that may be described by the picture attached.
So I have a container and i'm trying to retrieve SourceX from that container and from block of that container.
I believe I should find an answer in this snippet but haven't understand yet.

SegyIO v0.8.3

[kerim371]

Just in case I've found a problem.
My SEGY file used to have elevation and coordinate scaler header = 0.
Once I changed it to 1 it started to work properly.

Anyway it is strange that headers given from container differ from headers given by seis block. Or maybe it is for made intensionnally for the speed purpose...

[mloubout]

The scaling is used yes, but you can turn it off with scale=false. I'll double check the consistency

[kerim371]

I just figured out that get_header(SeisBlock) return one column vector of values for each trace while get_header(SeisCon) return two column matrix: 1st col min value for the shot and 2nd max value.

Maybe in the future get_header(SeisCon) could be renamed to something like get_header_limits(SeisCon).
Though it is not really important.

[mloubout]

That's a fair point. We wanted to be consistent while keeping the lookup table light (storing all the headers of a SeisCon would be quite big). Not sure what a good alternative would be but will think about it