HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
salesforce
awd-lstm-lm
Python2017–2018
salesforce / awd-lstm-lm · Archived

awd-lstm-lm

LSTM and QRNN Language Model Toolkit for PyTorch

2Distinct people
3Mentions
0Explicit recommenders
2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

LSTM and QRNN Language Model Toolkit for PyTorch

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week3 dated mentions

Observed mentions: 2017-10-26 08:23:35 UTC to 2018-05-04 20:13:00 UTC. Weeks start Monday, UTC.

0122017-10-23 00:00:00 UTC to 2017-10-30 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 232017-10-30 00:00:00 UTC to 2017-11-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-11-06 00:00:00 UTC to 2017-11-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-11-13 00:00:00 UTC to 2017-11-20 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-11-20 00:00:00 UTC to 2017-11-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-11-27 00:00:00 UTC to 2017-12-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-12-04 00:00:00 UTC to 2017-12-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-12-11 00:00:00 UTC to 2017-12-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-12-18 00:00:00 UTC to 2017-12-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-12-25 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-01 00:00:00 UTC to 2018-01-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-08 00:00:00 UTC to 2018-01-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-15 00:00:00 UTC to 2018-01-22 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-01-22 00:00:00 UTC to 2018-01-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 222018-01-29 00:00:00 UTC to 2018-02-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-02-05 00:00:00 UTC to 2018-02-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-02-12 00:00:00 UTC to 2018-02-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-02-19 00:00:00 UTC to 2018-02-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-02-26 00:00:00 UTC to 2018-03-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-03-05 00:00:00 UTC to 2018-03-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-03-12 00:00:00 UTC to 2018-03-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-03-19 00:00:00 UTC to 2018-03-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-03-26 00:00:00 UTC to 2018-04-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-02 00:00:00 UTC to 2018-04-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-09 00:00:00 UTC to 2018-04-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-16 00:00:00 UTC to 2018-04-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-23 00:00:00 UTC to 2018-04-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-30 00:00:00 UTC to 2018-05-07 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsApr 30

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Oct 232017-10-23 00:00:00 UTC2017-10-30 00:00:00 UTC101
Oct 302017-10-30 00:00:00 UTC2017-11-06 00:00:00 UTC000
Nov 62017-11-06 00:00:00 UTC2017-11-13 00:00:00 UTC000
Nov 132017-11-13 00:00:00 UTC2017-11-20 00:00:00 UTC000
Nov 202017-11-20 00:00:00 UTC2017-11-27 00:00:00 UTC000
Nov 272017-11-27 00:00:00 UTC2017-12-04 00:00:00 UTC000
Dec 42017-12-04 00:00:00 UTC2017-12-11 00:00:00 UTC000
Dec 112017-12-11 00:00:00 UTC2017-12-18 00:00:00 UTC000
Dec 182017-12-18 00:00:00 UTC2017-12-25 00:00:00 UTC000
Dec 252017-12-25 00:00:00 UTC2018-01-01 00:00:00 UTC000
Jan 12018-01-01 00:00:00 UTC2018-01-08 00:00:00 UTC000
Jan 82018-01-08 00:00:00 UTC2018-01-15 00:00:00 UTC000
Jan 152018-01-15 00:00:00 UTC2018-01-22 00:00:00 UTC000
Jan 222018-01-22 00:00:00 UTC2018-01-29 00:00:00 UTC000
Jan 292018-01-29 00:00:00 UTC2018-02-05 00:00:00 UTC000
Feb 52018-02-05 00:00:00 UTC2018-02-12 00:00:00 UTC000
Feb 122018-02-12 00:00:00 UTC2018-02-19 00:00:00 UTC000
Feb 192018-02-19 00:00:00 UTC2018-02-26 00:00:00 UTC000
Feb 262018-02-26 00:00:00 UTC2018-03-05 00:00:00 UTC000
Mar 52018-03-05 00:00:00 UTC2018-03-12 00:00:00 UTC000
Mar 122018-03-12 00:00:00 UTC2018-03-19 00:00:00 UTC000
Mar 192018-03-19 00:00:00 UTC2018-03-26 00:00:00 UTC000
Mar 262018-03-26 00:00:00 UTC2018-04-02 00:00:00 UTC000
Apr 22018-04-02 00:00:00 UTC2018-04-09 00:00:00 UTC000
Apr 92018-04-09 00:00:00 UTC2018-04-16 00:00:00 UTC000
Apr 162018-04-16 00:00:00 UTC2018-04-23 00:00:00 UTC000
Apr 232018-04-23 00:00:00 UTC2018-04-30 00:00:00 UTC000
Apr 302018-04-30 00:00:00 UTC2018-05-07 00:00:00 UTC202

