In the package
All code PACMAN needs to run and templates for the pcf and fit_par files are stored here. The scripts here use other python code from
This directory contains auxiliary scripts for the stages. E.g.,
PACMAN/src/pacman/lib/plots.pycreates and saves plots.
This directory contains the throughput for the G102 and the G141 grisms. These files will be used in Stage 03 to create the reference spectrum.
The flats (for the G102 and G141 grisms) are used to find the locations of bad pixels.
This directory tells PACMAN which stellar models are available to download. PACMAN can download three different stellar models: Kurucz stellar models 1993, Castelli and Kurucz stellar models 2004 and Phoenix models by Allard and collaborators. These models will be used in Stage 03 to create the reference spectrum. More on this at the walkthrough of Stage 03 using GJ1214 data as an example.
These three files have to be copied over to the run directory where the analysis will be run from! You find more information about that in Before Running.
This python script runs PACMAN. If the user did not install PACMAN properly as explained in the installation walkthrough (not recommended) he or she might have to add a path to the sys.path.append pointing to the PACMAN directory:
The path in
sys.path.appendhas to be changed to the location of PACMAN on the user’s device.
The path should point to
/PACMAN/and not to
The PACMAN control file (pcf): the user sets parameters related to the analysis. E.g., which plots should be saved, the path to the data directory and others. A thorough explanation of all the parameters in the pcf can be found on the PCF page.
The fit_par.txt file is used in Stage 30 to fit the light curve. The user defines here which fit parameters should be fixed, shared across visits, and sets other information like priors.
An example for a directory structure:
user └── Desktop └── Projects └── Observations └── Hubble └── GJ1214_13021 (="run directory") ├── pacman_script.py ├── fit_par.txt └── obs_par.pcf └── Data └── GJ1214_Hubble13021 (="data directory") ├── ibxy06d0q_ima.fits ├── ... └── ibxy07ryq_ima.fits
You have to copy the contents of run_files into this directory.
Contents to copy into the run directory:
If you pip-installed, downloaded or cloned the GitHub repository, you’ll find the run_files directory (with templates for these three files) in
PACMAN/src/pacman/data/run_files. They can also be downloaded under this link: Download here. You have to copy these files into your run directory.
NoteThe pcf file in the run directory is ONLY used in Stage 00.When running Stage 00, the pcf and fit_par files will be copied over to the work directory.The copied pcf file in the work directory will then be the pcf file for all following stages.The same is true for the fit_par.txt file.So, after running Stage 00, PACMAN does not care anymore about the changes made to the pcf file and the fit_par file in the run directory!
This directory will be created in Stage 00. All the results of the following stages will be stored here.
The name of the work directory is a combination of the following parts:
“run_” + “YYYY-MM-DD_HH-MM-SS_” + “eventlabel”
So for example: run_2022-03-04_15-10-29_GJ1214_Hubble13021
The eventlabel is chosen by the user when running Stage 00.
This directory should contain the .fits files which will be reduced and analyzed.
This is the heart of PACMAN containing all the code and data to run the different stages.