NLP and Multimodal Machine Learning. Asst. Professor @CityUniLondon

London, UK
Joined September 2015
The ACL Anthology is amazing. It's a shame that CogSci, AAAI, and other conferences don't have something like that
1
2
1
34
3,504
Pranava Madhyastha retweeted
Gradient descent with different momentum hyper parameters
4
6
2
99
28,692
Pranava Madhyastha retweeted
Introducing the world's fastest tokenizer implementation, Gigatoken! Gigatoken is ~500-1000x faster than HuggingFace, and ~100x faster than OpenAI's tiktoken for most tokenizer definitions on most machines. These baselines are already multithreaded Rust implementations! 🧵
84
482
93
4,130
741,142
Pranava Madhyastha retweeted
is k3 actually a transformer? why not consult The Chart!
10
86
4
775
37,835
(a) how did MMLU become the defacto standard benchmark every LLM is trying to beat? (b) it is estimated to contain 9% questions that human experts think are wrong. do we know if humans and models agree on which ones belong in this 9%?
3
1
1
27
3,832
Pranava Madhyastha retweeted
Papers at #EMNLP2024 #3 A counter-example to the frequently adopted mech interp linear representation hypothesis: Recurrent Neural Networks Learn … Non-Linear Representations Fri Nov 15 BlackboxNLP 2024 poster aclanthology.org/2024.blackb… CC @robert_csordas @ChrisGPotts
2
23
88
15,830
the term "experts" in "mixture of experts" in the context of LLMs is highly misleading and does way more harm than good in coming up with a conceptual representation of what this component brings to the table.
10
9
2
160
15,078
i think this is the wrong question. yes, CS graduates are very bad in software development, and a dedicated LLM can be better. but put these graduates in a job, and some will develop to be "senior devs" at some point, capable of working on real-life, large systems. LLMs won't.
You randomly select a graduate from a random but accredited CS/ECE department. How well would they perform--in isolation but with access to google search--in comparison to sonnet 3.5 or o1 on *new* but still undergrad level coding problems?
22%CS/ECE graduate is better
63%LLM is Better
14%Roughly on par
315 votes • Final results
1
4
52
6,964
great opportunity to do a #PhD in #Europe in #ML #AI 🚨🚨🚨 I'll hire 2 students via #ELLIS this year, reach out if you want to do research in: - #reliable and #efficient ML in the wild - scalable #neurosymbolic #nesy AI - #lowrank representations - #tractable inference 🚨🚨🚨
The #ELLISPhD application portal is now open! Apply to top #AI labs & supervisors in Europe with a single application, and choose from different areas & tracks. The call for applications: ellis.eu/news/ellis-phd-prog… Deadline: 15 November 2024 #PhD #PhDProgram #MachineLearning #ML
2
26
3
117
23,136
Pranava Madhyastha retweeted
"How to train a model on 10k H100 GPUs?" has now been immortalized on my blog: soumith.ch/blog/2024-10-02-t…
Replying to @francoisfleuret
There's three parts. 1. Fitting as large of a network and as large of a batch-size as possible onto the 10k/100k/1m H100s -- parallelizing and using memory-saving tricks. 2. Communicating state between these GPUs as quickly as possible 3. Recovering from failures (hardware, software, etc.) as quickly as possible 1. Fitting as large of a network and as large of a batch-size as possible onto the 10k H100s. Parallelizing: 1. parallelize over batches 2. parallelize over layers (i.e. split a layer across GPUs) 3. parallelize across layers (i.e. 1 to N are on GPU1, N+1th layer to N+10th layer are on GPU2) Keep parallelizing until you are able to use all GPUs well, with maximum utilization. Checkpointing / Compute vs memorize: * You need to save certain terms from forward to compute the backprop (save_for_backward). However, if the network is sufficiently large, it is more profitable to free these terms in order to fit a larger batch-size, and recompute them again when you need them to compute the backprop. * Tricks like FSDP discard parts of weights that are held in one GPU (to save memory), and ask for the shards of weights from other GPUs right before they need them. 2. Communicating state between these GPUs as quickly as possible Communication overlap: When you need to communicate among GPUs, try to start communication as soon as you can: * Exampel: when Nth layer is done with backward, while N-1th layer is computing backward, all GPUs with an Nth layer can all-reduce their gradients) Discover and leverage the underlying networking topology: Communicating large amounts of state (gradients, optimizer state) across multiple nodes is complicated. with Sync SGD, you have to communicate this state in a burst, as quickly as you can. we might have multiple layers of switches, and have RDMA (ability to copy GPU memory directly to NIC, bypassing CPU ram entirely), and have frontend and backend NICs (frontend connects to storage like NFS, backend connects GPUs to other GPUs in cluster). So, it's important to leverage all this info when running communication collectives like all-reduce or scatter/gather. All-reduce for example can be done algorithmically in log(n) if you tree-reduce; and the constant factors that change based on the type of fiber connecting one node to another in the tree of networking fiber is important to reduce overall time and latency. Libraries like NCCL do sophisticated discovery of the underlying networking topology and leverage them when we run all-reduce and other collectives. 3. Recovering from failures (hardware, software, etc.) as quickly as possible At 10k GPU scale, things fail all the time -- GPUs, NICs, cables, etc. Some of these failures are easy to detect quickly, some of them you can only detect because one node isn't replying back in time (say a NCCL all-reduce is stuck). We build various tools to monitor and detect fleet health, and remove failed nodes from the fleet as quickly as possible. This is quite hard. Separately, at this large of a scale you can have silent data corruptions from memory bits flipping randomly (due to basic physics and amplifying the probability at this scale), and you suddenly have loss-explosions for no reason other than this random phenomenon. These happen at small-scale too, but very very infrequently so you barely notice. This is very hard to detect before-hand in software. Some hardware has hardware circuitry that does built-in checksums after it computes things -- this way if bit-flips occur the hardware can throw an interrupt. H100s and previous NVIDIA GPUs don't have this feature. To counter all these failures, you would want to save your model state as frequently and as quickly as you can; and when a failure occurs, you want to recover and continue as quickly as you can. Usually, we save model state really quickly to CPU memory in a separate thread and in the background we save from CPU memory to disk or remote storage. We also save model state in shards (this is torch.distributed's checkpointing feature), i.e. not every GPU needs to save all of the model weights; each GPU only needs to save a portion of weights -- and they can recover the other part of weights from other GPU shard checkpoints.
8
76
5
583
88,126
Pranava Madhyastha retweeted
This “English(/French/etc) is the new code” trope bemuses me, even as someone bullish about LLMs substantially changing how we code. A 🧵(1/9)
it won't take long (once we hit The Threshold) for this entire flow to be automated to the point where you vaguely describe your idea and it's deployed a feature complete app within minutes. you'd at most need one idea guy and one infra guy
4
2
13
4,243
Pranava Madhyastha retweeted
Great workshop at AAAI about low-rank representations! These have important consequences for Neurosymbolic: Logical circuits can be understood as low-rank factorisations.
many of the recent successes in #AI #ML are due to #structured low-rank representations! but...What's the connection between #lowrank adapters, #tensor networks, #polynomials and #circuits? join our @RealAAAI workshop to know the answer! 👇👇👇 april-tools.github.io/colora…
2
3
15
1,130
Pranava Madhyastha retweeted
Unless you are an OpenAI employee working on improving their products, I don’t understand why such efforts are science. Why are we (question to faculty) spending taxpayer dollars in doing QA for a closed product by a well-capitalized company that does not give back to science?
54
59
11
731
76,401
Pranava Madhyastha retweeted
Today, we release several Moshi artifacts: a long technical report with all the details behind our model, weights for Moshi and its Mimi codec, along with streaming inference code in Pytorch, Rust and MLX. More details below 🧵 ⬇️ Paper: kyutai.org/Moshi.pdf Repo: github.com/kyutai-labs/moshi HuggingFace: huggingface.co/kmhf
49
384
84
1,652
857,024
Pranava Madhyastha retweeted
as SAC for EMNLP I was asked to read the discussions between the authors and reviewers and had every intention to do so but the length of the discussions is out of control. many tables with results of new experiments, hundreds of lines of code (!). bring back word limits please.
2
3
1
25
6,185
Pranava Madhyastha retweeted
I agree with much of both @emilymbender’s #ACL2024 presidential talk and @yoavgo’s rejoinder, but I want to comment on just one aspect where I disagree with both: the definition and domain of CL vs NLP. 🧵👇
i wrote a few remarks on @emilymbender 's presidential address (her slides are linked from the text, for those who weren't there). let's discuss. gist.github.com/yoavg/f952b7…
2
15
2
150
46,489
Pranava Madhyastha retweeted
PLEASE release this custom html parse PLEASE 🙏
2
5
2
113
8,976
Pranava Madhyastha retweeted
Thoughts exist without language.
Language is primarily a tool for communication rather than thought nature.com/articles/s41586-0… “Language is a defining characteristic of our species, but the function, or functions, that it serves has been debated for centuries. Here we bring recent evidence from neuroscience and allied disciplines to argue that in modern humans, language is a tool for communication, contrary to a prominent view that we use language for thinking. We begin by introducing the brain network that supports linguistic ability in humans. We then review evidence for a double dissociation between language and thought, and discuss several properties of language that suggest that it is optimized for communication. We conclude that although the emergence of language has unquestionably transformed human culture, language does not appear to be a prerequisite for complex thought, including symbolic thought. Instead, language is a powerful tool for the transmission of cultural knowledge; it plausibly co-evolved with our thinking and reasoning capacities, and only reflects, rather than gives rise to, the signature sophistication of human cognition.”
561
250
160
2,751
453,308
Pranava Madhyastha retweeted
Replying to @nathanbenaich
THEY WROTE ERROR BOUNDS SO IT’S REAL SCIENCE
1
1
26
1,591
Pranava Madhyastha retweeted
New essay: ML seems to promise discovery without understanding, but this is fool's gold that has led to a reproducibility crisis in ML-based science. aisnakeoil.com/p/scientists-… (with @sayashk). In 2021 we compiled evidence that an error called leakage is pervasive in ML models across scientific fields. In our most recent survey the number of affected fields has climbed to 30. reproducible.cs.princeton.ed… Leakage is only one of many reasons for reproducibility failures. There are widespread shortcomings in every step of ML-based science, from data collection to preprocessing and reporting results. reforms.cs.princeton.edu/app… Root causes The reasons for pre-ML replication crises, such as publication bias, also apply to ML. But a new and important reason for the poor quality of ML-based science is pervasive hype, resulting in the lack of a skeptical mindset among researchers, which is a cornerstone of good scientific practice. We’ve observed that when researchers have overoptimistic expectations, and their ML model performs poorly, they assume that they did something wrong and tweak the model, when in fact they should strongly consider the possibility that they have run up against inherent limits to predictability. Conversely, they tend to be credulous when their model performs well, when in fact they should be on high alert for leakage or other flaws. And if the model performs better than expected, they assume that it has discovered patterns in the data that no human could have thought of, and the myth of AI as an alien intelligence makes this explanation seem readily plausible. This is a feedback loop. Overoptimism fuels flawed research which further misleads other researchers in the field about what they should and shouldn’t expect AI to be able to do. aisnakeoil.com/p/scientists-… Glimmers of hope Researchers should in principle be able to download a paper’s code and data, review it, and check whether they can reproduce the reported results. And the vast majority of errors can be avoided if the researchers know what to look out for. So we think that the problem can be greatly mitigated by a culture change where researchers systematically exercise more care in their work and reproducibility studies are incentivized. We have led a few efforts to change this. First, our leakage paper has had an impact. Many researchers have used it to avoid leakage in their own work and to check previously published work. reproducible.cs.princeton.ed… Beyond leakage, we led a group of 19 researchers across computer science, data science, social sciences, mathematics, and biomedical research to develop the REFORMS checklist for ML-based science. It is a 32-item checklist that can help researchers catch eight kinds of common pitfalls in ML-based science. It was recently published in Science Advances. Of course, checklists by themselves won’t help if there isn’t a culture change, but based on the reception so far, we are cautiously optimistic. reforms.cs.princeton.edu/ A tool, not a revolution Of course, AI can be a useful tool for scientists. The key word is tool. AI is not a revolution. It is not a replacement for human understanding — to think so is to miss the point of science. AI does not offer a shortcut to the hard work and frustration inherent to research. AI is not an oracle and cannot see the future. We are at an interesting moment in the history of science. Look at these graphs showing the adoption of AI in various fields (by Duede et al. arxiv.org/abs/2405.15828): These hockey stick graphs are not good news. They should be terrifying. Adopting AI requires changes to scientific epistemology. No scientific field has the capacity to accomplish this on a timescale of a couple of years. This is not what happens when a tool or method is adopted organically. It happens when scientists jump on a trend to get funding. Given the level of hype, scientists don’t need additional incentives to adopt AI. That means AI-for-science funding programs are probably making things worse. We doubt the avalanche of flawed research can be stopped, but if at least a fraction of AI-for-science funding were diverted to better training, critical inquiry, meta-science, reproducibility, and other quality-control efforts, the havoc can be minimized. aisnakeoil.com/p/scientists-… P. S. Our book AI Snake Oil is all about how to separate real AI advances from hype. It's now available to preorder (and we're told preordering makes a big difference to the book's success). amazon.com/Snake-Oil-Artific… bookshop.org/p/books/ai-snak…
30
271
47
969
388,176