Research Projects
Small teams of guild members, each taking one research question all the way to a published paper.
Open projects
Projects looking for members right now.
Why it matters
Companies are starting to hand data analysis to agents, and A/B tests drive real product decisions. The traps, like peeking early, sample-ratio mismatch and Simpson’s paradox, are well documented, so there is a clear standard to grade against.
- Finish line
- NeurIPS 2027 · deadline ~May 2027Paper, arXiv preprint and an open benchmark
- Looking for
- Experimentation or causal inference experience
- Someone to build the simulator and evaluation harness
- Someone to drive analysis and writing
- Commitment
- 6–8 hrs/week until publication, with a biweekly group sync
Why it matters
These models now rival tuned gradient-boosted trees on small tables, which is where most real-world decision data lives. Almost nothing is known about how they work inside, and that matters before trusting them with decisions.
- Finish line
- NeurIPS 2027 · deadline ~May 2027Paper, arXiv preprint and code
- Looking for
- Interpretability or learning theory background
- Comfort with PyTorch internals
- Classical statistics or tabular ML experience
- Commitment
- 6–8 hrs/week until publication, with a biweekly group sync
Why it matters
Data, not compute, is increasingly the lever for reasoning, and it is the lever a small team can actually pull. Knowing what to train on makes capable reasoning models cheaper for everyone.
- Finish line
- COLM 2027 · deadline ~March 2027Paper, arXiv preprint and the curated datasets
- Looking for
- Experience fine-tuning language models
- Someone to own the data pipeline
- Someone to own evaluation and analysis
- Commitment
- 6–8 hrs/week until publication, with a biweekly group sync
Why it matters
Agent benchmarks steer research and spending, but scores often come from a single run on a few hundred tasks, some of them broken. Knowing which gains are real tells the field which ideas actually work.
- Finish line
- NeurIPS 2027 · deadline ~May 2027Paper, arXiv preprint and an open analysis toolkit
- Looking for
- Statistics or psychometrics background
- Someone to collect and clean leaderboard data
- Someone to drive analysis and writing
- Commitment
- 6–8 hrs/week until publication, with a biweekly group sync
Why it matters
More thinking at test time drives much of recent progress, and models are starting to make real decisions. Yet most of the evidence comes from math and code, where an answer is simply right or wrong.
- Finish line
- NeurIPS 2027 · deadline ~May 2027Paper, arXiv preprint and code
- Looking for
- Decision theory, operations research or behavioral economics
- Someone to build the decision task suite
- Someone to run and evaluate open models
- Commitment
- 6–8 hrs/week until publication, with a biweekly group sync
Post a short pitch on Discord. Four lines are enough:
- Question
- What do you want to find out?
- Why now
- Why does it matter, and why is it tractable today?
- Done
- What does finished look like, and by when?
- Team
- Who do you need, and for how many hours a week?
How it works
Register interest
Tell us about yourself and the hours a week you can commit.
Get approved
The project lead reads every request and replies by email.
Become a Member of Technical Research
Research every week in the hours you committed, with a biweekly sync for your group, until publication.
What you get
- Co-authorship on a paper published openly under NY-MLR.
- Public credit for your work on the project and on the site.
- A slot to present the finished work at a NY-MLR colloquium.
- Feedback from members across labs, schools and companies.
- Collaborators for your next project, and support to lead one.
What we ask
- Put in the hours you committed each week, or say so early if you can’t.
- Keep NY-MLR as the primary affiliation on the work.
- Share progress at your group’s biweekly sync.
- Help the next group: read a draft, advise a pitch.
Research tracks
I.Foundations
Theory & Science of Deep Learning
Why do networks with far more parameters than training examples still generalize, and why does performance improve so predictably with scale? This track builds the math and the careful experiments that explain how training actually works.
Classical theory said huge models should overfit. They don’t, and explaining why turns rules of thumb into predictions, like scaling laws that forecast a model’s loss before it is trained.
Mechanistic Interpretability
Reverse-engineering trained networks into parts people can understand: which concepts a model represents internally, and which circuits combine them to produce a behavior.
Models store far more concepts than they have neurons by packing them into overlapping directions. Tools like sparse autoencoders pull these apart, so you can find a concept, such as the Golden Gate Bridge or buggy code, and turn it up or down to see what it does.
Probabilistic ML & Uncertainty
Models that know what they don’t know: ways to measure, calibrate and communicate how confident a prediction should be, from Bayesian methods to conformal prediction.
A prediction is only useful for a decision if you know how far to trust it. Conformal prediction wraps any model, even a black box, and returns answers with a guaranteed error rate, under only mild assumptions about the data.
II.Methods
Generative Modeling
Models that learn a whole distribution of data well enough to create new samples from it: images, video, molecules, text. Diffusion and flow models do it by gradually turning noise into data.
Text doesn’t have to be written left to right. Diffusion language models draft every position at once and refine it, which promises faster generation and the ability to edit text in place.
Reinforcement Learning & Post-Training
Turning a pretrained model into a useful one: learning from human feedback, from rewards a computer can check, and from the model’s own attempts.
Rewarding only whether a math answer is correct, with no worked solutions to copy, is enough for models to learn to check their work and backtrack on their own. That is a large part of how today’s reasoning models were made.
Data-Centric ML
Treating data as the thing to engineer: what to collect, filter, mix and synthesize, and which examples a model actually learned a behavior from.
The choice of data often matters more than the choice of architecture. Careful filtering lets small models match larger ones trained on far more, and data attribution can trace a model’s behavior back to the examples that caused it.
Architectures & Efficient ML
Designing models that do more with less compute and memory: new layer types, sparse mixtures of experts, and ways to shrink and speed up a model after training.
The cost of attention grows with the square of the input length. State-space models and linear attention grow linearly, and quantization runs a model in 4 bits instead of 16, often with little loss. Efficiency decides what can run on a laptop or a phone.
Geometric & Structured Learning
Building known structure into a model. A molecule’s properties don’t change when you rotate it, and a graph means the same thing however its nodes are numbered.
A model that respects a symmetry by design doesn’t have to learn it from data, so it needs far less data. That is part of why such models do so well in chemistry and physics, where data is scarce.
III.Capabilities
Reasoning & Test-Time Compute
Getting better answers by letting a model think longer: writing out steps, searching over alternatives, and checking its own work.
Spending compute while answering, not just while training, has become a second way to scale. A small model that thinks longer can match a much larger one on hard math, and how far that carries beyond math and code is still open.
Agents & Tool Use
Models that act: they plan, call tools, run code and browse, working through a task over many steps instead of answering in one shot.
Small errors compound. An agent that gets each step right 95% of the time will usually fail a 50-step task, so reliability, not raw intelligence, is often what holds agents back.
World Models & Embodied AI
Models that learn how the world changes in response to actions, and agents such as robots that use them to act in the physical world.
A model that can predict what happens next lets an agent rehearse in imagination before it acts. Simulators learned from video are starting to stand in for hand-built ones when training robots.
Multimodal Learning
Models that work across vision, audio and language at once, and connect words to the things they refer to.
Vision-language models often answer questions about an image without really looking at it, leaning on what the words suggest instead. Measuring and fixing that is key to trusting them with charts, scans and screens.
Memory, Retrieval & Continual Learning
How models remember: long context windows, retrieval from outside documents, and learning new things after deployment without forgetting the old.
Today’s models mostly stop learning once they are trained. Making them keep learning on the job, cheaply and safely, would change what they are useful for, and it is still largely unsolved.
IV.Trust & Applications
Evaluation & Measurement
The science of measuring what models can do: building benchmarks that test what they claim to, and telling real progress from noise.
Benchmarks leak into training data, saturate, and sometimes contain wrong answers, so a gain on a leaderboard can mean less than it looks. Good measurement is how the field learns which ideas actually work.
Alignment, Safety & Robustness
Making models reliably do what we intend, even under pressure: from adversarial inputs and jailbreaks to models that exploit flaws in how they are rewarded.
Optimize a model hard against an imperfect reward and it finds the imperfections. Studying this reward hacking at small scale is one of the few safety questions you can research rigorously on a modest budget.
AI for Science
Using machine learning as a scientific instrument: predicting protein structures, discovering materials, simulating physics and climate, and generating hypotheses.
AlphaFold’s protein structure predictions shared the 2024 Nobel Prize in Chemistry. In many fields the bottleneck is now turning a model’s predictions into results that can be tested and trusted.
Human-Centered AI
How people and AI systems work together, and what AI does to the people and institutions that use it: collaboration, fairness, and effects on work.
A model that is more accurate than people can still make a team worse if people trust it at the wrong moments. Knowing when to rely on AI matters as much as making AI better.
Applied Decision Intelligence
Using machine learning to make better decisions, not just better predictions: forecasting, experimentation, causal inference and optimization under uncertainty, in finance, health, operations and cities.
A more accurate forecast doesn’t always lead to a better decision, because what matters is the cost of the mistakes you make. Training and judging models by the decisions they lead to is where much of the real-world value is.
FAQ
Why join the guild?
Because research goes further with collaborators. The guild brings together people from New York’s universities, labs and companies for monthly talks, ongoing discussion on Discord, and research projects that take a question all the way to a published paper.
Who can come to guild events?
Anyone with a sincere interest in machine learning research. Colloquia are open to everyone.
What is a Member of Technical Research?
Someone working on one of the guild’s research projects, approved by the project lead. Anyone can take part in the guild, but only people on a project are Members of Technical Research, and joining one has a higher bar.
Read more and apply →What is the one thing to know if I’m approved?
You have to contribute. At kickoff every member takes on a concrete role and deliverables, and progress is shared at the group’s biweekly sync. If you stop contributing, the project lead can remove you from the group, and authorship goes to the people who did the work.
It cuts both ways: members who see a project through get priority for future projects and the chance to lead one.
How does authorship work?
Each group agrees on roles and authorship at kickoff, before work starts, and checks again before submitting. It is the team’s call. If a group can’t settle something, senior members can help.
Who owns the work, and where is it published?
You and your co-authors own your work. It is published openly, with the New York Machine Learning Research Guild (NY-MLR) as the primary affiliation. You may also list your employer or school if they explicitly allow it and every co-author agrees.
Before you join, check that your employment or school agreements allow outside research. Some claim rights to work you do on your own time.
Can I use data or code from my job?
No. Never bring proprietary or confidential information into a project, and never disclose anything your employer or institution has not made public. Projects use only public data, code and models. The work is academic and community-driven, and it stays that way.
What happens when a project ends?
Working groups are temporary by design, like a party in an MMO: formed for one project and disbanded when it ships, unless the members choose to keep going together on the next one.
Can I propose my own project?
Yes. Post a short pitch on Discord: the question, why now, what done looks like, and who you need. If it gathers a team, it goes on the board.
Do I need to be in New York, or on Discord?
Colloquia are in person in New York. Projects, including their biweekly syncs, can be fully remote. Discord is where ongoing discussion happens, but you don’t need it to register interest.
Is NY-MLR affiliated with a university or company?
No. NY-MLR is an informal community of people interested in machine learning research: a gathering place for anyone looking for companions and collaborators to take on the problems on their mind. Partners host some of our events, but they don’t run the guild.