Skip to content
Snippets Groups Projects

Changes

Page history
  • New page
  • Templates
    • Update Home authored by Dario Barghini's avatar Dario Barghini
    Show whitespace changes
    Inline Side-by-side
    Showing
    with 2 additions and 2 deletions
    Home.md
    View page @ 5a1f3033
    ...@@ -31,7 +31,7 @@ Inside the event, each detection is named by adding the station NAME before the ...@@ -31,7 +31,7 @@ Inside the event, each detection is named by adding the station NAME before the
    Be aware that the date reported in the detection name might slightly differ (± 5 s) from the event date. Be aware that the date reported in the detection name might slightly differ (± 5 s) from the event date.
    This is due to the fact that each station may trigger the same meteor from a different starting time, or nodes may be not perfectly synchronized in time. This is due to the fact that each station may trigger the same meteor from a different starting time, or nodes may be not perfectly synchronized in time.
    The folder structure of events is detailed in the [Workspace](Workspace) section. The folder structure of events is detailed in the [Workspace](Workspace) page.
    ## Captures ## Captures
    For calibration purposes (both astrometric and photometric) of each station, the 30 fps stream is paused each 10 minutes to acquire a long-exposure image (5 seconds) named **capture**, also saved as a FITS file by FreeTure. For calibration purposes (both astrometric and photometric) of each station, the 30 fps stream is paused each 10 minutes to acquire a long-exposure image (5 seconds) named **capture**, also saved as a FITS file by FreeTure.
    ...@@ -43,4 +43,4 @@ This is a continuous dataflow from each station, and accounts in reality for mos ...@@ -43,4 +43,4 @@ This is a continuous dataflow from each station, and accounts in reality for mos
    Each capture is named after the station code and the acquisition date-time, in the following convention: Each capture is named after the station code and the acquisition date-time, in the following convention:
    `CODE_YYYYMMDDTHHMMSS_UT-0.fit` (e.g., ITPI01_20180100T001054_UT-0.fit) `CODE_YYYYMMDDTHHMMSS_UT-0.fit` (e.g., ITPI01_20180100T001054_UT-0.fit)
    The folder structure of captures is detailed in the [Workspace](Workspace) section. The folder structure of captures is detailed in the [Workspace](Workspace) page.
    \ No newline at end of file \ No newline at end of file