SEIS Rule Structure (P1)
As a ExSeisDat Developer I want a SEIS specific Rule structure for reading / writing SEIS file headers.
The current Rule structure can be renamed to SEGY_Rule. An interface Rule class can replace SEGY_Rule, with SEGY_Rule inheriting from it. And a SEGY_Rule instance should be attached to the SEGY reader / writer, and a SEIS_Rule instance attached to the SEIS reader / writer.
We will only worry about standard headers for the moment.
The hard-coded SEGY header byte locations have been removed from the existing rule structure. Now the SEG-Y rules get the byte offsets from a separate file in a similar fashion to the SEIS rules.
System Test Changes:
Coordinate Headers for SEGY (source X, Source Y, Receiver X, Receiver Y) was being read in as a float, while it was being stored in the SEGY file as a double. They are now read in as doubles to prevent precision loss.
C++ API Changes:
C API Changes:
CREATED ON 06/06/2018