User Tools

Site Tools


development:gnss_calibration

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.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
development:gnss_calibration [2020/11/19 03:37]
Tiege McCarthy
development:gnss_calibration [2021/01/20 22:39]
Tiege McCarthy
Line 23: Line 23:
   * **Recording from spectrum analyser:** I have written a very ugly script that currently grabs trace outputs from the spectrum analyser every 5 seconds during valid time periods (currently from 90s past the start of the scan to the end time). Between the 5 minute blocks it averages all grabbed spectra together and writes them to a file with the timestamp of the scan.   * **Recording from spectrum analyser:** I have written a very ugly script that currently grabs trace outputs from the spectrum analyser every 5 seconds during valid time periods (currently from 90s past the start of the scan to the end time). Between the 5 minute blocks it averages all grabbed spectra together and writes them to a file with the timestamp of the scan.
  
 +**Nov 19, 2020:**:
 +  * **Late start tracks:** The bash script generated during schedule generation has now been updated to include '​if'​ statements with time conditions - this should fix any issues with starting tracks late. Current version of the scripts can be found on my github in a repository named '​antenna_thrust_scripts'​ (https://​github.com/​tiegemccarthy/​antenna_thrust_scripts) (Tiege)
 +
 +**Dec 2, 2020:**:
 +  * **Schedules** Two tracks prepared for this day - one for KOSMOS 2461 (R735) and one for GPS IIRM-8 (G050) (Tiege)
 +  * This day was cancelled due to high winds - had a meeting with Lucia, Jamie and Guifre instead. Tracking postponed until next week. (Tiege)
 +
 +**Dec 8, 2020:**:
 +  * Another cancellation,​ this time due to post-LBA maintenance on the cryo system. (Tiege)
 +
 +**Dec 11, 2020:**:
 +  * **Remote track on GPS IIRM-8:** fixed a few issues with the observing setup. First issue was time stamps in the shell wrapper not working on newsmerd - the date command was for some reason reading them as GMT+7 timezone despite the default output of date being in UTC. This has since been fixed. (Tiege)
 +  * Also fixed a bug in the recording script that occasionally caused a type error when writing out the data with numpy.savetxt(). (Tiege)
 +  * Wrote a script for doing manual (not scheduled) recording using the spectrum analyser - will be useful for when we need to calibration scans on quasars. (Tiege)
 +
 +**Dec 15, 2020:**:
 +  * **Draft observing guide:** I have written a rough guide outlining the steps required in order to undertake the GNSS tracks and recording which currently exists [[https://​docs.google.com/​document/​d/​1ZQYY4cJqCG02h52L18jyCAuboBhCwgeG2JhKxVYTsHk/​edit?​usp=sharing|on my google drive]] (Tiege)
 +
 +**Jan 21, 2021:**:
 +  * **GPS050 tracks:** Finally have a run not being cancelled by weather. Running a full track of GPS050 today (and hopefully tomorrow pending weather) - trying a 2 degree offset on offsource scans as 1 degree was too little in our last run with valid data. Also trying some new spectrum analyzer settings - keeping RBW at 3 MHz and VBW at 10 MHz, but changing span to 999 MHz and sweep points to 333, this should remove the need to resample the data when reducing the data - should know by tomorrow. Ideally we will get another couple of tracks on this source next week to check experiment to experiment repeatability of the results.
 +  * **Flux calibration** Assuming wind remains pleasant, will get some data on a couple of bright quasar sources - 1934-638 is a little too weak for our setup. Would also be good to get multiple sources so we can check SEFD estimations. ​ (Tiege)
  
 **TO DO**: **TO DO**:
Line 32: Line 53:
   * **get value table ready** - try to replicate the tracking table Peter Steigenberger sent through; figure out boresight angle etc (Lucia to ask Ron/Peter)   * **get value table ready** - try to replicate the tracking table Peter Steigenberger sent through; figure out boresight angle etc (Lucia to ask Ron/Peter)
   * **have a look at subsequent estimation** - get all the necessary values together, code an estimator? first understand the code   * **have a look at subsequent estimation** - get all the necessary values together, code an estimator? first understand the code
-  * **next track**: booked in next Wednesday (Nov 18) for more tests+  * <del>**next track**: booked in next Wednesday (Nov 18) for more tests</​del>​
   * **next catchup**: booked in Wednesday (Dec 4)    * **next catchup**: booked in Wednesday (Dec 4) 
  
/home/www/auscope/opswiki/data/pages/development/gnss_calibration.txt · Last modified: 2021/01/25 00:42 by Tiege McCarthy