... | ... | @@ -30,7 +30,7 @@ This directory should contain only IDL code, and nothing else. |
|
|
|
|
|
The folder structure needed for the execution of the PRISMA pipeline and detailed in the [Workspace](Workspace) page.
|
|
|
|
|
|
The complete workspace for the PRISMA pipeline is hosted in a separate repository named [PRISMA-workspace](https://www.ict.inaf.it/gitlab/dario.barghini/prisma-workspace), which is freely available to PRISMA collaborators only, since it hosts detailed information about the PRISMA stations, their location and configuration.
|
|
|
The complete workspace for the PRISMA pipeline is hosted in a separate repository named [PRISMA-workspace](https://www.ict.inaf.it/gitlab/dario.barghini/prisma-workspace), which is available to PRISMA collaborators only, since it hosts detailed information about the PRISMA stations, their location and configuration.
|
|
|
If you do not have access to it, the workspace is easily reproducible following the guidelines detailed in the [Workspace](Workspace) page.
|
|
|
|
|
|
If you have access to it, the PRISMA-workspace repository is linked to the pipeline via a git submodule in the `workspace` folder.
|
... | ... | @@ -40,15 +40,14 @@ Most of the directories contained in the workspace will be empty at the beginnin |
|
|
|
|
|
# Settings
|
|
|
|
|
|
After recreating the workspace, some machine-dependent modifications are needed for the PRISMA pipeline to be fully operative on your computer.
|
|
|
They are all enclosed in the [`configuration.ini`](https://www.ict.inaf.it/gitlab/dario.barghini/prisma-workspace/-/blob/main/settings/configuration.ini) file inside the settings directory of the workspace: `/your_path_to_the/workspace/settings/configuration.ini`.
|
|
|
After installing the code and recreating the workspace, some machine-dependent modifications are needed for the PRISMA pipeline to be fully operative on your computer.
|
|
|
Most of them are enclosed in the [`configuration.ini`](https://www.ict.inaf.it/gitlab/dario.barghini/prisma-workspace/-/blob/main/settings/configuration.ini) file inside `(your_path_to_the)/workspace/settings/`.
|
|
|
More details about this file are given in the [Settings](Settings) page.
|
|
|
The configuration file in the workspace is designed for execution on the PRISMA servers.
|
|
|
If you do not have access to the workspace, you can find a template [here](uploads/configuration_template.ini)
|
|
|
If you do not have access to the workspace, you can find a template [here](uploads/configuration_template.ini).
|
|
|
|
|
|
To make the pipeline working, you have to adjust a few fields in the configuration file.
|
|
|
To do so, open [`configuration.ini`] with a text editor and modify the following:
|
|
|
|
|
|
To do so, open it with a text editor and modify the following:
|
|
|
|
|
|
### Path
|
|
|
|
... | ... | @@ -64,15 +63,28 @@ This is done to allow, for example, the raw data (captures and events) to be on |
|
|
This is a API key used for the generation and download of static background maps needed for the triangulation map of events (see [triangulation.pro](triangulation.pro)).
|
|
|
The API service is provided by [Geoapify](https://www.geoapify.com/) and it is based on [OpenStreetMap](https://www.openstreetmap.org/) tiles.
|
|
|
|
|
|
Go to the [login page](https://myprojects.geoapify.com/login) of Geoapify and generate your own API key.
|
|
|
Go to the [login page of Geoapify](https://myprojects.geoapify.com/login) and generate your own API key.
|
|
|
This service is free up to a usage limit of 3000 credits / day.
|
|
|
The credit price for each map is: `CP = 1 + (# tiles)/4`.
|
|
|
An average of 12 tiles is needed for each PRISMA map.
|
|
|
Therefore you can generate ~750 maps / day.
|
|
|
|
|
|
## Camera configuration
|
|
|
|
|
|
To make the code acknowledge the *existence* of a station, a few steps are needed:
|
|
|
|
|
|
- add the station CODE (e.g., `ITPI01`) and NAME (e.g., `PINOTORINESE`) to the [`solutions.ini`](https://www.ict.inaf.it/gitlab/dario.barghini/prisma-workspace/-/blob/main/settings/solutions.ini) file inside `workspace/settings/`.
|
|
|
If you do not have access to the workspace, you can find a template [here](uploads/solutions_template.ini).
|
|
|
- create a folder named after the camera CODE inside `/workspace/settings/configuration/`.
|
|
|
This folder must contain an initialization file in the format of `CODE.ini`, with the station and camera specification (e.g., [`ITPI01.ini`](https://www.ict.inaf.it/gitlab/dario.barghini/prisma-workspace/-/blob/main/settings/configuration/ITPI01/ITPI01_20171010.ini)).
|
|
|
If you do not have access to the workspace, you can find a template here [](uploads/CODE_template.ini).
|
|
|
|
|
|
More details are given in the [Settings](Settings) page.
|
|
|
|
|
|
# Third-part libraries
|
|
|
|
|
|
The PRISMA pipeline makes use of many external third-part IDL libraries in its code, listed here:
|
|
|
|
|
|
- [The IDL Astronomy User's Library](https://idlastro.gsfc.nasa.gov/) ([GitHub](https://github.com/wlandsman/IDLAstro))
|
|
|
- [Markwardt IDL Library](https://cow.physics.wisc.edu/~craigm/idl/idl.html)
|
|
|
- [Coyote IDL Program Libraries](http://www.idlcoyote.com/documents/programs.php) ([GitHub](https://github.com/idl-coyote/coyote))
|
... | ... | @@ -91,7 +103,7 @@ To install these libraries, follow the download links provided in the list and p |
|
|
|
|
|
The PRISMA pipeline uses the [NRLMSIS 2.0](https://ccmc.gsfc.nasa.gov/models/NRLMSIS~2.0/) empirical model to define the state of the atmospheric (density and temperature) within the solution of the dynamic evolution of the meteoroid in the atmosphere (see the [dynamic_model.pro](dynamic_model.pro) page).
|
|
|
NRLMSIS 2.0 is a major, reformulated upgrade of the previous version, [NRLMSISE-00](https://ccmc.gsfc.nasa.gov/models/NRLMSIS~00/).
|
|
|
To run this part of the code, you should build your own executable and place it (and other relevant files needed for the execution) in the `atmosphere/nrlmsis2.0` directory in the workspace.
|
|
|
To run this part of the code, you should build your own executable and place it (and other relevant files needed for the execution) in the directory `/your_path_to_the/workspace/atmosphere/nrlmsis2.0`.
|
|
|
This executable has to be named `msis20_windows.exe` for a Microsoft Windows platform or `msis20_linux.exe` for a Linux platform (the version for MacOS is not yet implemented in the pipeline).
|
|
|
Refer to the [Atmosphere](Atmosphere) page for more details.
|
|
|
|
... | ... | |