Open danieludick opened 5 years ago
Just also to mention: The software on our Raspberry Pi for TART-ZA is still running the original code that was sent to us. After performing antenna position measurements (as documented here), I uploaded the following files to the Pi's directory: /home/pi/git/TART/hardware/rpi/24_ant_setup
calibrated_antenna_positions.json.txt telescope_config.json.txt
Thanks for the report. The calibration minimum is returning -7 (this is a log of the function that is minimising) and usually we get around -11.0. A couple of questions.
1) Could you check the timing of the files. There appear to be two files created with close together dates (roughly 2.5 minutes apart) . Is there a chance that you're running two copies of the calibration script? (this shouldn't really stop the calibration working however).
2) Are the diagnose mode outputs showing all green in the telescope web application?
The status map of the antennas show all green:
I did observe just after uploading this, that one of the status flags changed red for a short duration. but is back on green now.
Also seems there is some strong source nearby:
Also clear when looking at the spectra (here the antenna that shows a
There looks to be a fair amount of RF interference in those spectra. Here is a single antenna spectrum from a telescope at a quiet site:
Thanks @tmolteno . Added now the calibration.log file
Thanks for the log file, the calibration process is not doing a good job of finding good phases and gains. I will try and come up with a good way to check for RF interference.
The visibilities can be retrieved from the telescope via the API. Here is how to get them from our live telescope: (https://tart.elec.ac.nz/signal/api/v1/imaging/vis). This will list the real and imaginary parts of the visibilities.
If there is strong RFI, the visibility amplitudes may be approaching 1.0. Typically they should be around 0.2. What numbers are you getting?
I've just noticed that there is a very bright satellite (LUCH 5A) dominating the sky here. This may cause calibration issues.
You can monitor visibilities using the script in /github/TART/doc/calibration/radio_hub. The following command will show the antenna pair 2-3 visibility as a function of time.
python monitor_vis.py --api https://tart.elec.ac.nz/signal --i 2 --j 3
Thanks @tmolteno . I will check the visibilities. Looking at the spectra, I also see that one of the Radio Hubs might be exhibiting on-board RFI (see Antenna 12 cluster).
We are planning to build also a new Radio Hub board. If you get a chance, will you please upload a bill of materials for the components.
Plotted now the monitored visibilities using the monitor_vis.py script for antennas 2 and 3:
Hi @danieludick. The BOM has been uploaded to
hardware/pcb/radio_hub_module/RadioHub2.1/RadioHub2.1_.html
Apologies for the delay.
Those visibilities look reasonable, in that the phase is slowly changing (Consistent with things moving over the sky). Could you run the command for a short baseline pair, and a long baseline pair (roughly east-west) and you should see the phase changing faster in the long pair, vs the short pair.
After installing the latest object detection server and calibration software on my Ubuntu 18.04 PC, I am not having any luck with our TART system in SA.
For reference, the image produced looks as follows:
Just for reference, this calibration was run using the following:
Then I did:
And when inside the bash attached to this docker machine, I executed the following:
The following output snippet was produced:
There is a directory in my $HOME with the following content:
I have attached now the file cal_2019_02_20_15_38_37.json (added .txt extension to get it on GitHub):
cal_2019_02_20_15_38_37.json.txt