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-05-06 08:40] – [DDECal] André Offringapublic:user_software:documentation:ndppp [2019-08-29 09:01] – [Input] 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 565: Line 566:
 | <step>.savefacets | bool | false | Write out each facet as a fits file (named facet<N>.fits). Only useful when useidg=true. | | <step>.savefacets | bool | false | Write out each facet as a fits file (named facet<N>.fits). Only useful when useidg=true. |
 | <step>.onlypredict | bool | false | Instead of solving, output the predicted visibilities instead. This is useful for testing, although when doing faceted prediction with IDG, it might be fast for certain cases. | | <step>.onlypredict | bool | false | Instead of solving, output the predicted visibilities instead. This is useful for testing, although when doing faceted prediction with IDG, it might be fast for certain cases. |
 +| <step>.applycal.*| | | ApplyCal sub-step, same as in Predict step. One can pass an h5parm with as many directions as set in "directions" and each direction model is corrupted accordingly. |
  
 ==== Predict ==== ==== Predict ====
Line 600: Line 602:
  
 ==== UVWFlagger ==== ==== UVWFlagger ====
-| <step>.type | string | | Case-insensitive step type; must be 'uvwflagger' or 'uvwflag'. | + 
-| <step>.count.save | bool | false | If true, the flag percentages per frequency are saved to a table with extension ''.flagfreq'' and percentages per station to a table with extension ''.flagstat''. The basename of the table is the MS name (without extension) followed by the stepname and extension. | +|<step>.type|string| |Case-insensitive step type; must be 'uvwflagger' or 'uvwflag'.| 
-| <step>.count.path | string | "" | The directory where to create the flag percentages table. If empty, the path of the input MS is used. | +|<step>.count.save|bool|false|If true, the flag percentages per frequency are saved to a table with extension ''.flagfreq'' and percentages per station to a table with extension ''.flagstat''. The basename of the table is the MS name (without extension) followed by the stepname and extension.| 
-| <step>.uvmrange | string vector | [] | Flag baselines with UV within one the given ranges (in meters). Delimiters .. and +- can be used to specify a range. E.g., ''uvmrange = [20..30, 40+-5]'' flags baselines with UV in range 20-30 meter and 35-45 meter. | +|<step>.count.path|string|""|The directory where to create the flag percentages table. If empty, the path of the input MS is used.| 
-| <step>.uvmmin | double | 0 | Flag baselines with UV < uvmmin meter. | +|<step>.uvmrange|string vector|[]|Flag baselines with UV within one the given ranges (in meters). Delimiters .. and +- can be used to specify a range. E.g., ''uvmrange = [20..30, 40+-5]'' flags baselines with UV in range 20-30 meter and 35-45 meter.| 
-| <step>.uvmmax | double | 1e15 | Flag baselines with UV > uvmmax meter. | +|<step>.uvmmin|double|0|Flag baselines with UV < uvmmin meter.| 
-| <step>.umrange | string vector | [] | Flag baselines with U within one of the given ranges (in meters). | +|<step>.uvmmax|double|1e15|Flag baselines with UV > uvmmax meter.| 
-| <step>.ummin | double | 0 | Flag baselines with U < ummin meter. | +|<step>.umrange|string vector|[]|Flag baselines with U within one of the given ranges (in meters).| 
-| <step>.ummax | double | 1e15 | Flag baselines with U > ummax meter. | +|<step>.ummin|double|0|Flag baselines with U < ummin meter.| 
-| <step>.vmrange | string vector | [] | Flag baselines with V within one of the given ranges (in meters). | +|<step>.ummax|double|1e15|Flag baselines with U > ummax meter.| 
-| <step>.vmmin | double | 0 | Flag baselines with V < vmmin meter. | +|<step>.vmrange|string vector|[]|Flag baselines with V within one of the given ranges (in meters).| 
-| <step>.vmmax | double | 1e15 | Flag baselines with V > vmmax meter. | +|<step>.vmmin|double|0|Flag baselines with V < vmmin meter.| 
-| <step>.wmrange | string vector | [] | Flag baselines with W within one of the given ranges (in meters). | +|<step>.vmmax|double|1e15|Flag baselines with V > vmmax meter.| 
-| <step>.wmmin | double | 0 | Flag baselines with W < wmmin meter. | +|<step>.wmrange|string vector|[]|Flag baselines with W within one of the given ranges (in meters).| 
-| <step>.wmmax | double | 1e15 | Flag baselines with W > wmmax meter. | +|<step>.wmmin|double|0|Flag baselines with W < wmmin meter.| 
-| <step>.uvlambdarange | string vector | [] | Flag baselines/channels with UV within one the given ranges (in wavelengths). Delimiters .. and +- can be used to specify a range. E.g., ''uvlambdarange = [20..30, 40+-5]'' flags baselines/channels with UV in range 20-30 wavelengths and 35-45 wavelengths. | +|<step>.wmmax|double|1e15|Flag baselines with W > wmmax meter.| 
-| <step>.uvlambdamin | double | 0 | Flag baselines/channels with UV < uvlambdamin wavelengths | +|<step>.uvlambdarange|string vector|[]|Flag baselines/channels with UV within one the given ranges (in wavelengths). Delimiters .. and +- can be used to specify a range. E.g., ''uvlambdarange = [20..30, 40+-5]'' flags baselines/channels with UV in range 20-30 wavelengths and 35-45 wavelengths.| 
-| <step>.uvlambdamax | double | 1e15 | Flag baselines/channels with UV > uvlambdamax wavelengths | +|<step>.uvlambdamin|double|0|Flag baselines/channels with UV < uvlambdamin wavelengths| 
-| <step>.ulambdarange | string vector | [] | Flag baselines/channels with U within one the given ranges (in wavelengths). | +|<step>.uvlambdamax|double|1e15|Flag baselines/channels with UV > uvlambdamax wavelengths| 
-| <step>.ulambdamin | double | 0 | Flag baselines/channels with U < ulambdamin wavelengths | +|<step>.ulambdarange|string vector|[]|Flag baselines/channels with U within one the given ranges (in wavelengths).| 
-| <step>.ulambdamax | double | 1e15 | Flag baselines/channels with U > ulambdamax wavelengths | +|<step>.ulambdamin|double|0|Flag baselines/channels with U < ulambdamin wavelengths| 
-| <step>.vlambdarange | string vector | [] | Flag baselines/channels with V within one the given ranges (in wavelengths). | +|<step>.ulambdamax|double|1e15|Flag baselines/channels with U > ulambdamax wavelengths| 
-| <step>.vlambdamin | double | 0 | Flag baselines/channels with V < vlambdamin wavelengths | +|<step>.vlambdarange|string vector|[]|Flag baselines/channels with V within one the given ranges (in wavelengths).| 
-| <step>.vlambdamax | double | 1e15 | Flag baselines/channels with V > vlambdamax wavelengths | +|<step>.vlambdamin|double|0|Flag baselines/channels with V < vlambdamin wavelengths| 
-| <step>.wlambdarange | string vector | [] | Flag baselines/channels with W within one the given ranges (in wavelengths). | +|<step>.vlambdamax|double|1e15|Flag baselines/channels with V > vlambdamax wavelengths| 
-| <step>.wlambdamin | double | 0 | Flag baselines/channels with W < wlambdamin wavelengths | +|<step>.wlambdarange|string vector|[]|Flag baselines/channels with W within one the given ranges (in wavelengths).| 
-| <step>.wlambdamax | double | 1e15 | Flag baselines/channels with W > wlambdamax wavelengths | +|<step>.wlambdamin|double|0|Flag baselines/channels with W < wlambdamin wavelengths| 
-| <step>.phasecenter | string vector | [] | If given, use this phase center to calculate the UVW coordinates to flag on. The vector can consist of 1, 2 or, 3 values. If one value is given, it must be the name of a moving source (e.g. SUN or JUPITER). Otherwise the first two values must contain a source position that can be given in sexagesimal format or as a value followed by a unit. The third value can contain the direction type; it defaults to J2000. Possible types are GALACTIC, ECLIPTIC, SUPERGAL, J2000, B1950 (as defined in the casacore ''Measures'' system). |+|<step>.wlambdamax|double|1e15|Flag baselines/channels with W > wlambdamax wavelengths| 
 +|<step>.phasecenter|string vector|[]|If given, use this phase center to calculate the UVW coordinates to flag on. The vector can consist of 1, 2 or, 3 values. If one value is given, it must be the name of a moving source (e.g. SUN or JUPITER). Otherwise the first two values must contain a source position that can be given in sexagesimal format or as a value followed by a unit. The third value can contain the direction type; it defaults to J2000. Possible types are GALACTIC, ECLIPTIC, SUPERGAL, J2000, B1950 (as defined in the casacore ''Measures'' system).| 
 + 
 +==== Split ==== 
 + 
 +|<step>.type|string| |Case-insensitive step type; must be 'split' or 'explode'
 +|<step>.steps|string vector|[]|List of next steps; each step will run after this step. E.g. ''[average, msout]''
 +|<step>.replaceparms|string vector|[]|The substep keys that should be different for each of the next steps. Instead of their default type, they should now be a list of those things. E.g. ''[average.timestep, msout.name]''
 + 
 +\\ 
  
 ==== Interpolate ==== ==== Interpolate ====
  • Last modified: 2021-02-26 14:18
  • by Tammo Jan Dijkema