public:user_software:prefactor

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Last revisionBoth sides next revision
public:user_software:prefactor [2019-02-25 09:12] – [Overview] David Raffertypublic:user_software:prefactor [2019-02-25 09:15] – [To do list] David Rafferty
Line 19: Line 19:
 ==== Software requirements ==== ==== Software requirements ====
  
-  * the full "offline" LOFAR software installation version >= 2.15 \\ (With small modifications the Pre-Facet-Cal pipelines can be run with older versions, but that is not supported by the authors anymore.)+  * the full "offline" LOFAR software installation
   * LoSoTo   * LoSoTo
   * LSMTool (see https://github.com/darafferty/LSMTool)   * LSMTool (see https://github.com/darafferty/LSMTool)
-  * Python-PP (see http://www.parallelpython.com/ or https://pypi.python.org/pypi/pp ) 
   * Python matplotlib   * Python matplotlib
-  * WSClean (for Initial-Subtract, version >=1.9)+  * WSClean (for Initial-Subtract)
   * Aplpy (see https://aplpy.github.io)   * Aplpy (see https://aplpy.github.io)
 +  * See the prefactor GitHub page for more information
 ==== Documentation ==== ==== Documentation ====
  
-Installation and setup is explained in the preliminary version of a cookbook chapter at: https://github.com/lofar-astron/prefactor/blob/pdf-doc/docs/cookbook_prefacet.pdf \\ +Installation and setup is explained at the GitHub page: https://github.com/lofar-astron/prefactor \\ 
 **Please read that first!** **Please read that first!**
  
Line 40: Line 40:
     * Calibrator and target data are typically processed separately.     * Calibrator and target data are typically processed separately.
     * The target data can be processed one time- or frequency- block at a time, e.g. when you have limited disk space. (The processed data is a lot smaller than the input data.)     * The target data can be processed one time- or frequency- block at a time, e.g. when you have limited disk space. (The processed data is a lot smaller than the input data.)
-  * Yes, updating the LOFAR software can be annoying. But it is worth ist! Trust me. 8-) 
-  * Get someone to write a better documentation for the genericpipeline. 
   * Don't forget to update the recipe_directories entry in the pipeline.cfg to include the pre-factor plugins, for example: <code> recipe_directories = [%(pythonpath)s/lofarpipe/recipes,/home/rvweeren/software/prefactor]  </code>   * Don't forget to update the recipe_directories entry in the pipeline.cfg to include the pre-factor plugins, for example: <code> recipe_directories = [%(pythonpath)s/lofarpipe/recipes,/home/rvweeren/software/prefactor]  </code>
  
Line 99: Line 97:
 https://github.com/lofar-astron/prefactor/issues https://github.com/lofar-astron/prefactor/issues
  
-== FACTOR == 
- 
- 
-  * Time correlation settings given by user. 
-  * Aplpy plots (Tammo has script on his github but change noise to 1mJy (current 5mJy)) 
-  * All WSclean (any aliasing issues?) 
-  * pybdsm boxes from restoring beam size. 
-  * outer uvrange option (maybe good for help create models for selfcalbration when working at full resolution) 
-  * Check that amplitudes are properly normalised 
-  * Second major iteration 
-  * High dynamic range option 
-  * optimize number of IO-intesive (NDPPP) processes 
  • Last modified: 2019-02-25 09:16
  • by David Rafferty