Live data from Hacker News

Viewing profile — pietern

pietern

HN member
Joined
Mon, Jan 03, 2011, 1:22 PM UTC
HN karma
25
Public activity
13 items

About pietern

No profile information was provided.

Recent public activity

  1. comment
    Comment #18072711

    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.

  2. comment
    Comment #18072616

    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 …

  3. comment
    Comment #18072583

    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…

  4. comment
    Comment #18071016

    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 wi…

  5. comment
    Comment #18070333

    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 availab…

  6. comment
    Comment #18070311

    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 f…

  7. comment
    Comment #14546196

    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 the…

  8. comment
    Comment #14546161

    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 rendez…

  9. comment
    Comment #14542961

    Interconnect between the servers is 50 Gbit Ethernet (see section 4 of the paper).

  10. comment
    Comment #2311003

    Or set the OPTIMIZATION environment variable for even more control ;-)

  11. comment
    Comment #2151946

    It's called optimistic for a reason. You assume there is low contention and configure your client to have random back off.

  12. comment
    Comment #2064378

    Sorry about that, just deployed a fix to make it less likely for session identifiers to collide. Shouldn't happen again.

  13. comment
    Comment #2063043

    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/red…