Move the body of the usage function directly to the body of member function
datrw::imseedstream::help()

Place this code in a separate compilation unit.

- pass consistency check values to reading functions
- provide information regarding Mxm1 value which is used to check for data
  value continuity

Let MiniSEEDRecord store consistency check control flags in its own member
data.

- pass flags to inner reading function
- note changes in file headers

Read format modifiers and set flags for consistency checks appropriately.

Merge branch 'master' into 25-libdatrwxx-miniseed-consistency-checks

hide

  typedef typename aff::Series<T> Tinseries;

from compiler, because Tinseries is not used. The declaration itself however
might be useful as a reminder of which type the expected series container
should be.

Implement structures to hold control flags for consistency checks.

The only way to properly distinguish between references to the namespace and
the module documentation is by a prefix group_ for the group keyword.

errno is already used by system headers; leads to conflicts

Discard SVN keywords and subroutines which were used to report SVN Id at the
terminal:
- subroutine foucmd_revision
- subroutine foufil_revision
- subroutine fou_revision

So far these subroutines were only called by subroutine foucmd_help
within libfourier itself.

The parameters for the transformation into Fourier domain (selecting the
number of samples to be used) was not defined in detail.

Solve two issues in the MiniSEED module of libdatrwxx:
- do not complain about inconsistent frame count, if number of frames is just
  guessed (issue21)
- read past unused data in each MiniSEED record (issue23)

This way libdatrwxx and all tools based in the library (like any2matlab)
should be prepared to properly read recent EarthDataLogger (EDL) files.

After having made clear that incompletely filled MiniSEED records are covered
by the format specification, there is no reason to complain, if estimated
number of frames (in cases where blockette 1001 is not present in the data)
does not match actual number of frames. By deactivating this consistency check
in the case where data files do not specify number of frames, we implicitely
solve issue21.

Issue21: When reading a MiniSEED data file with incompletely filled records,
the user was confronted with a vast amount of (insignificant) warning
messages.

This reverts commit ecb2ebce.

Conflicts:
	src/libs/libdatrwxx/mseed/imseedstream.cc

Subformat "silent" is not required, since incompletely filled MiniSEED records
are considered to be in compliance with the data format specification.

This reverts commit 33845dc7.

Conflicts:
	src/libs/libdatrwxx/mseed/mseedread_mseedrecord_read.cc

Note 6 in the description of the Data Externsion Blockette [1001] specifies:
  Frame count is the number of 64 byte compressed data frames in the 4K record
  (maximum of 63). Note that the user may specify fewer than the maximum
  allowable frames in a 4K record to reduce latency

see SEED V2.4 Manual, chapter 8, page 124

A record not necessatily must be filled completely by time series data.
This also applies to records without blockette 1001. The reading program must
be prepared to skip unused bytes in the record. If it does not, it will fail
to find the next Fixed Section of Data Header (48 bytes) as defined on page
108 in chapter 8 of SEED V2.4 Manual.

This fix:
Make sure that the entire record is read before processing the next one.