Hacker Newsnew | past | comments | ask | show | jobs | submit | cgs1019's commentslogin

`cat -n` prints with line numbers, which is occasionally handy.


nl?


To grok the ELBO, don't start with VAEs; start with basic variational inference. https://arxiv.org/abs/1601.00670 is good, though maybe increasingly dated...Once you're happy with VI in general, https://arxiv.org/abs/1606.05908 is a nice read on the VAE.


Thank you! Do you have any recommendations for educational resources at an even more basic level of understanding of variational inference? The first paper you mentioned is "for statisticians", and it seems pretty dense to me on the first glance. My current level is somewhere at the first undergrad pstat course.


Oh yeah that's gonna be a dense read then :)

I really like Kevin Murphy's books. I learned a lot from them when I was getting started on this stuff. He's just released a two part follow up to his 2012 book. Both parts are available online.

I also really like David Mackay's book (also free online). It's...idiosyncratic. But fantastic!

Best of luck with your learning! Start simple, go slow. Write code every step of the way!! ^_^


Hi, tech lead for TFP here. The wording here was unclear -- sorry! We're fixing it presently.

We are not migrating away from TF; far from it!

The change here was to interoperate with TF and JAX (and numpy!), by way of some rewrite trickery under the hood. Essentially, we wrote a translation layer that implements the TF API surface (or, the parts we actually use) in terms of numpy & JAX primitives [1]. This lets us leave most TFP code intact, written in terms of the TF API, but interoperate with JAX by way of the API translation layer. (Actually we implemented numpy support first, and mostly got JAX for "free" since JAX is largely API-compatible with numpy).

Sorry for any confusion!

We're pretty stoked about this work, so happy to answer any other questions you may have (also feel free to chime in on the github tracker or email [email protected])

[1] - https://github.com/tensorflow/probability/tree/master/tensor...


hey thanks for the clarification.

here's what everybody is puzzled on: it looks like the layers going forward are JAX -> Tensorflow -> Keras.

and we are seeing people moving to JAX directly. So this is ending up like a Flutter vs Kotlin issue (also within Google).

Do you envision JAX being low level .. and the high level tensorflow keras interface being the most usable api ?


The link cites a vice article that cites a guardian article: https://www.theguardian.com/world/2016/jul/01/philippines-pr...





Neutrons are electrically neutral but they still interact electromagnetically (they're composed of charged quarks). They have a magnetic moment, for instance [1]. So they wouldn't be dark the way "dark matter" appears (heh) to be.

[1] - https://en.wikipedia.org/wiki/Neutron_magnetic_moment


If dark matter particles had a magnetic moment, how would we know?


They would interact with photons, allowing us to see some effects of concentrations of dark matter against background light sources.


Google's auto library, auto/value in particular, is worth a look: https://github.com/google/auto/tree/master/value


I've always thought it would be fun to somehow incorporate technology into climbing for tracking or otherwise augmenting the experience.

Time trials sound like a quick avenue to painful injury, though. If I were a gym, I'd be cautious in encouraging it. In my experience, climbing prowess is not a matter of speed but control -- the more statically you can complete a route the more control you demonstrate. A friend of mine once said his goal is to complete a route as silently as possible, avoiding accidental scuffs of his shoes or knocking of his knuckles on the wall. This is actually a great measure of control, too.


Explosive power is pretty important though, and this would be a nice way to train it outside of campus boarding which gives you one movement on each side of your body. This gives an avenue for a lot of different movement, but then there are system boards for that as well and those are a little more "quantifiable". Maybe this would be a good way to mix it up of you're bored of system boarding?

I agree about being cautious about using this. It seems like a good way for new people to mess up their shoulders. The thought of hitting crimps that hard/fast is terrifying.

I do really want to take some of my friends who climb like Fred Nicole (super slow and static as possible) and make them use this though. Sometimes utilizing momentum is important. Sometimes climbing everything static is a huge waste of energy and is actually bad technique, despite being generally safer and better for training outright strength (as opposed to power).


> Time trials sound like a quick avenue to painful injury

Oh it's already a thing, injury or no.

https://www.youtube.com/watch?v=n4n6xfu8VDU


That's pretty different than this though. Those people have made those exact moves hundreds or thousands of times. They know how to set their shoulders for those moves and aren't put in situations with novel foot work that could mess up their knees. Those routes are also rather easier than the hardest thing they could climb. All of the holds are massive, not necessarily good, but large enough that finger injury should be very unlikely.

The parent is worried about the combination of pushing the limit of what you can do safely with your strength and doing so as fast as possible. This can lead to being out of control, and strength and technique are part of what keep you safe.

You should probably have a very high level of climbing fitness before you even consider this, though I can see it being potentially quite useful. You would also have to break down what is going on in the route that is generated and how it might be dangerous. Throwing out drop knees[0] and heel hooks[1] and yanking on crimps[2] is a great way to get wrecked if you don't know _exactly_ what you're doing.

[0] - https://www.youtube.com/watch?v=KHlzC7EqyDA

[1] - https://climbingtogetherandotherfunadventures.files.wordpres...

[2] - really tiny holds => https://www.google.com/search?q=climbing+crimp&tbm=isch


Looks like Nature makes the whole paper readable online: http://www.nature.com/nphys/journal/vaop/ncurrent/full/nphys...


Not to me it doesn't. I see this near the bottom of the page:

  READ THE FULL ARTICLE

  Subscribe to      Purchase article
  Nature Physics    full text and PDF:
  for full access:  $32
  $175              [Buy Now]
  [Subscribe]
Edit: Thanks Mr. M.



This appears to point to an unrelated article, "An instability of unitary quantum dynamics" but one of the co-authors of the paper that the article describes.


this is not the article.


Ai sorry, I thought it was the pre-press version of the paper.

See:

https://news.ycombinator.com/item?id=10037257


Oops, maybe I unwittingly had access by being on work VPN. Sorry bout that! Thanks for the open link, jacquesm.


Your link is correct (but paywalled). I have no idea what jacquesm is linking to.


It's not as snazzy as in the article but this alias in my .gitconfig is an integral part of my git workflow:

  gr = !git \
    --no-pager \
    log -n 16 --graph --date-order --date=short --branches \
    --pretty=\
  '%C(yellow bold)%h%Creset\
   %Creset %C(blue bold)%d%Creset\
   %C(white bold blink)%s'
The 'gr' is short for 'graph'. You can tweak the -n to show more history. I actually have several of these, 'gr', 'grr', 'grrr', etc. to show more and more history.


I think your alias might have gotten cut off; the last color tag is never reset. Also, I don't understand, why disable the pager and limit the number of entries?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: