User Tools

Site Tools


chara:pavo_analysis_manual

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
chara:pavo_analysis_manual [2018/11/29 14:49]
jones [processv2.pro]
chara:pavo_analysis_manual [2018/11/29 15:30] (current)
jones [l1_l2_gui.pro]
Line 79: Line 79:
 ==== l0_l1_gui.pro ==== ==== l0_l1_gui.pro ====
  
-This program takes the .pav files and performs an automated outlier rejection as well as enables the user to manually reject bad sections of data. This program can only be run if /individual is set when running processv2.pro (i.e. .pav files have been created), which should really be the default option. \\  \\ Walkthrough: \\ 1) generate a file which contains the path and names of your .pav files you want to analyse, one .pav file per line. Suppose in the following this file is called //list//, and an example .pav file is called //example0.pav.// \\ 2) start the GUI in IDL, click on the LOAD button and load the file //list//. The output files for all scans will be called //list_l0l1.res.// \\ 3) The program will start showing results for the first .pav file, with the top panel displaying UT time versus V2, and the bottom panel UT time versus S/N (calculated in real-time (RT), i.e. the number you see in the PAVO server during observing). In the top panel each wavelength is shown as a white dot, and white squares are the average V2 over all wavelengths. Green squares are frames which are kept with the current rejection criteria. A screenshot of this for good 1-bl data can be found [[:chara:file_view_l0l1_1bl.tiff_232655714_l0l1_1bl.tiff|here]]. \\+This program takes the .pav files and performs an automated outlier rejection as well as enables the user to manually reject bad sections of data. This program can only be run if /individual is set when running processv2.pro (i.e. .pav files have been created), which should really be the default option. \\  \\ Walkthrough: \\ 1) generate a file which contains the path and names of your .pav files you want to analyse, one .pav file per line. Suppose in the following this file is called //list//, and an example .pav file is called //example0.pav.// \\ 2) start the GUI in IDL, click on the LOAD button and load the file //list//. The output files for all scans will be called //list_l0l1.res.// \\ 3) The program will start showing results for the first .pav file, with the top panel displaying UT time versus V2, and the bottom panel UT time versus S/N (calculated in real-time (RT), i.e. the number you see in the PAVO server during observing). In the top panel each wavelength is shown as a white dot, and white squares are the average V2 over all wavelengths. Green squares are frames which are kept with the current rejection criteria. A screenshot of this for good 1-bl data can be found {{:chara:files:l0l1_1bl.jpg?linkonly|here}}. \\
 4) Outlier rejection is based on 3 criteria: S/N, seconds after lock on fringes is lost (NSEC) and deviation from mean in sigma (SIGMA LIMIT); The default values for this should be fine in most cases; S/N cuts are probably the most sensible to be adjusted if data is particularly bad/good. \\ 4) Outlier rejection is based on 3 criteria: S/N, seconds after lock on fringes is lost (NSEC) and deviation from mean in sigma (SIGMA LIMIT); The default values for this should be fine in most cases; S/N cuts are probably the most sensible to be adjusted if data is particularly bad/good. \\
-5) The bottom row shows a range of diagnostics that can be used to determine the quality of data such as group delays, cart positions, V2C/V2 (measure of t0, good if high) and histograms. An example for a histogram display for 3-bl data can be found [[:chara:file_view_l0l1_3bl.tiff_232655724_l0l1_3bl.tiff|here]]. The top right window will display the fraction of datapoints rejected with the current settings. \\+5) The bottom row shows a range of diagnostics that can be used to determine the quality of data such as group delays, cart positions, V2C/V2 (measure of t0, good if high) and histograms. An example for a histogram display for 3-bl data can be found {{:chara:files:l0l1_3bl.jpg?linkonly|here}}. The top right window will display the fraction of datapoints rejected with the current settings. \\
 6) Once you're satisfied with the rejection settings for the scan press OUTPUT FILE, which will show V2 vs lambda using all frames that survived the outlier rejection. This step will create and entry in the output file //list_l0l1.res//, as well as an individual file //example0.pav_UT??_UT??.dat//, depending on the UT range that goes into the scan. \\  \\ Note: If you are adjusting outlier rejection criteria, it is probably a good idea to use a set of best settings for all scans of a single night (rather than adjusting them star-by-star) in order to avoid bias in your calibration. Ideally you shouldn't have to adjust anything, and simply use the graphical inspection to decide which scans are useful for calibration and which are not. \\ Note2: OUTPUT FILE also create additional files called //example0.pav.ind//  and //example0.pav.cov.//  The contain the array indices of frames that are kept for each file, as well as the covariance matrix of each scan which are used in l1_l2_gui.pro 6) Once you're satisfied with the rejection settings for the scan press OUTPUT FILE, which will show V2 vs lambda using all frames that survived the outlier rejection. This step will create and entry in the output file //list_l0l1.res//, as well as an individual file //example0.pav_UT??_UT??.dat//, depending on the UT range that goes into the scan. \\  \\ Note: If you are adjusting outlier rejection criteria, it is probably a good idea to use a set of best settings for all scans of a single night (rather than adjusting them star-by-star) in order to avoid bias in your calibration. Ideally you shouldn't have to adjust anything, and simply use the graphical inspection to decide which scans are useful for calibration and which are not. \\ Note2: OUTPUT FILE also create additional files called //example0.pav.ind//  and //example0.pav.cov.//  The contain the array indices of frames that are kept for each file, as well as the covariance matrix of each scan which are used in l1_l2_gui.pro
  
