News for hackers. Stuff that matters.

gormanc

Re:Robinhood now lets your AI agents trade stocks on Friday May 29, 2026 @01:59PM (#48326864)
Entering the SmarterChild economy
Re:Ask HN: Who is hiring? (May 2018) on Tuesday May 01, 2018 @04:51PM (#16971467)
ooo I'm moving back to Boston in a month or so and this is right up my alley :)
According to the website (https://vectordash.com/hosting/) they use a highly isolated Ubuntu image, so the person hosting the service shouldn't have access to the VM with your model or data on it. It would be nice if there was some third party audit of the software though, the models, the code, and even the training data can be pretty sensitive for researchers.
Visual Studio Code with the LaTeX Workshop addon is definitely my favorite LaTeX editor. The integration with the Chktex linter, latexmk, git, and all that jazz just makes it so much easier to focus on writing.

For research management I had been using Mendeley for a while and got a bit frustrated with the way it handled bibtex. Like it got really annoying when I had papers which fell into multiple categories and/or were used in multiple papers. My new setup is to use JabRef to manage individual bibtex files for specific projects and to use Mendeley just for document management and notes.

Oh also PyCharm is extremely good.

Hot damn this has got me all giddy. How will this work on single node multi-GPU systems? For example, with PyTorch you have to either use threading, multiprocessing, or even MPI. Can you think of a not-too-scary way to use eager execution with multiple GPUs?
Re:Tensorflow sucks on Sunday October 08, 2017 @08:37PM (#15430828)
For installing it, yeah pip is great too, but for building conda includes third party tools and libraries and stuff. e.g. in order to use the MPI backend for PyTorch's distributed processing you need to build it yourself and conda just makes it a bit easier. That and I had a real bad experience with trying to build Tensorflow (and Bazel) to run on an HPC cluster.
Re:Tensorflow sucks on Sunday October 08, 2017 @08:34PM (#15430815)
Not yet! I'm not using convnets or backprop or anything so I don't think it would be beneficial that way, but you could get something similar to what I'm doing by looking at Fritzke's Growing Neural Gas[1]

[1] http://papers.nips.cc/paper/893-a-growing-neural-gas-network...

Re:Tensorflow sucks on Sunday October 08, 2017 @07:32PM (#15430616)
Hell, being able to effortlessly switch between PyTorch and Numpy/SciPy/sklearn/skimage has been so helpful for the project I'm working on. That and I have tensors in later layers whose shapes depend on the training of the previous layers.
Re:Tensorflow sucks on Sunday October 08, 2017 @07:18PM (#15430577)
I love that PyTorch kind of went all-in with anaconda. Building it is so much easier than TF! I'm a recent convert but it's dang good.