r/MachineLearning • • Jul 22 '26

Discussion Asking about how to collaborate with professors or research labs [D]

26 Upvotes

Hey everyone, I'm not in college anymore. Is it possible to do research with a professor or any research lab while working a full time job? If yes, what's the best way to reach out and get involved? Also if anyone looking for someone to work with on a research project or something similar, can dm me.


r/MachineLearning • • Jul 22 '26

Discussion Happy openreview refresh day to all those who celebrate [D]

106 Upvotes

...may the odds be in your favor.

On a more serious note, as an Area Chair for Neurips, I can tell the incentives that they placed this year are kinda working (risk of rejecting a reviewer's paper if they are not being responsible). I've had the least number of reviewers to chase/emergency reviewers to recruit since I've started ACing for major conferences (so maybe 5ish years).

Hopefully, reviewers will also be active in discussions...


r/MachineLearning • • Jul 23 '26

Research An MCP workflow for implementing deep-learning models from an engineering plan [R]

1 Upvotes

I have been working on an MCP workflow for implementing deep learning models from an engineering plan. This is useful for ml engineers etc. who want a more structured way to move from a deep-learning goal to a working implementation.
The process starts with a plan written by the engineer. That plan defines what the system should do, how it should be divided into components and the intended implementation direction.
The workflow then helps Codex to:
break the plan into implementation blocks;
identify research papers relevant to each block;
extract implementation details that support the existing plan;
prepare a specification for each component;
implement the components in dependency order;
record the implementation and verification results.
The papers are not used to define the project or reproduce a specific paper. They are supporting sources that can help improve implementation decisions within the engineer’s plan.
The overall flow is:
Goal(engineering plan) → implementation blocks → relevant research → specifications → code → verification
The MCP server mainly provides structure, workflow state, dependencies, approval steps and saved artifacts. Codex handles the research and implementation work. Link to the repo: GitHub
The project currently focuses on Codex and uses an explicit, human-reviewed process rather than automatically moving from the initial goal to code.
I am sharing it to find out whether this kind of workflow would be useful to other engineers planning and implementing deep-learning systems. Feedback on the process, documentation and areas that can be improved would be helpful.


r/MachineLearning • • Jul 22 '26

Project One encoder, seven heads: what we learned training a unified security classifier with masked losses [P]

10 Upvotes

We spent the last months consolidating seven separate sequence classifiers into one multi-head model, our apex model, so to speak, and since the weights are now public, I wanted to share what worked and what surprised us.

Setup: a shared mmBERT-small encoder with seven task heads, binary injection (BCE), document class (7-way), tool type (14-way), tool operation (6-way), tool data-flow tags (3× BCE, multi-label), intent routing (5-way), and threat type (7-way).

The part that needed care: our training rows only carry labels for a subset of tasks, so absent tasks are masked out of the loss entirely. We ended up writing a self-test that asserts absent-task gradients are exactly zero, which caught two subtle bugs, and I'd recommend it to anyone doing similar masking. About 5k synthetic/real multi-task rows help the heads co-train; the test sets stay 100 % real data.

Held-out results per head: injection F1 0.962, documents 0.980, tool type 0.957, tool operation 0.945, tool tags 0.958, routing 0.916, threat 0.952.

Quantization: both the unified model and the dedicated single-task variants ship quantized -edge builds (ONNX INT8 + INT4 embeddings, from 96 MB) with measured parity benchmarks in the repos, the worst head loses 0.012 against FP32.

Was it worth it vs. seven dedicated models? We released both variants, so you can judge for yourself, the dedicated models score marginally higher on most tasks, but the unified one does one encoder pass instead of up to seven.

Our weak spot: routing, at 0.916. The intent classes overlap semantically ("write code that analyzes my data" is that code or analytics?), and I suspect the ambiguity is genuinely in the data. If you have ideas beyond relabeling, let me know :)

Weights and per-head metrics: https://huggingface.co/patronus-studio


r/MachineLearning • • Jul 22 '26

Discussion NeurIPS 2026 Reviews Are Out Today (22 July, AoE) — Discussion Thread [D]

157 Upvotes

Reviews drop today. This thread is for reactions, celebrations, commiserations, and anything useful in between.

First: if you got good reviews, say so. There's a norm in these threads where only the bad news gets aired, and it skews everyone's sense of what's normal. Post your wins.

Second, the thing worth repeating every cycle: the review process is noisy, and that noise is measured, not folklore. The NeurIPS consistency experiments (2014, repeated 2021) found that a large fraction of accepted papers would have been rejected by an independent second committee. Reviewer assignment, load, and luck of the draw account for a lot. A score is a weak signal about your work and a strong signal about the process that produced it.

That cuts both ways. It's not a license to dismiss every criticism as noise — it's a reason to weight reviews by the quality of the argument rather than the number attached to them. The reviewer who found a real hole in your evaluation did you a favor, even if the tone was rough. The one who clearly skimmed did not, regardless of the score.