Line 93: Line 93:
 ==== l1_l2_gui.pro ==== ==== l1_l2_gui.pro ====
  
-A GUI extension of l1_l2.pro to calibrate data, including multi-bracket calibration and proper uncertainty calculations using Monte-Carlo simulations. This program can only be run with the output of l0_l1_gui.pro (see above). \\  \\ Walkthrough: \\ 1) Load the output file generated by l0_l1_gui.pro. If you run the program for the first time it will search for coordinates using querysimbad to calculate projected baselines etc, which takes a few minutes. \\ 2) Load your estimated calibrator diameters using the CAL DIAMETERS button - see diamsfile keyword in l1_l2.pro above. The third column can be used to specify diameter uncertainties for the calibrators. ***This step is mandatory for sensible science calibration*** \\ 3) Using the TARGETS and CALS boxes in the second row you can calibrate individual scans of data, including averages of multiple scans (separated by a comma in the box). The scan numbers including information on elevation, azimuth, time between scans and expected diameter can be found in the top right box. This feature should be used to identify the brackets that you want to use for the final calibration, and to identify bad calibrators (e.g. by calibrating calibrators with each other). An example screenshot can be found [[:chara:file_view_l1l2_1.png_232661548_l1l2_1.png|here]]. \\+A GUI extension of l1_l2.pro to calibrate data, including multi-bracket calibration and proper uncertainty calculations using Monte-Carlo simulations. This program can only be run with the output of l0_l1_gui.pro (see above). \\  \\ Walkthrough: \\ 1) Load the output file generated by l0_l1_gui.pro. If you run the program for the first time it will search for coordinates using querysimbad to calculate projected baselines etc, which takes a few minutes. \\ 2) Load your estimated calibrator diameters using the CAL DIAMETERS button - see diamsfile keyword in l1_l2.pro above. The third column can be used to specify diameter uncertainties for the calibrators. ***This step is mandatory for sensible science calibration*** \\ 3) Using the TARGETS and CALS boxes in the second row you can calibrate individual scans of data, including averages of multiple scans (separated by a comma in the box). The scan numbers including information on elevation, azimuth, time between scans and expected diameter can be found in the top right box. This feature should be used to identify the brackets that you want to use for the final calibration, and to identify bad calibrators (e.g. by calibrating calibrators with each other). An example screenshot can be found {{:chara:files:l1l2_1.png?linkonly|here}}. \\
 4) Once you have identified the brackets that should be used for calibration, edit the l1l2.config file and specify the brackets by listing the .pav files as shown in the example (note that you need to give the full path to the .pav files if they are not in the same directory). The parameters in the top part of the file are relevant for the Monte-Carlo simulations used to estimate uncertainties. A mandatory parameter to edit here is the estimate for the limb-darkening coefficient of your star (set to 0 if you want a UD fit). \\ 4) Once you have identified the brackets that should be used for calibration, edit the l1l2.config file and specify the brackets by listing the .pav files as shown in the example (note that you need to give the full path to the .pav files if they are not in the same directory). The parameters in the top part of the file are relevant for the Monte-Carlo simulations used to estimate uncertainties. A mandatory parameter to edit here is the estimate for the limb-darkening coefficient of your star (set to 0 if you want a UD fit). \\
 5) Load your config file using the LOAD CONFIG FILE button and press CALIBRATE to perform the multi-bracket calibration. A LD/UD will be performed automatically. Press OUTPUT FILES to output the data of this graph. \\ 5) Load your config file using the LOAD CONFIG FILE button and press CALIBRATE to perform the multi-bracket calibration. A LD/UD will be performed automatically. Press OUTPUT FILES to output the data of this graph. \\
-6) Pressing RUN MC will start the Monte-Carlo simulations to calculate uncertainties of the UD fit to the data. The simulations include uncertainties in wavelength scale, calibrator diameters, measurement errors, limb-darkening coefficient and correlations between wavelength channels (see [[:chara:file_view_l1_l2.tiff_232656708_l1_l2.tiff|here]] for an example output screenshot). This feature is so far only implemented for a simple UD fit. \\+6) Pressing RUN MC will start the Monte-Carlo simulations to calculate uncertainties of the UD fit to the data. The simulations include uncertainties in wavelength scale, calibrator diameters, measurement errors, limb-darkening coefficient and correlations between wavelength channels (see {{:chara:files:l1_l2.jpg?linkonly|here}} for an example output screenshot). This feature is so far only implemented for a simple UD fit. \\
  \\  \\
 Note: /exp is default in this program as I've found it to improve the calibration in almost all cases. Note: /exp is default in this program as I've found it to improve the calibration in almost all cases.
chara/pavo_analysis_manual.1543520943.txt.gz ยท Last modified: 2018/11/29 14:49 by jones