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
Next revisionBoth sides next revision
public:user_software:documentation:ndppp [2019-08-26 11:16] – Document split step Tammo Jan Dijkemapublic:user_software:documentation:ndppp [2019-10-02 09:00] – [Demixer] Tammo Jan Dijkema
Line 309: Line 309:
 | msin.nchan | integer | 0 | Number of channels to use from the input MS (0 means till the end). It can be an expression with `nchan` (nr of input channels) as parameter. E.g. \\ ''15*nchan/16'' | | msin.nchan | integer | 0 | Number of channels to use from the input MS (0 means till the end). It can be an expression with `nchan` (nr of input channels) as parameter. E.g. \\ ''15*nchan/16'' |
 | msin.starttime | string | first time in MS | Center of first time slot to use; if < first time in MS, dummy time slots are inserted. A date/time must be specified in the casacore MVTime format, e.g. 19Feb2010/14:01:23.817 | | msin.starttime | string | first time in MS | Center of first time slot to use; if < first time in MS, dummy time slots are inserted. A date/time must be specified in the casacore MVTime format, e.g. 19Feb2010/14:01:23.817 |
 +| msin.starttimeslots | int | 0 | Starting time slot. This can be negative to insert flagged time slots before the beginning of the MS. |
 | msin.endtime | string | last time in MS | Center of last time slot to use; if > last time in MS, dummy time slots are inserted. | | msin.endtime | string | last time in MS | Center of last time slot to use; if > last time in MS, dummy time slots are inserted. |
 | msin.ntimes | integer | 0 | Number of time slots to use (0 means till the end). | | msin.ntimes | integer | 0 | Number of time slots to use (0 means till the end). |
Line 382: Line 383:
 | <step>.type | string | | Case-insensitive step type; must be 'demixer' (or 'demix'). | | <step>.type | string | | Case-insensitive step type; must be 'demixer' (or 'demix'). |
 | <step>.baseline | string | "" | Baselines to demix. See [[#Description of baseline selection parameters]]. | | <step>.baseline | string | "" | Baselines to demix. See [[#Description of baseline selection parameters]]. |
-| <step>.blrange | double vector | "" | Baselines to demix. See [[#Description of baseline selection parameters]]. |+| <step>.blrange | double vector | [] | Baselines to demix. See [[#Description of baseline selection parameters]]. |
 | <step>.corrtype | string | cross | Baselines to demix. Correlation type to match? Must be auto, cross, or an empty string. | | <step>.corrtype | string | cross | Baselines to demix. Correlation type to match? Must be auto, cross, or an empty string. |
 | <step>.timestep | integer | 1 | Number of time slots to average when subtracting. It is truncated if exceeding the actual number of times. Note that the data itself will also be averaged by this amount. | | <step>.timestep | integer | 1 | Number of time slots to average when subtracting. It is truncated if exceeding the actual number of times. Note that the data itself will also be averaged by this amount. |
Line 559: Line 560:
 | <step>.statfilename | string | "" | File to write the step-sizes to. Form of the file is: "<iterationnr> <normalized-stepsize> <unnormalized-stepsize>", and all solution intervals are concatenated. File is not written when this parameter is empty. | | <step>.statfilename | string | "" | File to write the step-sizes to. Form of the file is: "<iterationnr> <normalized-stepsize> <unnormalized-stepsize>", and all solution intervals are concatenated. File is not written when this parameter is empty. |
 | <step>.uvlambdamin | double | 0 | Ignore baselines / channels with UV < uvlambdamin wavelengths. **Note**: also all other variants of uv flagging described in [[#UVWFlagger]] (uvmmin, uvmrange, uvlambdarange, etc) are supported (New in 3.1).| | <step>.uvlambdamin | double | 0 | Ignore baselines / channels with UV < uvlambdamin wavelengths. **Note**: also all other variants of uv flagging described in [[#UVWFlagger]] (uvmmin, uvmrange, uvlambdarange, etc) are supported (New in 3.1).|
-| <step>.subtract | bool | false | Subtracts the corrected model from the data.|+| <step>.subtract | bool | false | Subtracts the corrected model from the data. **NOTE** This may not work when you apply a uv-cut. |
 | <step>.useidg | bool | false | Do image-based prediction using IDG.| | <step>.useidg | bool | false | Do image-based prediction using IDG.|
 | <step>.idg.image | string | "" | Name of fits file for IDG prediction. Should have the phase direction of the measurement set. | | <step>.idg.image | string | "" | Name of fits file for IDG prediction. Should have the phase direction of the measurement set. |
  • Last modified: 2021-02-26 14:18
  • by Tammo Jan Dijkema