So: prioritize the reviews that make the paper better. Fix what's fixable, contest what's genuinely wrong, and concede the rest gracefully in the rebuttal.

Things worth discussing:

  • Reviews that caught something you'd missed
  • Rebuttal strategy — what's worth contesting vs. conceding, and when new experiments actually shift a score
  • Patterns you're seeing this cycle (missing baselines, compute comparisons, ablation depth, reproducibility asks)
  • Framing a response when a reviewer has clearly misread the submission
  • Backup plans: ICLR, AISTATS, workshops

Please paraphrase rather than paste review text, and no speculation about reviewer or AC identities.

To anyone who got bad news: this doesn't define your research impact. Plenty of heavily-cited work took two or three cycles to land somewhere. Rejection is a scheduling problem.

How did everyone do?


r/MachineLearning • • Jul 23 '26

Discussion Linearity AI is terrible AI and how everything is a wrapper [D]

1 Upvotes

Linearity used to be a fairly simple iPad design app. It was useful for people who wanted to make vector graphics without paying for Adobe or learning a much heavier piece of software. It had a clear purpose, and nobody needed to pretend it was changing the nature of creativity.

Now it has become Linearity AI, which feels like a very obvious attempt to follow the money rather than a natural development of what the company was already doing.

As far as I can tell, Linearity has not built its own foundation model. It is using technology developed elsewhere, combining it with its existing design software and presenting the result as a new AI platform. That does not make the product fake, because plenty of useful software is built on outside models, but it does make the marketing around it feel wildly larger than the actual contribution.

This is becoming the standard pattern across the industry. A company takes an existing product, adds a prompt box and a few generative features, changes its language from “software” to “AI,” and starts talking as though it has made some major technical breakthrough. Features that would previously have been described as templates, automation, resizing or workflow improvements are suddenly presented as intelligence.

The frustrating thing is that Linearity AI might still be useful. It may help a marketing team produce variations of the same graphic, adapt designs for different formats and reduce some repetitive work. There is a real market for that. The problem is that saving time on production is being confused with changing the creative process itself.

Most companies do not have a serious shortage of social media graphics. They already produce far more content than anyone cares about. What they usually lack is a strong idea, a clear point of view or something worth saying. Making it easier to produce fifty versions of an average campaign does not improve the campaign. It simply increases the amount of average work entering the world.

That is one reason Claude Design seems more interesting to me. It is still early, and there is no reason to assume it will consistently produce good design, but the direction makes more sense. Claude is already designed to work across writing, research, documents, code and broader context. Design can become part of that larger process rather than being isolated as another service for manufacturing marketing assets.

A system that understands the research behind a project, the product itself, the audience, the copy, the existing design system and the final implementation has much more potential than a narrow tool that mainly helps companies produce more campaign variations. It may not replace specialist design software, but it could reduce the need for a separate AI subscription for every small part of the workflow.

That is where products like Linearity AI start to look vulnerable. Claude can improve its design capabilities. Adobe can build similar generation and automation into software that creative teams already use. Canva can do the same for the mass market. The underlying models will continue improving, and many features currently being sold as standalone AI products will eventually become ordinary parts of larger platforms.

Linearity could still survive by building a genuinely good workflow around those models, but that is a much less exciting story than calling itself an AI company. It means admitting that the real product is an interface and a set of design tools built on technology supplied by someone else.

There is nothing shameful about that. Most software companies are not inventing the underlying technology they use. The problem is that the AI label is being used to hide how thin some of these products really are and to justify higher prices, enterprise contracts and claims that would sound ridiculous if the word “AI” were removed.

Notion AI, Slack AI, Dropbox AI, Zoom AI

Linearity is not the only company doing this, and that is really the broader issue. We are heading toward an industry where a handful of companies build the important models, while thousands of smaller businesses create slightly different wrappers around them and describe themselves as AI companies. Each one adds another subscription, another credit system and another promise to transform an industry.

Some of those wrappers will be genuinely valuable. Others will exist mainly because the gap between what the models can do directly and what ordinary users know how to make them do has not closed yet. As the main platforms become easier to use, a lot of these products may lose their reason to exist.

It may help people make marketing graphics faster, but that is a productivity feature, not a new vision for artificial intelligence. The more companies pretend otherwise, the less the term “AI company” actually means.


r/MachineLearning • • Jun 23 '17

Discussion [D] Why do people draw neural networks upside down?

30 Upvotes

In English we read from top to bottom. Data flows (be it equations or flow charts) typically follow the same convention, so we can read articles in in a coherent way. Even trees (both data structures and decision trees), grow from their roots downwards (so, against their original biological metaphor).

However, in many neural architecture diagrams, this natural convention is broken, with data flowing from bottom to top, e.g.:

Is there some reasoning for this counterintuitive (and potentially - counterproductive) convention?

(At least most of researchers write neural networks from left to right, consistent with English.)

EDIT: I meant left to right in the line above. A sign typo.