This shows you the differences between two versions of the page.
Both sides previous 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-24 08:29] – [H5ParmPredict] Tammo Jan Dijkema |
---|
| <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'') | |