5 ms·
Low responsiveness of ML models to critical or deteriorating health conditions
- chiph 2y ago[flagged]
- wswope 2y agoI work in the ICU monitoring field, on the R&D team of a company with live systems at dozens of hospitals and multiple FDA approvals. We use extended Kalman filters (i.e. non-blackbox "ML") to estimate certain lab values of patients that are highly indicative of them crashing, based on live data from whatever set of monitors they're hooked up to - and it's highly robust. What the authors of this paper are doing is throwing stuff at the wall to see if it works, and publishing results. That's not necessarily a bad thing at all, but I say this to underline that their results are not at all reflective of SOTA capabilities, and they're not doing much exploration of prior art.
- jvanderbot 2y agoParameter estimation is ML now?
- klodolph 2y agoI think ML is in quotes for a reason—the reason is because the usage is not typical.
- thenobsta 2y agoWhy not? LLMs, vision models, and kalman filters all learn parameters based on data.
- PaulHoule 2y agoA linear regression model can be written and trained as a neural net, has a loss function, all of that. Most if not all ML problems can be formulated as modelling a probability distribution
- klodolph 2y agoThat’s too reductive—ML models are statistical models. Statistical models have parameters, and in general cases, you choose the parameters with some kind of optimization algorithm. If you play fast and loose with your definition of “ML”, you’ll end up defining it so that any statistical model is an ML model… in which case, why even bother using two different terms? ML models are, broadly speaking, the more complicated ones with more parameters, where the behavior of the models is not really known without training. I’m sure you could nitpick to death any definition I give, but that’s fine.
- PaulHoule 2y agoI am sure there are people teach data science classes who look at it in that "reductive" way. From the viewpoint of engineering, scikit-learn provides the same interface to linear regression that it supplies to many other models. Huggingface provides an interface to models that is similar in a lot of ways but I think a 'regression' in that it doesn't provide the bare minimum of model selection facilities needed to reliably make calibrated models. There are many problems where you could use either linear regression or a much more complex model. When it comes to "not known without training" I'm not sure how much of that is the limit of what we know right now and how much is fundamental as in the problem of "we can't really know what a computer program with free loops with do" (Halting problem) or "we can't predict what side of the side Pluto is going to be on in 30 million years" (Deterministic chaos) (The first industrial model trainer I built was a simultaneously over and under engineered mess like most things in this industry... I didn't appreciate scikit-learn's model selection facilities and even though the data sci's I worked with had a book understanding of them, they didn't really put them to work.)
- AlotOfReading 2y agoCalling EKFs "ML" is certainly a choice.
- Epa095 2y agoIs it less ML than linear regression?
- klodolph 2y agoIf you want to draw the line between ML and not ML, I think you’ll have to put Kalman filters and linear regression on the non-ML side. You can put support vector machines and neural networks on the ML side. In some sense the exact place you draw the distinction is arbitrary. You could try to characterize where the distinction is by saying that models with fewer parameters and lower complexity tend to be called “not ML”, and models with more parameters and higher complexity tend to be called “ML”.
- wrsh07 2y agoLinear regression is literally the second lecture of the Stanford ML class. https://cs229.stanford.edu/ https://cs229.stanford.edu/ If you want to say "not neural networks" or not dnn or not llm, sure. But it's obviously machine learning
- klodolph 2y agoWhen you say it’s “obviously machine learning”, how could that statement possibly be correct? There’s not even broad consensus here… so you don’t get to say that your definition is obviously correct. There are pedagogical reasons why you’d include linear regression in a machine learning course. This is pretty clear to me—they have properties which are extremely important to the field of machine learning field, such as differentiability.
- computerex 2y agoLinear regression is ML. You are off base.
- nyrikki 2y agoAs an intuition on why many people see this as different. PAC Learning is about compression, KF/EKF is more like Taylor expansion. The specific types of PAC Learning that this paper covers has problems with a simplicity bias, and fairly low sensitivity. While based on UHATs, this paper may provide some insights. https://arxiv.org/abs/2502.02393 https://arxiv.org/abs/2502.02393 Obviously LLM and LRMs are the most studied, but even the recent posts on here from anthropic show that without a few high probability entries in the k-top results, confabulations are difficult for transformers. Obviously there are PAC Learning methods that target anomaly detection, but they are very different than even EKF + Mc You will note in this paper that even highly weighted features exhibited low sensitivity. While the industry may find some pathological cases that make the approach usable, autograd and the need for parallelism make the application of this papers methods to tiny variations to multivariate problem ambitious. They also only trained on medical data. Part of the reason the foundation models do so well is that they encode verifiers from a huge corpus that invalidates the traditional bias variance tradeoffs from the early 90's papers. But they are still selecting from the needles and don't have access to the hay in the haystack. The following paper is really not related except it shows how compression exacerbates that problem. https://arxiv.org/abs/2205.06977 https://arxiv.org/abs/2205.06977 Chaitin's constant encoding the Halting problem, and that it is normal and uncomputable is the extreme top end of computability, but relates to the compression idea. EKFs have access to the computable reals, and while non-linear, KF and EKFs can be thought of linearization of the approximations as a lens. If the diagnostic indicators were both ergodic and Markovian, this paper's approach would probably be fairly reliable. But these efforts are really about finding a many to one reduction that works. I am skeptical about it in this case for PAC ML, but perhaps they will find a pathological case. But the tradeoffs between statistical learning and expansive methods are quite different. Obviously hype cycles drive efforts, I encourage you to look at this years AAAI conference report and see that you are not alone with the frustration on the single minded approach. IMHO this paper is a net positive, showing that we are moving from a broad exploration to targeted applications. But that is just my opinion.
- anthk 2y agoLLM models are organic? They somehow obbey the laws of Thermodinamycs by some parallel on algorythms and underlying Math? It would be amazing if it were some parallel between Biologhycs (specially Funghi with emergent properties) and neural networks...
- magicalhippo 2y agoFor IHM prediction, LSTM models and transformer models were trained for 100 epochs using the MIMIC-III and eICU datasets separately. I might be blind, but I don't see any mention of loss. Did they stop at 100 because it was a nice round number or because it was a good place to stop? The LSTM model they used had 7k trainable parameters, the CW-LSTM model 153k while the transformer model had 800k parameters (300k trainable parameters and 600k optimizer parameters as they say). I don't follow the field close enough, but is it reasonable these models all converged at the same time, given the large difference in size? They mention the transformer model outperforming the LSTMs, but I wonder if it could have done a lot better.
- PaulHoule 2y agoWhat ever happened to early stopping? I see so many papers where people train neural networks with half-baked recipes. I think I saw early stopping first around 1990 but it is so often for people to pick some arbitrary number of epochs to run. I have to admit I never liked the term "early stopping", I think people should have called it just "stopping", because it makes it seem optional. Back when I was training LSTM networks it was straightforward to train nets reliably with early stopping...
- Al-Khwarizmi 2y agoI'm also annoyed about this. I suppose the main reason is because 20 years ago, if you didn't use early stopping, typically your accuracy would plummet. In earlier, smaller neural networks, overfitting was a huge issue; and lack of dropout, batch normalization, etc. made learning much more brittle. Now the young'uns don't bother because you can just set 100 epochs, or whatever, and the result might not be optimal but it will generally be fine. Still, it's a pity because you're often wasting computational resources that could be spent in trying alternative architectures, exploring hyperparameters or whatever. BTW, I also think "early stopping" is a terrible name. If you don't know the term, it suggests that you're going to undertrain the network, sacrificing some accuracy for efficiency. No one wants undertrained networks. I think it's not an overstatement to say that if it were called "adaptive stopping", "validation guided stopping", or even something more catchy like "smart stopping", probably more people would use it.
- amelius 2y agoMaybe start a Kaggle competition?
- MeteorMarc 2y agoMaybe the training set had too many zeroshot patients.
- bbstats 2y agoAm I missing something or is this just "We built models that are bad"?
- ohgr 2y agoBad model, bad method or bad paper?
- timewizard 2y agoAll of this seems designed to make the hospital more labor efficient. None of this seems designed to improve long term outcomes for patients. My continuing suspicion that this technology gets the hype it does as part of an effort to reduce wages for all workers grows.