Free Access
Table 1.
AMPEL terminology.
| Term | AMPEL interpretation |
|---|---|
| Transient | Object with a unique ID provided from a data source and accepted into AMPEL by at least one channel |
| Datapoint | A single measurement with a specific calibration, processing level, etc. |
| Compound | A collection of datapoints (from one or more instruments) |
| State | A view of a transient object available at some point for some observer. Connects a compound with one (or more) transients |
| Tier | AMPEL is internally divided into four tiers, where each performs a different kind of operation and is controlled by a separate scheduler |
| Channel | Configuration of requested behavior at all AMPEL tiers supplied by a user (for one science goal). Typically consists of a list of requested units together with their run parameters |
| Archive | All alert data, and also those rejected during live processing, are stored in an archive for reprocessing |
| ScienceRecord | Records the result of a science computation made based on data available in specific state |
| TransientView | All information available regarding a specific transient. This can include multiple states, and any ScienceRecords associated with these |
| Unit | Typically implemented as python modules, a unit allows user-contributed code to be directly called during data processing. Units at different tiers receive different input and are expected to produce different kinds of output |
| Journal | A time-ordered log included in each transient |
| Purge | The transfer of a no-longer-active transient from the live database to external storage. This includes all connected datapoints, states, compounds, and ScienceRecords |
| Live instance | A version of AMPEL processing data in real-time. This includes a number of active channels |
| Reprocessing | Parsing archived alerts as they would have been received in real-time, using a set of channels defined as for a live instance |
Current usage metrics show cumulative count of Article Views (full-text article views including HTML views, PDF and ePub downloads, according to the available data) and Abstracts Views on Vision4Press platform.
Data correspond to usage on the plateform after 2015. The current usage metrics is available 48-96 hours after online publication and is updated daily on week days.
Initial download of the metrics may take a while.