-
Notifications
You must be signed in to change notification settings - Fork 0
2_How to
SimonaRighini edited this page Feb 11, 2018
·
6 revisions
Open a terminal. Launch IDL
$ IDL
Inside IDL, procedures are compiled as:
IDL> .r procname
And then launched as:
IDL> procname [, key=value, key2=’stringvalue’, /option]
Inside the command line, the various arguments must be comma—separated. If the procedure accepts input values, they are structured as key-value pairs. When the value to be passed is a string, it must be enclosed in ‘ ’. If options are available for a given procedure, they are enabled by using /
separate: | Used to reorganize the dataset in band-separated folders and, inside them, according to th nature of the source (flux calibrator, target, skydip) |
---|---|
opacity: | (Optional) Used when needing to estimate the tau0 values, which are needed to compensate the subsequent calibrators/targets measurements inside the pipeline |
dataflagging: | (Optional) Used to visually inspect and flag each single subscan in the dataset It exploits an interactive GUI |
runcalib: | Used in order to analyze the cross-scans acquired on flux density calibrators and to extract the counts-to-Jy factors to be then employed in the target data calibration. |
c2jtimeline: | Used in order to reconstruct a timeline (averaged values or linear interpolations) of the counts-to-Jy conversion factors |
runtarget: | Used in order to reduce and calibrate the cross-scans acquired on target sources |
srcaver: | (Optional) Used in order to reprocess runtarget’s output and average the different measurements on a target basis |