What Hacker News says

3 sources
tensor: my main point was and is that features learned by a suitable deep model (whether recurrent or attention-based) routinely outperform human-designed features. This has been shown in a large and growing number of sequence tasks (WMT language translation datasets, Stanford Question Answering Dataset, WikiText language modeling datasets, Penn Treebank dataset, IMDB and Stanford Sentiment Treebank movie review datasets, etc. -- to name a few). Now, in some cases, and depending on the task, it might make sense to have the last layer of a deep model be a CRF layer. In the OP's case, for example, one could try replacing all those one-off feature functions with a proven deep architecture -- in other words, instead of having ψ at each time step be equal to exp(sum(weighted feature functions))), have it be a function of the output of the dee
Read the rest
p model. That said, for something like the OP's task, the first thing I would try would be one of the readily available LSTM architectures[a], with a standard softmax layer predicting a distribution over the vocabulary of tags at each time step, and feeding that into a standard beam search.[b] [a] Example: https://github.com/salesforce/awd-lstm-lm/blob/master/model.... [b] Intro to beam search algorithm: https://www.youtube.com/watch?v=UXW6Cs82UKo
In Extracting Structured Data from Recipes Using Conditional Random Fields (2015)
This is the kind of problem for which LSTM RNNs -- and more recently, fully-attention-based deep neural nets -- produce state-of-the-art results. I wonder if the author ever tried using, say, an AWD LSTM RNN[a] or a Transformer-like model[b] for this task. Using an RNN or an attention model for this would eliminate the need for feature engineering such as: feature_1 = 1 if x_t is capitalized and y_t equals "NAME"; 0 otherwise. This is one of seven carefully engineered feature functions listed in the article, and the author states that the seven are only a partial list. Moreover, using a modern RNN or attention model likely would produce better predictions, with much better generalization. [a] https://arxiv.org/abs/1708.02182 / https://github.com/salesforce/awd-lstm-lm [b] https://arxiv.org/abs/1706.03762 / https://github.
Read the rest
In Extracting Structured Data from Recipes Using Conditional Random Fields (2015)
The P3 instances are the first widely and easily accessible machines that use the NVIDIA Tesla V100 GPUs. These GPUs are straight up scary in terms of firepower. To give an understanding of the speed-up compared to the P2 instances for a research project of mine: + P2 (K80) with single GPU: ~95 seconds per epoch + P3 (V100) with single GPU: ~20 seconds per epoch Admittedly this isn't exactly fair for either GPU - the K80 cards are straight up ancient now and the Volta isn't sitting at 100% GPU utilization as it burns through the data too quickly ([CUDA kernel, Python] overhead suddenly become major bottlenecks). This gives you an indication of what a leap this is if you're using GPUs on AWS however. Oh, and the V100 comes with 16GB of (faster) RAM compared to the K80's 12GB of RAM, so you win there too. For anyone using the standard set o
Read the rest
f frameworks (Tensorflow, Keras, PyTorch, Chainer, MXNet, DyNet, DeepLearning4j, ...) this type of speed-up will likely require you to do nothing - except throw more money at the P3 instance :) If you really want to get into the black magic of speed-ups, these cards also feature full FP16 support, which means you can double your TFLOPS by dropping to FP16 from FP32. You'll run into a million problems during training due to the lower precision but these aren't insurmountable and may well be worth the pain for the additional speed-up / better RAM usage. - Good overview of Volta's advantages compared to event the recent P100: https://devblogs.nvidia.com/parallelforall/inside-volta/ - Simple table comparing V100 / P100 / K40 / M40: https://www.anandtech.com/show/11367/nvidia-volta-unveiled-g... - NVIDIA's V100 GPU architecture white paper: http://www.nvidia.com/object/volta-architecture-whitepaper.h... - The numbers above were using my PyTorch code at https://github.com/salesforce/awd-lstm-lm and the Quasi-Recurrent Neural Network (QRNN) at https://github.com/salesforce/pytorch-qrnn which features a custom CUDA kernel for speed
In Introducing Amazon EC2 P3 Instances

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.