| Both sides previous revision Previous revision Next revision | Previous revision Next revisionBoth sides next revision |
| public:user_software:documentation:ndppp [2019-10-24 08:28] – [H5ParmPredict] Tammo Jan Dijkema | public:user_software:documentation:ndppp [2019-10-30 10:30] – [Input] Tammo Jan Dijkema |
|---|
| | msin.datacolumn | string | DATA | Data column to use, i.e. the name of the column in which the visibilities are written. | | | msin.datacolumn | string | DATA | Data column to use, i.e. the name of the column in which the visibilities are written. | |
| | msin.weightcolumn | string | WEIGHT_SPECTRUM or WEIGHT | Weight column to use. Defaults to WEIGHT_SPECTRUM if this exists, otherwise the WEIGHT column is used. | | | msin.weightcolumn | string | WEIGHT_SPECTRUM or WEIGHT | Weight column to use. Defaults to WEIGHT_SPECTRUM if this exists, otherwise the WEIGHT column is used. | |
| | msin.modelcolumn | string | MODEL_DATA | Model data column. Currently only used in gaincal | | | msin.modelcolumn | string | MODEL_DATA | Model data column. Currently only used in gaincal and ddecal.| |
| | msin.autoweight | bool | false | Calculate weights using the auto-correlation data? It is meant for setting the proper weights for a raw LOFAR MeasurementSet. | | | msin.autoweight | bool | false | Calculate weights using the auto-correlation data? It is meant for setting the proper weights for a raw LOFAR MeasurementSet. | |
| | msin.forceautoweight | bool | false | In principle the calculation of the weights should only be done for the raw LOFAR data. It appeared that sometimes the ''autoweight'' switch was accidently set in a DPPP run on already dppp-ed data. To make it harder to make such mistakes, the ''forceautoweight'' flag has to be set as well for MSs containing dppp-ed data. | | | msin.forceautoweight | bool | false | In principle the calculation of the weights should only be done for the raw LOFAR data. It appeared that sometimes the ''autoweight'' switch was accidently set in a DPPP run on already dppp-ed data. To make it harder to make such mistakes, the ''forceautoweight'' flag has to be set as well for MSs containing dppp-ed data. | |
| | <step>.applycal.parmdb | string | | Path of the h5parm in which the corruptions are stored | | | <step>.applycal.parmdb | string | | Path of the h5parm in which the corruptions are stored | |
| | <step>.applycal.correction | string | | SolTab which contains the directions to be predicted, or "fulljones".| | | <step>.applycal.correction | string | | SolTab which contains the directions to be predicted, or "fulljones".| |
| | <step>.directions | string vector | [] | List of directions to include. Each of those directions needs to be in the h5parm soltab. If empty, all directions in the soltab are predicted. The names of the directions need to look like ''[dir1,dir2]'', where ''dir1'' and ''dir2'' are patches in the sourcedb. By default, the list of directions is taken from the H5Parm. The convention for naming directions in DDECal in H5Parm is ''[patch1,patch2]''.|| | | <step>.directions | string vector | [] | List of directions to include. Each of those directions needs to be in the h5parm soltab. If empty, all directions in the soltab are predicted. The names of the directions need to look like ''[dir1,dir2]'', where ''dir1'' and ''dir2'' are patches in the sourcedb. By default, the full list of directions is taken from the H5Parm. The convention for naming directions in DDECal in H5Parm is ''[patch1,patch2]''. This directions parameter can be used to predict / subtract a subset of the directions.|| |
| | <step>.usebeammodel | bool | false | Use the LOFAR beam in the predict part of the calibration | | | <step>.usebeammodel | bool | false | Use the LOFAR beam in the predict part of the calibration | |
| | <step>.operation | string | replace | Should the predicted visibilities replace those being processed (''replace'', default), should they be subtracted from those being processed (''subtract'') or added to them (''add'') | | | <step>.operation | string | replace | Should the predicted visibilities replace those being processed (''replace'', default), should they be subtracted from those being processed (''subtract'') or added to them (''add'') | |