Skip to content

Commit

Permalink
Added explanation on usage of enrico on the fly.
Browse files Browse the repository at this point in the history
  • Loading branch information
jlenain committed Apr 7, 2016
1 parent d127a27 commit 9bcf358
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,8 @@ Help can be found on the two individual scripts, by typing:
./processAllSources.py -h
```

The pipeline uses an allsky file as input, which could easily be created using [`enrico`](http://enrico.readthedocs.org/en/latest/index.html). You'll also need the `make3FGLxml.py` script available at http://fermi.gsfc.nasa.gov/ssc/data/analysis/user/.
The pipeline uses an allsky file as input, which could easily be created using [`enrico`](http://enrico.readthedocs.org/en/latest/index.html). `FLaapLUC` is actually using `enrico` and can use it to generate an allsky file on the fly for you.

You'll also need the `make3FGLxml.py` script available at http://fermi.gsfc.nasa.gov/ssc/data/analysis/user/.

`FLaapLUC` depends on the *Fermi* Science Tools, and it is assumed that you have a local installation of this software on your machine (for more details, see http://fermi.gsfc.nasa.gov/ssc/data/analysis/software/). In more details, the two Python scripts 'automaticLightCurve.py' and 'processAllSources.py' should be able to find the `gt_apps` Python modules provided in the *Fermi* Science Tools (be careful to have your shell variable `$PYTHONPATH` up-to-date !).

0 comments on commit 9bcf358

Please sign in to comment.