tilepy 2.7.5

Computation of the tiling scheduling of large localization uncertainty region event with multi-wavelength pointing telescopes.

Installation

We clone the repo, create an environment to work, activate the environment and install the package. You can use conda or mamba for this.

git clone [e-mail]:astro-transients/tilepy.git
cd tilepy
conda env create -n tilepyenv -f environment.yml
conda activate tilepyenv
python -m pip install .

Some users have encounter problems with the use of the mocpy package within conda. If this is your case follow these instructions:

- remove mocpy from the environment.yml
- create and activate the environment as described above
- run "pip install mocpy"

If you prefer to avoid conda and use a virtual environment with your favorite python version, use the following sequence:

python -m venv tilepy_venv
source tilepy_venv/bin/activate
pip3 install --upgrade pip
python -m pip install -r requirements.txt

Requirements of the installation:

• The current version of the package only runs with python>=3.9. Python 3.9 is recommended. Be careful as well with the versions of matplotlib and healpy, they should be the ones explicitly given in the requirements.yml, otherwise conflicts between them when plotting skymaps will arise.
• Note that by creating the env from the environment.yml, the libraries and versions needed will be installed automatically.
• Note that every time we made changes to the package, you should update the installation of the package doing pip install . in the folder where the setup.py is located. The changes will be only applied to the env in which you are working.
• The package relies on 'curl' to download the localisation map of the multi-messenger events.

In the case you are working in CC-Lyon, the easiest solution is to doccenv conda and then follow the instructions given above.

If you have any problem with the installation of the package, please drop an email to [e-mail] or join the discussion forum at https://forum.astro-colibri.science/c/instrumentation-and-tools/tilepy

Creation of a galaxy catalog

For using the 3D algorithm tilepy need to have access to a galaxy catalog. Currently, the only supported catalog is GLADE+. You'll find the download link on this webpage : https://glade.elte.hu. To prepare it for usage by tilepy we provide a the ConvertGalaxyCatalog.py script that converts the original catalog into a hdf5 file compatible with tilepy. The script is located in the tilepy/tools repository.

Example: use the script to keep only galaxies that are within 500 Mpc (recommended). It reads the downloaded GLADE+.txt file and creates the output file Gladeplus.h5 which is the one that should be used with tilepy. You'll be able to specify the path to that file in your tilepy configuration. The examples assume the Gladeplus.h5 to be located in the tilepy/dataset/ directory.

python ConvertGalaxyCatalog.py --input GLADE+.txt --output Gladeplus.h5 --max-luminosity-distance 500

Description

Package including functions to perform GW follow-up scheduling and simulations in IACTS. The package can be found in the folder tilepy, which contains the following folders:

• src/tilepy: Folder including the python package

  • tilepy.include: The main files were functions are placed. In the usual case, the manager script is ObservationScheduler.py. At the following level, we have TilingDetermination.py. And the base set of functions are in CampaignDefinition.py, Observatories.py, PointingPlotting.py, PointingTools.py and RankingObservationTimes.py.
  • tilepy.tools: Includes several scripts that have been used so far for different aims related to visualization and catalog cleaning
  • tilepy.scripts: Further support scripts

• github/workflows: a series of workflows are enabled and triggered via GitHub Actions.

• docs: files to create a documentation [dev ongoing]

• examples: Examples on how to use tilepy, see dedicated README

  • launcher: Jupyter notebooks and .py scripts to run observation schedules for various use-cases. We recommend to use the Jupyter notebooks as these are more comprehensive, specially with the inputs given.
  • paperplots: Precise plots of ApJS Series, Volume 274 Number 1 (11pp), 2024 September
  • sciencecases: Support material and extra plots connected to those of the paper ApJS Series, Volume 274 Number 1 (11pp), 2024 September
  • visualization: Several notebooks to improve the visualization of observation campaigns
  • config: various examples of configuration files, used in the notebooks to run the scripts. The format is the following:

    • [observatory]

      • name: name of the observatory (it is not critical, you can use any name)
      • lat: lat coordinates of the observatory
      • lon: lon coordinates of the observatory
      • height: height of the observatory

    • [visibility]

      • sunDown: altitude of the Sun in deg to define darkness conditions (for astronomic darkness sunDown= -18)
      • moonDown: altitude of the Moon in deg to define darkness conditions (for astronomic darkness moonDown= -0.5)
      • moonGrey: altitude of the Moon in deg to define greyness conditions
      • moonPhase: phase of the Moon to define greyness conditions
      • minMoonSourceSeparation: minimum separation Source-Moon in deg to define greyness conditions
      • maxMoonSourceSeparation: max separation Source-Moon in deg to define greyness conditions

    • [operations]

      • maxZenith: max zenith angle which will be considered as accesible sky
      • FOV: radius of the circular FoV defining the tiles
      • maxRuns: maximum number of tiles that will be scheduled
      • maxNights: total number of nights considered
      • duration: standard exposure per tile
      • minDuration: minimal duration of tile if standard exposure is not available (e.g. at the end of the night)
      • useGreytime: flag to schedule greyness observations in addition to darkness

    • [tiling]

      • minimumProbCutforCatalogue: only galaxies that have probabilities higher than 'minimumProbCutforCatalogue x (GW x galaxy)_max' participate in the scheduling calculation
      • minProbcut: minimal probability covered per tile to schedule observation
      • distCut: distance cut to define the mandatory use of 2D strategy (coming from galaxy catalogue completeness)
      • doPlot: produce detailed plots of the scheduling
      • secondRound: consider two maps for scheduling
      • zenithWeighting: weight on probability that would be applied to prioritize coordinates that have lower zenith angle values. Step size is 5 deg in zenith (0.75 is a reasonable value)
      • percentageMOC: percentage of the sky localization region that will be considered to compute the MOC
      • reducedNside: nside of the low-resolution skymap used as a grid to speed up the computation
      • HRnside: nside of the high-resolution skymap used to compute the covered probability
      • mangrove: flag to use the mangrove method of weighting by the mass of the host galaxy
      • countPrevious: True if you want previous observation to be considered in number to set the max run variable. False else

Issue with Daily Earth Orientation Parameters Solutions file (finals2000A)

Astropy requires a recent reference file to compute correctly the coordinates. This file is in general downloaded automatically by Astropy but if you are offline, you will be able to run tilepy if you do the following fix in a global variable. First you need to download the file, it is available through several sources, IERS, OBSPM, NASA, USNO, .... For a fully offline installation, try to update the file every few month.

You need then to modify your script calling tilepy by adding the following lines before importing tilepy. Adapt the path to the file (here pathToYourReferencefile) in order that the system is able to find the file and loaded correctly.

import os
from astropy.utils import iers
iers_file = os.path.join(os.path.abspath(
    os.path.dirname(__file__)), pathToYourReferencefile)
iers.IERS.iers_table = iers.IERS_A.open(iers_file)

Help

If you find any problem, please open a new issue in the project main page to document it. You can of course also directly create a Pull Request with new features.

Otherwise you can also contact us at [e-mail] A user/developer discussion forum is available at https://forum.astro-colibri.science/c/instrumentation-and-tools/tilepy