[installation] Change to nightly

This commit is contained in:
2025-10-30 12:04:59 +01:00
parent 2ff097f9d1
commit a31bc45cce
1441 changed files with 60368 additions and 56360 deletions

View File

@ -13,11 +13,18 @@ Historically, the only time format native to |scname| would be
.. code-block:: properties
YYYY-MM-DD hh:mm:ss.ssssss
'%F %T.%f'
As a consequence of the space between *DD* and *hh* this time string needs
to be enclosed by quotes or double quotes. Otherwise, the time string meant to
be a single string only would be interpreted as two strings. Example:
like
.. code-block:: properties
'2025-01-01 00:00:00.000000'
As a consequence of the space character between *DD* and *HH* this time string
needs to be enclosed by quotes or double quotes. Otherwise, the time string
meant to be a single string only would be interpreted as two strings. Example
application:
.. code-block:: sh
@ -55,55 +62,43 @@ Currently unsupported are:
* Time zone offset designators,
* Local times.
.. csv-table:: List and examples of supported time string formats
:widths: 30 30 40
:header: Implementation, Time string format, Examples: all actual times are identical
.. csv-table:: Table: List and examples of supported time string formats
:widths: 40 60
:header: Implementation (+), Examples: all given times are identical
:align: left
:delim: ;
%FT%T.%fZ ; YYYY-MM-DDThh:mm:ss.ssssssZ ; 2025-01-01T00:00:00.000000Z
%FT%T.%f ; YYYY-MM-DDThh:mm:ss.ssssss ; 2025-01-01T00:00:00.000000
%FT%TZ ; YYYY-MM-DDThh:mm:ssZ ; 2025-01-01T00:00:00Z
%FT%T ; YYYY-MM-DDThh:mm:ss ; 2025-01-01T00:00:00
%FT%R ; YYYY-MM-DDThh:mm ; 2025-01-01T00:00
%FT%H ; YYYY-MM-DDThh ; 2025-01-01T00
%Y-%jT%T.%f ; YYYY-DDDThh:mm:ss.ssssss ; 2025-001T00:00:00.000000
%Y-%jT%T ; YYYY-DDDThh:mm:ss ; 2025-001T00:00:00
%Y-%jT%R ; YYYY-DDDThh:mm ; 2025-001T00:00
%Y-%jT%H ; YYYY-DDDThh ; 2025-001T00
%F %T.%f (*) ; YYYY-MM-DD hh:mm:ss.ssssss ; '2025-01-01 00:00:00.000000'
%F %T (*) ; YYYY-MM-DD hh:mm:ss ; '2025-01-01 00:00:00'
%F %R (*) ; YYYY-MM-DD hh:mm ; '2025-01-01 00:00'
%F %H (*) ; YYYY-MM-DD hh ; '2025-01-01 00'
%F ; YYYY-MM-DD ; 2025-01-01
%Y-%j ; YYYY-DDD ; 2025-001
%Y ; YYYY ; 2025
%FT%T.%fZ ; 2025-01-01T00:00:00.000000Z
%FT%T.%f ; 2025-01-01T00:00:00.000000
%FT%TZ ; 2025-01-01T00:00:00Z
%FT%T ; 2025-01-01T00:00:00
%FT%R ; 2025-01-01T00:00
%FT%H ; 2025-01-01T00
%Y-%jT%T.%f ; 2025-001T00:00:00.000000
%Y-%jT%T ; 2025-001T00:00:00
%Y-%jT%R ; 2025-001T00:00
%Y-%jT%H ; 2025-001T00
%F %T.%f (*) ; '2025-01-01 00:00:00.000000'
%F %T (*) ; '2025-01-01 00:00:00'
%F %R (*) ; '2025-01-01 00:00'
%F %H (*) ; '2025-01-01 00'
%F ; 2025-01-01
%Y-%j ; 2025-001
%Y ; 2025
(+): Compare the formats with those of the :program:`date` command:
:program:`man date`.
(*): Time strings with spaces must be enclosed by quotes or double quotes for
protecting the space.
protecting the space character.
.. csv-table:: List of format symbols used in table of time string formats
:widths: 10 90
:header: Symbol, Description
:align: left
:delim: ;
YYYY; 4-digit year
MM; 2-digit month starting with 01
DD; 1- or 2-digit day of the month starting with 01
DDD; 1-, 2- or 3-digit day of year starting with 001
hh; 1- or 2-digit hour of the day starting with 00
mm; 1- or 2-digit minute of the hour starting with 00
ss; 1- or 2-digit second of the minute starting with 00
ssssss; 1-6 digits decimal fraction of a second with 0
Z; Zone designator for the zero UTC offset
Durations can be formed from start and end dates and times combined by tilde(~).
Example:
Time spans can be formed from start and end dates and times combined by tilde
(~). Examples:
.. code-block:: sh
scart -dsEv -t 2024-01-01T12~2024-01-01T12:15:30.2Z
scart -dsEv -t '2024-01-01 12:00:00~2024-01-01 12:15:30.2'
.. _time-grammar:
@ -258,7 +253,7 @@ Functions
.. py:function:: tt(phase)
Calculates the travel-time of the given phase **w.r.t. relative origin
time, :py:envvar:`OT`**. The result is unset if the travel time cannot be
time**, :py:envvar:`OT`. The result is unset if the travel time cannot be
computed. The travel times are computed based on the travel-time interface
and model defined in :confval:`amplitudes.ttt.interface` and
:confval:`amplitudes.ttt.model`, respectively.
@ -276,9 +271,9 @@ Functions
sensor location of the associated pick must match the sensor
location of the target object.
:param acceptAll: Whether to accept all arrivals or only manually
revised arrivals. The default is 'true' if not
revised arrivals. The default is 'false' if not
given. Allowed is either 'true' or 'false'. If
'true' is given, then either the evaluation mode
'false' is given, then either the evaluation mode
of the origin or the evaluation mode of the pick
must be 'manual'.