public:user_software:documentation:ndppp

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
public:user_software:documentation:ndppp [2020-05-28 18:52] André Offringapublic:user_software:documentation:ndppp [2021-02-26 14:18] (current) – [DPPP] Tammo Jan Dijkema
Line 1: Line 1:
 ===== DPPP ===== ===== DPPP =====
 +
 +==== Important ====
 +
 +A newer version of this documentation is available at https://www.astron.nl/citt/DP3
 +
 +==== Old documentation ====
 +
 DPPP (the Default Preprocessing Pipeline, previously NDPPP for New Preprocessing Pipeline) is the LOFAR data pipelined processing program. It can be used to do all kind of operations on the data in a pipelined way, so the data are read and written only once. DPPP (the Default Preprocessing Pipeline, previously NDPPP for New Preprocessing Pipeline) is the LOFAR data pipelined processing program. It can be used to do all kind of operations on the data in a pipelined way, so the data are read and written only once.
  
Line 611: Line 618:
  
 ==== SetBeam ==== ==== SetBeam ====
-SetBeam is an expert option and should only be used in rare cases. It allows direct manipulation of the beam-keywords for a column in a measurement set. Normally, DP3 registers whether the visibilities in a column are corrected for a beam or not, and if so, in what direction the beam was corrected for. This avoids incorrect corrections / scaling by the beam. However, certain actions can change the scaling of the visibilities without that the beam keywords are changed, in particular when predicting (either with DP3 or with another tool). When predicting a single source and not applying the beam, the visibilities are 'corrected' for the beam in the direction of the source. Under those circumstances, SetBeam can be used to modify the beam keywords. In that case, use direction for the source direction and beammode to default.+SetBeam is an expert option and should only be used in rare cases. It allows direct manipulation of the beam-keywords for a column in a measurement set. Normally, DP3 registers whether the visibilities in a column are corrected for a beam or not, and if so, in what direction the beam was corrected for. This avoids incorrect corrections / scaling by the beam. However, certain actions can change the scaling of the visibilities without that the beam keywords are changed, in particular when predicting (either with DP3 or with another tool). When predicting a single source and not applying the beam, the visibilities are 'corrected' for the beam in the direction of the source. Under those circumstances, SetBeam can be used to modify the beam keywords. In that case, set ''direction'' to the source direction and ''beammode'' to default.
 | <step>.type | string | | Case-insensitive step type; must be 'setbeam' | | <step>.type | string | | Case-insensitive step type; must be 'setbeam' |
 | <step>.direction | string vector | [] | A RA/Dec value specifying in what direction the beam is corrected. | | <step>.direction | string vector | [] | A RA/Dec value specifying in what direction the beam is corrected. |
  • Last modified: 2021-02-26 14:18
  • by Tammo Jan Dijkema