User Tools
information_for_astronomers:user_guide:reduc_pointing
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
information_for_astronomers:user_guide:reduc_pointing [2015/12/07 14:33] akraus |
information_for_astronomers:user_guide:reduc_pointing [2016/11/03 17:00] ubach [Raw Data Processing] |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== Location of the Raw Data ===== | ===== Location of the Raw Data ===== | ||
| - | The raw data of the 100m Effelsberg telescope is stored in MBFITS-Format. In Effelsberg the files are located in the directory /daten/Raw which should be available on every **Observer-PC**. Older data can be found in /daten/Raw/Raw-YYYY-MM. Most programs listed here support the flag "fdir" to point the program to the directory where the MBFITS data can be found. Default is always /daten/Raw. | + | The raw data of the 100m Effelsberg telescope is stored in MBFITS-Format. In Effelsberg the files are located in the directory /daten/Raw which should be available on every **Observer-PC**. Older data can be found in /eff/data/Raw/Raw-YYYY-MM. /eff/data/Raw is available on every **Observer-PC** and in the network in Bonn as well. Most programs listed here support the flag "fdir" to point the program to the directory where the MBFITS data can be found. Default is always /daten/Raw. |
| - | Every 30 minutes the raw data is synced to Bonn. It is accessible in /effbg/effdata/. More details on the location of data can be found here under [[Data storage and archive]] | + | Every 30 minutes the raw data is synced to Bonn. It is accessible in /eff/data/. Old data is accessible in /hsm/effarchive More details on the location of data can be found here under [[Data storage and archive]] |
| + | Current **Observer-PCs** are observer4 (64-bit) and observer7 (32-bit). Observers should use their MPIfR account to login to those machines, observes without an MPIfR account can use the common **obs2** account. | ||
| ===== Inspecting scans by hand using the Toolbox ===== | ===== Inspecting scans by hand using the Toolbox ===== | ||
| Line 105: | Line 106: | ||
| [[information_for_astronomers:user_guide:pyobslog|Obslogger]]. | [[information_for_astronomers:user_guide:pyobslog|Obslogger]]. | ||
| + | Once you have found your observations in the Obslogger, the log can be saved in a text file that can be used as an input file for the further data reduction below. | ||
| + | ===== Reducing a number of scans at once ===== | ||
| + | Looking at single scan might be appropriate for checking the data during an observation, but for calibration or flux density monitoring a more automatic way is preferred. There is a collection of scripts and programs that can be used to perform all the tasks to obtain flux density calibrated data. The scripts are located in /opt/bin on the **Observer-PCs**. | ||
| - | ===Logbook.py=== | + | ==== Raw Data Processing ==== |
| - | Logbook.py lists by default the last 1000 scans. This might take some time, because Logbook.py is reading the original MBFITS data files to get the information. Using | + | The scripts and programs mostly use a file that contains all the scan numbers to be reduced. The scripts **dblog2scan.py** or **dblog2scan_wea.py** produce such lists from observing logs written Obslogger. |
| - | <code> | + | |
| - | Logbook.py 100 <fdir=directory> | + | |
| - | </code> | + | |
| - | it lists only the last 100 scans. The time range can be restricted by the option | + | |
| - | <code> | + | |
| - | Logbook.py 10000 tstart=YYYY-MM-DD tstop=YYYY-MM-DD | + | |
| - | </code> | + | |
| - | where "tstart" marks the more recent time (if not specified the print out starts today) and "tstop" specifies the stop time in the past. The 10000 is just chosen to be big enough to cover most time ranges. Logbook.py can be used only to produce logs from more recent data because it searches only in /daten/Raw. | + | |
| - | For example: | + | In dblog2scan.py one can optionally restrict the frequency by the receiver version and frequency in GHz, if the log contains entries at different frequencies. |
| - | <code> | + | |
| - | obs2@observer3:~$ Logbook.py tstart=2011-04-18 tstop=2011-04-18 | + | |
| - | # SCAN SUB OBJECT SCANTYPE FEBE PROJECT DATE_OBS MJD | + | |
| - | .... | + | |
| - | 2692 2 3C345 FOCUS P13mm-PBE 46-09 2011-04-18T01:45:17 55669.0731 | + | |
| - | 2691 4 3C345 POINT P13mm-PBE 46-09 2011-04-18T01:42:56 55669.0715 | + | |
| - | 2690 4 3C345 POINT P13mm-PBE 46-09 2011-04-18T01:40:05 55669.0695 | + | |
| - | 2689 2 3C345 FOCUS P13mm-PBE 46-09 2011-04-18T01:38:44 55669.0686 | + | |
| - | 2688 4 3C345 POINT P13mm-PBE 46-09 2011-04-18T01:36:22 55669.0669 | + | |
| - | 2687 2 W3MAIN ONOFF P13mm-FFTS 46-09 2011-04-18T01:26:08 55669.0598 | + | |
| - | 2686 4 3C286 POINT P13mm-PBE 46-09 2011-04-18T01:17:28 55669.0538 | + | |
| - | 2685 2 3C286 FOCUS P13mm-PBE 46-09 2011-04-18T01:16:08 55669.0529 | + | |
| - | 2684 4 3C286 POINT P13mm-PBE 46-09 2011-04-18T01:13:45 55669.0512 | + | |
| - | .... | + | |
| - | </code> | + | |
| - | ===log.py=== | + | |
| - | log.py is a small script that prints some more detailed information than Logbook.py. | ||
| <code> | <code> | ||
| - | Usage: log.py scan1 scan2 [fdir=<PATH>] | + | ubach@observer4:~$ dblog2scan_wea.py |
| - | Options: | + | Usage: dblog2scan.py log-file [receiver] [freq GHz] |
| - | fdir=<PATH>: if the data are not in /daten/Raw any more | + | |
| - | </code> | + | |
| - | + | ||
| - | It can be also used to produce a log from older data in the archival directories, /datan/Raw/Raw-YYYY-MM specifying "fdir". | + | |
| - | + | ||
| - | For example: | + | |
| - | <code> | + | |
| - | obs2@observer3:~$ log.py 2684 2692 | + | |
| - | # *** Date: 2011-04-18 Project-ID: 46-09 Observer-Operator: ALEX *** | + | |
| - | # ** Temp = 3.7 deg C Humid = 70.0 % Press = 984.6 hPa | + | |
| - | #Scan Sub Source UT LST FE-BE Mode Freq Type Sw-mode AZI ELV Col* NULE z-Lin | + | |
| - | 2684 4 3C286 01:13:45 15:23:59 P13mm-PBE CONTINUUM 24000.00 POINT TOTP 236.9 61.0 4.3 2.1 -7.8 | + | |
| - | 2685 2 3C286 01:16:08 15:26:36 P13mm-PBE CONTINUUM 24000.00 FOCUS TOTP 237.8 60.7 2.6 -1.9 -7.8 | + | |
| - | 2686 4 3C286 01:17:28 15:27:44 P13mm-PBE CONTINUUM 24000.00 POINT TOTP 238.2 60.5 2.6 -1.9 -7.3 | + | |
| - | 2687 2 W3MAIN 01:26:08 15:36:25 P13mm-FFTS SPECTROSCO 23407.18 ONOFF TOTP 369.2 23.5 -0.0 -0.5 -7.3 | + | |
| - | 2688 4 3C345 01:36:22 15:46:40 P13mm-PBE CONTINUUM 23407.18 POINT TOTP 131.9 75.4 -0.0 -0.5 -7.3 | + | |
| - | 2689 2 3C345 01:38:44 15:49:18 P13mm-PBE CONTINUUM 23407.18 FOCUS TOTP 133.4 75.7 1.2 7.7 -7.3 | + | |
| - | 2690 4 3C345 01:40:05 15:50:24 P13mm-PBE CONTINUUM 23407.18 POINT TOTP 134.2 75.8 1.2 7.7 -7.6 | + | |
| - | 2691 4 3C345 01:42:56 15:53:15 P13mm-PBE CONTINUUM 25056.25 POINT TOTP 136.0 76.1 0.4 6.1 -7.5 | + | |
| - | 2692 2 3C345 01:45:17 15:55:56 P13mm-PBE CONTINUUM 25056.25 FOCUS TOTP 137.7 76.4 -0.1 7.3 -7.5 | + | |
| + | Give a frontend designation (e.g. 28.1) and additional a frequency | ||
| </code> | </code> | ||
| - | ===== Reducing a number of scans at once ===== | + | **dblog2scan.py** will just produce the files scans (input file for weather.py and corr_point.py) and scanlist (to be attached to the reduce.par file), **dblog2scan_wea.py** will produce an additional weather.dat file with weather information for each scan. The weather file is useful for the opacity correction described below. |
| - | + | ||
| - | Looking at single scan might be appropriate for checking the data during an observation, but for calibration or flux density monitoring a more automatic way is preferred. There is a collection of scripts and programs that can be used to perform all the tasks to obtain flux density calibrated data. The scripts are located in /home/obs2/bin on the observer3-PC. | + | |
| - | + | ||
| - | ==== Raw Data Processing ==== | + | |
| - | + | ||
| - | The scripts and programs mostly use a file that contains all the scan numbers to be reduced. The scripts **log2scan.py** or **logbook2scan.py** produce such lists from observing logs written by log.py or Logbook.py, respectively. | + | |
| - | + | ||
| - | In log2scan.py one can optionally restrict the frequency if the log contains entries at different frequencies. | + | |
| - | <code> | + | |
| - | log2scan.py | + | |
| - | Usage: log2scan.py log-file [freq GHz] | + | |
| - | </code> | + | |
| ---- | ---- | ||
| + | \\ | ||
| The script **reduce.py** can be used to reduce a number of given scans using the toolbox with a list of options. Some example parameter files are stored in /home/obs2/flux_monit/reduce-par. E.g., reduc28.par for the 2.8cm SFK receiver. Calling just reduce.py prints out some help as well. | The script **reduce.py** can be used to reduce a number of given scans using the toolbox with a list of options. Some example parameter files are stored in /home/obs2/flux_monit/reduce-par. E.g., reduc28.par for the 2.8cm SFK receiver. Calling just reduce.py prints out some help as well. | ||
information_for_astronomers/user_guide/reduc_pointing.txt · Last modified: 2022/07/04 20:35 by twedel
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
