That is awesome to hear! Building this has been a fun side project and I'm happy to hear it sparked interest for you as well.
Yes, there are multiple interfaces. This is a nice interactive one: http://rammb-slider.cira.colostate.edu/?sat=goes-16. There is also an S3 bucket where you can find all data as soon as it is available:…
Great, if you end up building one, keep us updated (here or on Twitter). 1) Yes, this is DCS (Data Collection System) data. It's a very low bandwidth signal (300 or 1200 baud) that ground stations uplink to GOES on UHF.…
Depends on the mode the satellite is operating in. Typically: a full disk image every 15 minutes, the continental USA every 5 minutes, and two selected "mesoscale" regions (they will move around based on interesting…
Hi everybody, cool to see this submitted on HN. I'm around for questions so ask away. Also beware that the guide is a little out of date: 1) the listed antenna is no longer available, but there are comparable ones for…
It's not. The SUVI data is not broadcast on the HRIT feed, only on the GRB (GOES ReBroadcast) feed. Receiving GRB requires more effort: minimum 10ft dish, dual circular polarized feed, DVB-S2 demodulator, and different…
Re: your second point, it is strictly synchronous, though since there are 8 GPUs per process (thus have 1 process per machine) the gradient reduction is done in 3 phases. First they are reduced within the process, then…
Hi Salvatore! :D And there's even a tiny Redis dependency (optional though) in the code to generate these results. In particular the collective communication library needs a rendezvous phase where all nodes connect to…
Interconnect between the servers is 50 Gbit Ethernet (see section 4 of the paper).
Or set the OPTIMIZATION environment variable for even more control ;-)
It's called optimistic for a reason. You assume there is low contention and configure your client to have random back off.
Sorry about that, just deployed a fix to make it less likely for session identifiers to collide. Shouldn't happen again.
All keys are namespaced to a unique session identifier, so parallel sessions are isolated. You can check out the code for the interactive stuff here: https://github.com/antirez/redis-io/tree/master/lib/interact...
That is awesome to hear! Building this has been a fun side project and I'm happy to hear it sparked interest for you as well.
Yes, there are multiple interfaces. This is a nice interactive one: http://rammb-slider.cira.colostate.edu/?sat=goes-16. There is also an S3 bucket where you can find all data as soon as it is available:…
Great, if you end up building one, keep us updated (here or on Twitter). 1) Yes, this is DCS (Data Collection System) data. It's a very low bandwidth signal (300 or 1200 baud) that ground stations uplink to GOES on UHF.…
Depends on the mode the satellite is operating in. Typically: a full disk image every 15 minutes, the continental USA every 5 minutes, and two selected "mesoscale" regions (they will move around based on interesting…
Hi everybody, cool to see this submitted on HN. I'm around for questions so ask away. Also beware that the guide is a little out of date: 1) the listed antenna is no longer available, but there are comparable ones for…
It's not. The SUVI data is not broadcast on the HRIT feed, only on the GRB (GOES ReBroadcast) feed. Receiving GRB requires more effort: minimum 10ft dish, dual circular polarized feed, DVB-S2 demodulator, and different…
Re: your second point, it is strictly synchronous, though since there are 8 GPUs per process (thus have 1 process per machine) the gradient reduction is done in 3 phases. First they are reduced within the process, then…
Hi Salvatore! :D And there's even a tiny Redis dependency (optional though) in the code to generate these results. In particular the collective communication library needs a rendezvous phase where all nodes connect to…
Interconnect between the servers is 50 Gbit Ethernet (see section 4 of the paper).
Or set the OPTIMIZATION environment variable for even more control ;-)
It's called optimistic for a reason. You assume there is low contention and configure your client to have random back off.
Sorry about that, just deployed a fix to make it less likely for session identifiers to collide. Shouldn't happen again.
All keys are namespaced to a unique session identifier, so parallel sessions are isolated. You can check out the code for the interactive stuff here: https://github.com/antirez/redis-io/tree/master/lib/interact...