kristinemlarson
commented
3 months ago no one has done this - which is fine - but i am not going to leave it up as something that has to be done. just a FYI if you are using a docker, i do not personally know how well it works to use parallel processing.
@fgnievinski i'm going to post new versions of rinex2snr and gnssir. these allow up to 10 processes (-par). but in the docker, the number of processes is limited by how you set up the docker, so something you control outside of gnssrefl. i found it in Resources. potentially you also need to set number of allowed processes when you do the 'docker run' command. on my machine it was limited to two, so i tried it with 'docker run --cpus 2'
i have tested out gnssir pretty well - rinex2snr less so. i will need to keep an eye on the error queue and whether archives block multiple downloads at the same time. unavco does not seem to have a problem with ten simultaneous requests. i have NOT tried it with highrate data from CDDIS and i do not plan to any time soon.
basically i need someone who uses the docker to try out these new features so that we know how to change the documentation re: processes. there is no rush on this.
the weekly and monthly options are currently turned off in rinex2snr. i can see how to put them back in - but have not gotten around to it. and likely won't for a while.
FWIW, i have determined that sopac will not allow multiple download processes reliably. unavco seems to not care at all. so i guess i could check for that (if archive is sopac, disable request for parallel).
cddis use of -par should also be disabled. at least in our current configuration. i have not tested all the archives - but GA and the BKG are accessible and provide a big savings in time.
the downloads are behind a try - and that is annoying when trying to debug.