nostalgebraist

6 ms·

1.
by nostalgebraist 5y ago
> implies that they're thoroughly disconnected from the realities of ML devops on the cloud FWIW, I deal with "the realities of ML devops on the cloud" nearly every day -- both at work and in hobby projects. The comments h
2.
by nostalgebraist 5y ago
You are confusing Sagemaker (the AWS product) with the Sagemaker python SDK. The Sagemaker python SDK provides a usability wrapper around API calls (etc) that trigger Sagemaker (the product) to do things. In the usage example I screenshott
3.
by nostalgebraist 6y ago
I wasn't referring to one specific graph. The GPT-3 paper ( https://arxiv.org/pdf/2005.14165.pdf ) has a very large number of graphs showing parameter count on the horizontal axis and some kind of prediction quality
4.
by nostalgebraist 7y ago
Serious question: did you read the post? You seem to be critiquing something quite different from what I did.
5.
by nostalgebraist 7y ago
Just wariness about spreading around my tumblr credentials. There’s probably a secure way to do it, I just haven’t thought about it much.
6.
by nostalgebraist 7y ago
If you know what Colab's definition of abusive or disallowed use is (or even whether they have such a definition), please let me know. This isn't meant as a gotcha -- I actually haven't been able to find a full TOS or anythi
7.
by nostalgebraist 7y ago
I suspect GPT-2's limitations with larger-scale structure have less to do with the capacity to track long-range dependencies (which shouldn't be a problem for an attention-based architecture), and more to do with language modeling
8.
by nostalgebraist 7y ago
hence GPT-2 or its near successors are not dangerous FWIW, my post that's linked here doesn't claim that GPT-2 won't have dangerous successors, just that GPT-2 itself is not very dangerous, and that this doesn't vary m