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 | ||
hardware:phasecal [2019/05/23 02:42] Guifre [WHAT TO DO??] |
hardware:phasecal [2019/05/28 07:46] Guifre [Data processing] |
||
---|---|---|---|
Line 39: | Line 39: | ||
====== 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 \\ | ||
+ | </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: \\ | ||
+ | |||
+ | <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 -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: \\ | ||
+ | ctrl+a c - creates \\ | ||
+ | ctrl+a p - previous \\ | ||
+ | ctrl+a n - next \\ | ||
+ | ctrl+a d - leaves the current screen\\ | ||
+ | </WRAP> | ||
+ | |||
+ | You should find most of the necessary files inside of the folder \\ | ||
The processing takes 3 steps: \\ | The processing takes 3 steps: \\ | ||
Line 54: | Line 77: | ||
<WRAP center round important 60%> | <WRAP center round important 60%> | ||
- | UseFile1Channel = 1 # Change this value from 1 to 8, one per channel \\ | + | UseFile1Channel = 1 \\ |
- | BaseFilename1 = p190522_Hb_VDIF_If000A_%fftpoints%pt_%integrtime%s_ch%channel% # Modify IF000A to A/B/C/D/E/F to cover all the boards. \\ | + | BaseFilename1 = p190522_Hb_VDIF_If000A_%fftpoints%pt_%integrtime%s_ch%channel%\\ |
+ | Notes: \\ | ||
+ | # Change then channel value from 1 to 8, one per channel \\ | ||
+ | # Change IF000A to A/B/C/D/E/F to cover all boards \\ | ||
</WRAP> | </WRAP> | ||
- | 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> | ||
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. \\ | ||
+ | |||
// -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 \\ | ||
Line 66: | Line 95: | ||
// -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 \\ | ||
- | - python3 checkSpectra.py p190522_Hb_VDIF_If000A_320000pt_5s_ch1_swspec.bin -bw 32e6 -f0 4e6 -f1 6e6 -p \\ | + | <note important> |
- | - python3 calculatePcalCpp.py p190522_Hb_VDIF_If000A_320000pt_5s_ch1_swspec.bin -bw 32e6 -f0 4.9e6 -f1 5.1e6 \\ | + | 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 \\ | ||
3. Configure and run sctracker \\ | 3. Configure and run sctracker \\ | ||
+ | |||
Edit inifileHb and modify the following fields \\ | Edit inifileHb and modify the following fields \\ | ||
# Input file . InputSource = /mnt/vbsPcal/pcal_on_2205_Hb_No0001_46227 \\ | # Input file . InputSource = /mnt/vbsPcal/pcal_on_2205_Hb_No0001_46227 \\ | ||
Line 82: | Line 116: | ||
Run the sctracker as: \\ | Run the sctracker as: \\ | ||
- | - sctracker inifileHb \\ | + | <note important>sctracker inifileHb \\</note> |
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 \\ |