User Tools
hardware:phasecal
This wiki is not maintained! Do not use this when setting up AuScope experiments!
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
hardware:phasecal [2019/05/28 07:46] Guifre [Data processing] |
hardware:phasecal [2019/11/26 00:29] (current) Guifre [Data recorded in Flexbuff Hb] |
||
|---|---|---|---|
| Line 18: | Line 18: | ||
| </note>\\ | </note>\\ | ||
| - | ====== Data recorded in Flexbuff Hb ====== | ||
| - | |||
| - | mkdir /mnt/vbsPcal/ \\ | ||
| - | vbs_fs -n 4 -I *pcal_*2205 /mnt/vbsPcal/ \\ | ||
| - | ls -l /mnt/vbsPcal/ \\ | ||
| - | |||
| - | -rw-r--r-- 0 observer observer 15G May 22 16:13 pcal_off_2205_Hb_No0001_46227 \\ | ||
| - | -rw-r--r-- 0 observer observer 15G May 22 16:13 pcal_off_2205_Hb_No0001_46228 \\ | ||
| - | -rw-r--r-- 0 observer observer 15G May 22 16:13 pcal_off_2205_Hb_No0001_46229 \\ | ||
| - | -rw-r--r-- 0 observer observer 15G May 22 16:13 pcal_off_2205_Hb_No0001_46230 \\ | ||
| - | -rw-r--r-- 0 observer observer 15G May 22 16:13 pcal_off_2205_Hb_No0001_46233 \\ | ||
| - | -rw-r--r-- 0 observer observer 15G May 22 16:13 pcal_off_2205_Hb_No0001_46234 \\ | ||
| - | -rw-r--r-- 0 observer observer 137G May 22 16:10 pcal_on_2205_Hb_No0001_46227 \\ | ||
| - | -rw-r--r-- 0 observer observer 137G May 22 16:10 pcal_on_2205_Hb_No0001_46228 \\ | ||
| - | -rw-r--r-- 0 observer observer 137G May 22 16:10 pcal_on_2205_Hb_No0001_46229 \\ | ||
| - | -rw-r--r-- 0 observer observer 137G May 22 16:10 pcal_on_2205_Hb_No0001_46230 \\ | ||
| - | -rw-r--r-- 0 observer observer 137G May 22 16:10 pcal_on_2205_Hb_No0001_46233 \\ | ||
| - | -rw-r--r-- 0 observer observer 137G May 22 16:10 pcal_on_2205_Hb_No0001_46234 \\ | ||
| ====== Data processing ====== | ====== Data processing ====== | ||
| - | First need to change PythonPath every-time you open a new terminal, otherwise is using DifX defaults one: \\ | + | First need to change PythonPath every-time you open a new terminal, otherwise is using DifX defaults one: |
| - | <WRAP center round tip 60%> | + | export PYTHONPATH=/usr/lib/python3.4 |
| - | export PYTHONPATH=/usr/lib/python3.4 \\ | + | cd /home/observer/PcalTests |
| - | cd /home/observer/PcalTests \\ | + | |
| - | </WRAP> | + | |
| - | I recommend using the program call screen in order to have the processing in the background. A short description on how to use screen is below: \\ | + | I recommend using the program call screen in order to have the processing in the background. A short description on how to use screen is below: |
| - | <WRAP center round tip 60%> \\ | + | observer@flexbuffhb DiFX-2.5.2 ~> screen YourName - You can recognise the screen later |
| - | observer@flexbuffhb DiFX-2.5.2 ~> screen YourName - You can recognise the screen later \\ | + | observer@flexbuffhb DiFX-2.5.2 ~> screen -raAD |
| - | observer@flexbuffhb DiFX-2.5.2 ~> screen -raAD \\ | + | |
| - | There are several suitable screens on: \\ | + | |
| - | 14835.pts-4.flexbuffhb (28/05/19 17:39:31) (Detached) \\ | + | |
| - | 18325.pts-4.flexbuffhb (14/05/19 13:53:38) (Detached) \\ | + | |
| - | Type "screen [-d] -r [pid.]tty.host" to resume one of them. \\ | + | |
| - | observer@flexbuffhb DiFX-2.5.2 ~> screen -raAD 18325 - Check if that is the screen you were using last!! \\ | + | |
| - | Commands to use inside a screen: \\ | + | There are several suitable screens on: |
| - | ctrl+a c - creates \\ | + | 14835.pts-4.flexbuffhb (28/05/19 17:39:31) (Detached) |
| - | ctrl+a p - previous \\ | + | 18325.pts-4.flexbuffhb (14/05/19 13:53:38) (Detached) |
| - | ctrl+a n - next \\ | + | Type "screen [-d] -r [pid.]tty.host" to resume one of them. |
| - | ctrl+a d - leaves the current screen\\ | + | observer@flexbuffhb DiFX-2.5.2 ~> screen -raAD 18325 - Check if that is the screen you were using last!! |
| - | </WRAP> | + | |
| + | Commands to use inside a screen: | ||
| + | ctrl+a c - creates | ||
| + | ctrl+a p - previous | ||
| + | ctrl+a n - next | ||
| + | ctrl+a d - leaves the current screen | ||
| You should find most of the necessary files inside of the folder \\ | You should find most of the necessary files inside of the folder \\ | ||
| Line 86: | Line 65: | ||
| We run the program by executing this program. If we process the 8 channels per each of the 6 files (6 IFs), You should end up with 48 spectra data files. \\ | We run the program by executing this program. If we process the 8 channels per each of the 6 files (6 IFs), You should end up with 48 spectra data files. \\ | ||
| - | <note important>swspectrometer inifile.ini /mnt/vbsPcal/pcal_on_2205_Hb_No0001_46227</note> | + | swspectrometer inifile.ini /mnt/vbsPcal/pcal_on_2205_Hb_No0001_46227 |
| 2. Check the quality of the spectrum. I have written several Python scripts to provide a quick validation of the recorded data. \\ | 2. Check the quality of the spectrum. I have written several Python scripts to provide a quick validation of the recorded data. \\ | ||
| + | <WRAP center round important 60%> | ||
| // -bw sets the bandwidth \\ | // -bw sets the bandwidth \\ | ||
| // -f0 sets the minimum frequency to search for the peak \\ | // -f0 sets the minimum frequency to search for the peak \\ | ||
| // -f1 sets the maximum frequency to search for the peak \\ | // -f1 sets the maximum frequency to search for the peak \\ | ||
| // -p plots the output - don't put anything if you don't need \\ | // -p plots the output - don't put anything if you don't need \\ | ||
| + | </WRAP> | ||
| + | |||
| + | python3 checkSpectra.py p190522_Hb_VDIF_If000A_320000pt_5s_ch1_swspec.bin -bw 32e6 -f0 4e6 -f1 6e6 -p | ||
| + | python3 calculatePcalCpp.py p190522_Hb_VDIF_If000A_320000pt_5s_ch1_swspec.bin -bw 32e6 -f0 4.9e6 -f1 5.1e6 | ||
| - | <note important> | ||
| - | python3 checkSpectra.py p190522_Hb_VDIF_If000A_320000pt_5s_ch1_swspec.bin -bw 32e6 -f0 4e6 -f1 6e6 -p \\ | ||
| - | python3 calculatePcalCpp.py p190522_Hb_VDIF_If000A_320000pt_5s_ch1_swspec.bin -bw 32e6 -f0 4.9e6 -f1 5.1e6 \\ | ||
| - | </note> | ||
| The calculatePcalCpp will provide a set of polynomials that will be used for the tracking software to study the Phase Cal tone. Example: \\ | The calculatePcalCpp will provide a set of polynomials that will be used for the tracking software to study the Phase Cal tone. Example: \\ | ||
| - | -rw-r--r-- 1 observer observer 75 May 23 12:07 p190522_Hb_VDIF_If000A_320000pt_5s_ch1.poly2.txt \\ | + | -rw-r--r-- 1 observer observer 75 May 23 12:07 p190522_Hb_VDIF_If000A_320000pt_5s_ch1.poly2.txt |
| - | -rw-r--r-- 1 observer observer 50 May 23 12:07 p190522_Hb_VDIF_If000A_320000pt_5s_ch1.X1cfs.txt \\ | + | -rw-r--r-- 1 observer observer 50 May 23 12:07 p190522_Hb_VDIF_If000A_320000pt_5s_ch1.X1cfs.txt |
| - | -rw-r--r-- 1 observer observer 34558 May 24 13:23 Fdets.cal2019.05.22.Hb.ifA.ch1.r0i.txt \\ | + | -rw-r--r-- 1 observer observer 34558 May 24 13:23 Fdets.cal2019.05.22.Hb.ifA.ch1.r0i.txt |
| 3. Configure and run sctracker \\ | 3. Configure and run sctracker \\ | ||
| Line 115: | Line 95: | ||
| # Output file name . . BaseFilename = p190519_Hb_VDIF_If000A_%fftpoints%pt_%integrtime%s_ch%channel% \\ | # Output file name . . BaseFilename = p190519_Hb_VDIF_If000A_%fftpoints%pt_%integrtime%s_ch%channel% \\ | ||
| - | Run the sctracker as: \\ | + | Run the sctracker as: |
| - | <note important>sctracker inifileHb \\</note> | + | sctracker inifileHb |
| Once sctracker has finished, which can take several hours, it produces several output files. The most important one is \\ | Once sctracker has finished, which can take several hours, it produces several output files. The most important one is \\ | ||
/home/www/auscope/opswiki/data/attic/hardware/phasecal.1559029563.txt.gz · Last modified: 2019/05/28 07:46 by Guifre
Page Tools
