-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not converting all scans in archive data to ms and Read timed out #186
Comments
The read timeout is most likely because @ludwigschwardt seems to like setting short timeouts for some reason. Try searching for I can't imagine what would cause scans to be skipped non-deterministically, but maybe see if increasing the timeout fixes that problem too. |
@sirothia @spassmoor did the suggested workaround work? |
@bmerry the problem re-occurered for me so I rewrote my data reading function to read a scan (~50 reads) at a time for all antennas instead of originally reading for one Antenna at a time , one scan at a time ( about ~3000 reads). This seems to work , also 20 times faster read times. |
@sirothia, just be aware that MS conversion only considers scans where the reference antenna tracks an radec target, so any 'slew' or 'scan' antenna activity, or azel or satellite targets, are ignored. |
So i tried using mvftoms a quite heavily over the last few days. I found that the timeouts occur whether you use the haproxy or any of the gateways into ceph. However, once I used the suggestion by @bmerry I found I could quite happily convert observations without a problem. |
mvftoms.py does not convert all scans in the archive data to ms. Each time I try generates different ms with several scans missing. Also sometimes gives Read timed out error somewhere midway and stop converting. Have tried this on following datasets
1536252666_sdp_l0.rdb
1536431487_sdp_l0.rdb
1536438420_sdp_l0.rdb
1536607816_sdp_l0.rdb
log file for two of conversion using 1536252666_sdp_l0.rdb are attached
1536252666_std.txt
1536252666_std_1.txt
The text was updated successfully, but these errors were encountered: