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 5 deletions
    Home.md
    View page @ aaad46e8
    ...@@ -15,6 +15,7 @@ PRISMA nodes are operated by an open-source software named [FreeTure](https://gi ...@@ -15,6 +15,7 @@ PRISMA nodes are operated by an open-source software named [FreeTure](https://gi
    The camera acquires a 30 fps video stream that is triggered in livetime by FreeTure looking for meteors in the field of view (FoV). The camera acquires a 30 fps video stream that is triggered in livetime by FreeTure looking for meteors in the field of view (FoV).
    PRISMA data are divided into two categories: **captures** (calibration data) and **events** (meteor data). PRISMA data are divided into two categories: **captures** (calibration data) and **events** (meteor data).
    The structure of these data is detailed in the [Workspace](Workspace) page.
    ## Events ## Events
    Once FreeTure triggers a meteor, a video of few hundred of frames is saved in FITS format. Once FreeTure triggers a meteor, a video of few hundred of frames is saved in FITS format.
    ...@@ -31,8 +32,6 @@ Inside the event, each detection is named by adding the station NAME before the ...@@ -31,8 +32,6 @@ 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) 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.
    Captures are calibration images which allow detecting stars down to +4/+5 mag (depending on the light pollution of the site). Captures are calibration images which allow detecting stars down to +4/+5 mag (depending on the light pollution of the site).
    ...@@ -42,5 +41,3 @@ This is a continuous dataflow from each station, and accounts in reality for mos ...@@ -42,5 +41,3 @@ 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)
    \ No newline at end of file
    The folder structure of captures is detailed in the [Workspace](Workspace) page.
    \ No newline at end of file