If the nav header is being received, this will
try to detect the start and end of line and create
an entry in the log.
It doesn't check whether FSP/FGSP LSP/LGSP entries
already do exist for that sequence.
Closes # 28.
If a QC has failed in the past there will be a
record of it in raw_lines, raw_shots or preplot_points.
If that QC then stopped failing, e.g., because of a
change of parameters, then the QC results would correctly
reflect the change but not the line/shot tables and
hence, the event log.
This commit hopefully takes care of that.
The events endpoint will return data in the format
agreed with Multiseis if the request has an
Accept: application/vnd.seis+json
header.
Related to #12.
The reason for refactoring was to accommodate
Multiseis / client sequence exports, which will be
served by this endpoint via a specific Content-Type.
In the process, the cache has been fixed and redesigned.
Related to #12.
This is not really a substitute for proper database
design but if deemed useful it might be refactored
into a more generic caching middleware and applied
to other requests as a low-cost alternative to
database refactoring while we gain usage and
performance information.
This is to enable the user to associate information, in
particular “QCAccepted” override labels, to individual
results. The information stays associated with tests
unless the data is removed or the results change (e.g.,
because the data was reprocessed or the test parameters
or algorithm were changed).
Even though for practical reasons it's inside lib/www
this is meant to be run by bin/runner.sh at regular
intervals and refresh the QC data. This is a work
in progress. This version does not process or produce
labels, it doesn't create events in the event log and
it doesn't do online data, amongst other things.
This was brought about due to the absence of CRS information
in the navigation header outputs. We get either unqualified
easting / northing or unqualified latitude / longitude, neither
of which happen to be WGS84.
This is not a good solution as it involves manual configuration,
but allows us to move forward for the time being.
