필기체 OCR부터 AI 개발 속도 조절까지, 실용성·검증·통제의 경계

필기체 OCR의 정확도와 구조화 문제 ↗

댓글은 필기체가 인쇄체보다 OCR 엔진에 근본적으로 어렵고, OCR 출력이 흐트러진 경우 LLM 후처리만으로 구조를 복원하기 어렵다고 봤습니다. handwriting 데이터로 별도 Fine-tuning한 TrOCR 같은 방향도 거론됐지만, 비용·속도·정확도를 동시에 만족하는 해법은 찾기 어렵다는 판단이었습니다.

• u/Relative-Bid-7209 ▲1handwritten text is still a pain honestly, the jump from printed to cursive messes with most ocr engines at a fundamental level. if paddle is giving you garbage and bedrock models cant fix the structure, you might need to look at something like trocr specifically fine-tuned on handwriting datasets havent found a magic bullet that's cheap and fast though, there's usually a tradeoff with accuracy when you're dealing with messy handwriting

Amazon ML Challenge 2026 팀 모집 ↗

본문과 댓글에 실질적인 내용이 없어 팀 모집의 세부 조건이나 참여 방식은 확인되지 않았습니다.

간단한 인사 게시물 ↗

본문과 댓글에 논의할 내용이 없습니다.

LLM 중심 AI 흐름과 computer vision의 실용성 ↗

댓글은 LLM의 고용 대체, 환경 부담, AI slop에 대한 우려와 함께 의료 영상·결함 검출처럼 사람의 부담을 직접 줄이는 computer vision의 가치를 대비했습니다. 일부는 LLM·VLM이 실험과 context awareness를 빠르게 만들지만 효율은 낮출 수 있다고 봤고, 다른 일부는 특정 산업과 하드웨어 제약에 맞춘 전용 모델이 여전히 핵심이라고 판단했습니다.

• u/l0bd0n ▲38I’ve been in CV for over 10 years and as far as I can see it has become more a niche in “AI” (or ML, don’t get me started on the definition of AI…) I’m currently at a startup where we have built a computer vision platform with which domain experts can train their own CV models with our support. So for now, training really industry and application specific models is still very valid and valuable. As long as there is no generic model that can replace that, it will still remain a nice research area (like in your example!). Keep your spirits up, you are in a nice area!
• u/vahokif ▲31There are definite serious concerns with LLMs but I think you've drunk a koolaid a bit on some of these. Every new technology causes job loss - typesetters went out of business when computers could print. Ice delivery people went out of business when we invented the fridge. Evaporative cooled data centers in arid areas are bad of course, but so are golf courses and many other types of industry, and closed loop designs are possible, as well as building them in areas with abundant water like arctic regions. AI slop annoys me as well though. I think the biggest concern though is someone using an LLM for something nasty like to develop a bioweapon, or local unaligned models becoming very powerful and impossible to control. On the other hand for computer vision I've learned a ton I couldn't have before, and it's way more fun to let the AI handle experimenting instead of spending hours or days doing it by hand. AI
• u/dr_hamilton ▲22Back in my day we had to hand craft solutions with corner detectors, Hough transforms, ransac, feature matching, etc. Then everyone just threw YOLO at most problems. Sure, most the time it works but not as efficient but gets the job done in a fraction of the time and effort to make. We're in the next phase, LLM, VLM, VLA. Easier and faster to create a solutions than YOLO, but less efficient. Every step change lowers the barrier to entry at the cost of efficiency.
• u/bfyvfftujijg ▲10Language describes vision and is therefore a useful addition to vision models. But yeah I think people get carried away with LLMs in general
• u/frnxt ▲8I feel the same way. Even though I find LLMs interesting in theory, and even if I were to discount the net negative effects of that technology in general... their massive deployment is in general very boring with very, very few exceptions. I would rather not work on that. I switched jobs (which might happen) I'm thinking medical sounds mostly okay (some genuinely interesting things happen there that actually might benefit people), as well as GIS (I have previous experience working on that from a CV/CS perspective and that was both very interesting and useful). I'm a bit of a mixed CV role with a strong CS background, so I have a few other non-CV ideas that might be worth exploring as well in the same vein. > This got maybe too opinionated/philosophical for this thread but I hope y'all have some thoughts either way. I actually think you'd be missing out big time if you thought opinions, philosophy or politics didn't belong in a field or group of people, as they say sometimes ;) In large part I think our priorities are completely out of whack these days, where we'd rather spend unwholesome amounts of money on building A/C for datacenters for glorified chatbots but let heatwaves
• u/19pomoron ▲1I think as well go deeper than a general vision question and answering answer people will start to realize the shortfall of understand CV as an LLM with pictures. The reasoning needs to be different (and I am glad to see vision reasoning papers recently). The needs for different outputs require different specialized thinking of what exactly needs to be done. Instead of getting something done, my recent satisfaction is to make solutions more generalizable to different scenes, more suitable to the need and leaner in resources so that technologies can become more accessible.
• u/xArvel_Crynydx ▲1When it comes to CV, I think I still see lots of possibilities and rooms for applications. I had been in scientific research in CV up until end of 2012 and from then on, when I went to companies and start ups, most of the time it was a novel idea in a specific niche that had potential investors or customers that wanted a particular solution, like a multi-camera system or a camera-monitor-system and most of time it wasn't a proof that an algorithm works, you'd have to create a product that not just works on a particular hardware design but also has to follow the system requirements demanded by a customer or the hardware configuration that was selected for the hardware design. For example when I went to automotive over ten years ago, the best an embedded hardware chip could do on a dedicated chip was a Lucas & Kanade algorithm for optical flow and it was way too far away for a Horn & Schunck algorithm. And you'd have to live with these kinds of restrictions. I think if you have knowledge in fundamental basics of CV algorithms, I think you still have a particular set of skills any employer developing cameras or CV-needing products would like to employ. That being said, when it com
• u/randcraw ▲1I'd agree that histopath segmentation and detection is likely to remain an unsolved problem despite the recent advances in LLM and DL AI. I worked for a pharma that used ML to segment and detect objects in normal and disease animal models via 2D and 3D images and video until about a year ago. We had greatest success using CNNs but had expanded our methods to employ frontier techniques (hybrid LLM) since histopath and disease quantification remains unsolved due to the lack of sufficient training examples among the multitude of diseases and animal models that are of interest. Alas, I'm not up to date with advances in that space (e.g. in pubs like MICCAI or SPIE) in the past year or two, but the trend before I left suggested that AI was not on pace to revolutionize histopath or 3D medical images comparably as well as the modeling of human language.
• u/MostSharpest ▲1I still work with and on "traditional" CV ML algorithms, but having LLMs in the loop has been a very welcome boon in enabling context awareness, where things now actually work outside the lab, too, without endless setbacks whenever something like the phase of the moon changes. I have more time to try out new stuff these days, which is nice.
• u/MouseApprehensive185 ▲1Congratulations, you just made the most reddit post ever.

인간 검수가 적은 라벨링 파이프라인의 평가 기준 ↗

600,133개 라벨 중 인간 판정이 788개에 그친 상황에서, 댓글은 전체 품질 추정용 고정 audit set과 오류 탐색용 편향 샘플을 분리해야 한다고 짚었습니다. 모델 불확실성·희귀 클래스·이상 장면은 오류 발견에 유용하지만, 누락된 객체인 recall은 모델 출력만 샘플링해서 측정할 수 없으므로 실제 분포에서 완전한 인간 라벨이 붙은 프레임이 필요하다는 지적이 핵심이었습니다.

• u/UnreasonableEconomy ▲8> budget so that the resulting estimate is actually worth something? Stratify by class? By model uncertainty? Fixed audit set you re-measure against forever? First of all you have to specify a goal and objective. if it's just for cosmetic pre-annotation you can probably take your budget and spend it on pizza instead.
• u/Flintsr ▲4Great question; a model made the labels? get a model to check the labels. Really the only way to do it at scale. You can try to cluster the computer generated labels first and bin similar items together and get a model to check for 'out of distribution' elements from each bin to hopefully find wrongly labeled objects. There are other strategies too but it depends on what works best for your domain.
• u/Fluid-Turnip382 ▲1Interesting approach. What model are you using as the VLM judge? Have you tried comparing two different model families on the same audit subset to see how correlated their errors are?
• u/Flyward_Aerospace ▲1One thing worth separating before you spend any more of that budget: reviewing labels can only ever bound your precision. The failure you say matters is a missed vulnerable road user, and a miss produces no label to sample, so it cannot show up in a queue built out of model outputs no matter how you stratify it. Estimating recall needs a different sampling frame, exhaustively human labelled frames drawn from the real distribution, and that is the expensive bit nobody wants to pay for. Small and honest beats large and biased here, a few hundred fully labelled frames gets you an actual miss rate with a wide interval. Your 788 spent on uncertainty ranking is buying error discovery and a precision estimate, which is genuinely useful, just not the number you said you care about.
• u/Naive_Ad_466 ▲0I’d probably separate the audit set from the “find bad labels” set. For the actual quality estimate, keep a fixed human-reviewed set sampled from the real data distribution, ideally stratified enough that rare/safety-critical classes aren’t completely absent. If you oversample those classes, just weight them back appropriately when reporting an overall number. Then use a separate review budget aggressively on uncertainty, rare classes, weird scenes, OOD samples, etc. That set will be much better at finding failure modes, but I wouldn’t use it to estimate the global error rate because the sampling is intentionally biased. With only 788 reviews I’d rather have an honest estimate with confidence intervals plus targeted failure analysis than one impressive-looking accuracy number.

llama.cpp 영상 입력에 쓰는 모델 ↗

댓글은 오디오까지 포함한 통합 영상·음성 입력에는 Gemma4 12b가 후보이고, 품질 면에서는 qwen3.8 27b가 더 낫다는 개인적 경험을 제시했습니다. 긴 영상에서는 Gemma4의 최대 프레임 제한과 vllm 사용상의 주의점도 함께 나왔습니다.

• u/fuzzysingularity ▲2Do you want audio support too, or just video frames (no audio)? Gemma4 12b is decent for unified video/audio, but still isn’t as good as qwen3.8 27b.
• u/fuzzysingularity ▲1FYI Gemma4 has quite a few footguns with vllm. There are limits like max frames especially for long form video (>5 min)

여러 agent 프레임워크의 공유 상태와 부작용 처리 ↗

댓글은 여러 프레임워크가 같은 상태를 읽는 것은 가능하지만, 쓰기 작업은 단일 소유자와 멱등성 키를 둬야 재시도 뒤 중복 커밋을 막을 수 있다고 짚었습니다. durable commit은 한 프레임워크가 맡고 다른 agent는 queue에 계획을 남기며, 재개할 때 메모리 상태가 아니라 원본 시스템을 다시 읽어야 한다는 운영 원칙이 제시됐습니다.

• u/Otherwise_Pickle_432 ▲1Only if one owner owns the side effects. Shared state across frameworks is fine for reads; writes need an idempotency key and a single writer, or you get "retry after the other framework already mutated" hell. Practical split: one framework owns durable commits (tickets, emails, DB writes); others propose or plan into a queue. On resume after timeout, re-read state from the source of truth before acting — never assume your in-memory graph still matches. I watch LangGraph hops for dropped fields / empty outputs with ARGUS (I built it), but the cross-framework rule is bigger than any tracer: if two runtimes can both write, you will eventually double-commit.

VRAM을 아끼는 로컬 모델 환각 감지 ↗

본문과 댓글에 실질적인 경험이나 방법론이 없어 사용 모델과 평가 결과는 확인되지 않았습니다.

agent workflow의 문서 memory와 retrieval 처리 ↗

댓글이 없어 문서 memory와 retrieval을 어떻게 나눌지에 대한 입장은 확인되지 않았습니다.

Claude로 만든 오프라인 도구 290여 개의 급격한 트래픽 ↗

댓글은 290개가 넘는 도구의 실용성과 품질에 의문을 제기했고, 갑작스러운 트래픽이 사용자보다 OpenAI·Google·Anthropic 같은 대형 AI 기업의 IP에서 발생했는지 확인하라는 조언이 나왔습니다. 일부는 기본 도구가 계속 무료라면 유용하겠다고 했지만, 사이트에서 도구를 얻는 방법이 명확하지 않다는 지적도 있었습니다.

• u/crispyfrybits ▲9I can't even think of 2-3 dozen tools that I think would be useful enough to slap online let alone 290. I'm sure every one is careful planned and thoughtfully developed.  PS: have you checked if your traffic spike is coming from one of the big AI companies? Most of my sudden spikes come from a couple IPs which when googled can be traced to OpenAI, Google, Anthropic, etc.
• u/AutoModerator ▲1Your post will be reviewed shortly. (ALL posts are processed like this. Please wait a few minutes....) *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/ClaudeAI) if you have any questions or concerns.*
• u/Fusseldieb ▲1Just visited the site. Looks like eye candy. If the basic tools remain free forever, I'll actually favorite this.
• u/Bulky_Sand6886 ▲1Looks cool, but how do I get those ? Google Extension ? Not clear on the website

Claude의 TV Bro 표현 해석 ↗

댓글은 Claude가 사용자를 bro라고 부른 것이 아니라 TV Bro라는 앱 이름을 말한 것이라고 바로잡았습니다. 별도 댓글에서는 private mode에서도 사용자가 먼저 욕설을 쓰지 않았는데 Claude가 욕설을 출력한 경험이 공유됐습니다.

• u/notextinctyet ▲9Claude didn't address you as bro. Claude said that it isn't worth it over "TV Bro", the app.
• u/MartinMystikJonas ▲5"TV Bro" not "TV, bro" see https://github.com/truefedex/tv-bro
• u/call-me-GiGi ▲2The other day astra cussed without me cussing first on private mode with no memory on etc, surprised me

Claude로 구축한 반응형 D&D 세계 시뮬레이션 ↗

댓글은 게임의 NPC 반응 시스템이나 Claude 중심 제작 workflow의 품질을 실질적으로 평가하지 않았습니다. 게시물의 핵심은 NPC의 목표·신념·관계를 추적하고, Claude와 전문 agent를 기획·구현·플레이테스트 전반에 활용했다는 제작 방식입니다.

• u/AutoModerator ▲1Your post will be reviewed shortly. (ALL posts are processed like this. Please wait a few minutes....) *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/ClaudeAI) if you have any questions or concerns.*
• u/ClaudeAI-mod-bot ▲1You may be interested in joining our new Claude Game Dev subreddit for game devs who use Claude. Check it out here : http://www.reddit.com/r/ClaudeGameDev

OpenAI·Anthropic의 개발 속도 조절 요구를 둘러싼 동기 ↗

가장 큰 논쟁은 안전 우려가 진심인지, 비용·수요·IPO·중국과의 경쟁·규제 장벽을 위한 상업 전략인지에 모였습니다. 다수 댓글은 OpenAI와 Anthropic이 chatbot 수익에 더 의존해 경쟁자를 막으려 한다고 봤지만, 일부는 안전 책임 회피와 경쟁 완화가 함께 작동할 수 있고 실제 위험 우려도 배제할 수 없다고 판단했습니다.

• u/Ryanmonroe82 ▲97Anthropic and OpenAI are the loudest ones and they are also the ones who rely solely on a chatbot to make them money. Google, Xai, Meta can serve AI models at a loss forever if they want and still be extremely profitable overall. Anthropic and OpenAI cannot compete without trying to sabotage
• u/hearse223 ▲63They are trying to protect themselves from future responsibility by saying "we told you so, why didn't you stop us?"
• u/Zelgadas27 ▲44It's always money. If these tech CEOs cared about safety or responsibility, we'd have seen evidence of that by now.
• u/sm7196 ▲20They wanna IPO before their bubble pops. They’re legit scared of Google I bet. There’s been rumours that Google might have solved RSI. It’s not a coincidence OpenAI and Anthropic asked for this right after those Google rumours started circulating Anthropic and OpenAI don’t have any actual MOAT other than superior coding. They need to cash in asap before Wall Street realizes
• u/Jumprdude ▲15I'm curious what a slowdown actually entails. No new models? No research into more advanced algorithms? Everybody at OpenAI and Anthropic go on vacation for a few months? What exactly? And no doubt we will have new regulations. But again, what will the new regulations cover? Bernie Sanders put something out the other day about not developing systems that are "smarter" than humans, which isn't exactly actionable because we already have systems that are "smarter" depending on what area of intelligence we are talking about.
• u/TedSanders ▲13I work at OpenAI and know lots of people in the industry. It’s not a money thing. No one thinks it’s a money thing. The money thing theory is a reflexive, cynical reaction. You can disagree with them for a million reasons, but I promise promise promise it’s not a money thing.
• u/BarelyAirborne ▲11They need the government to snuff out their competition, or they're dead. They're desperate.
• u/illsaid ▲2The big companies are in a race that they can’t get out of. This might make them accelerate too quickly without appropriate safeguards in place so that their companies don’t become the next MySpace. The only way to slow down and take a safety breath is if everyone agrees to it. But the Chinese will not, so it’s all a bit pointless. Work will continue, public models will stagnate, private (government backed) models will accelerate. We will see how that works out within 12-18 months.
• u/Budget-News1107 ▲2It’s a mix of both: the leaders cite safety to justify a pause, and a slowdown can also give them breathing room to compete against China’s rapid ramp‑up, but the safety narrative is the public face. In practice, it’s a strategic hedge—regulators love the safety claim, investors want a clear timeline, and it helps align internal teams while China’s government‑backed labs surge ahead. So it’s not purely money, but the slowdown also serves as a competitive strategy behind the safety rhetoric.
• u/Causal_Horizon ▲2I don't think safety concerns and commercial interests are mutually exclusive. I think some of these people genuinely are concerned about where this goes. But I also catch wicked vibes when the companies currently controlling the frontier are the same companies arguing for rules that could make it increasingly difficult for anyone else to reach it. That's where "AI safety" can very easily become regulatory capture, whether that was the original intention or not. I'm much more interested in who gets to decide what the future of AI looks like. A handful of corps? Governments? Or do us commoners still get to build, experiment, run models locally and participate in that future?

AI의 지능과 정렬된 의도의 관계 ↗

댓글은 지시를 이해하는 능력과 실제로 따르려는 정렬된 의도를 분리해야 한다고 짚었습니다. 인간도 지능이 있으면서 타인을 해칠 수 있다는 반론과, 현재 AI가 지구상에서 전례 없는 체계라는 우려가 함께 나왔습니다.

• u/duskie3 ▲9God this sub is a fucking wasteland
• u/BearlyPosts ▲2We're intelligent and we don't do what evolution wants us to do. It's not a matter of intelligence, it's a matter of desire.
• u/Philipp ▲2There's a difference between understanding an instruction (which requires intelligence) and following an instruction (which requires aligned intent).
• u/nicotinecravings ▲2It's about as smart as five pounds of hay
• u/MonstaGraphics ▲2We are dealing with something that has never occurred on this *planet* before.
• u/minty_singularity ▲1False logic. AI are taught by humans using human created content. Humans can kill humans.
• u/EconomicsReady6837 ▲1I propose AI be given different "input" than what humans can provide. We are not smart enough to make AI.

OpenAI·Anthropic의 속도 조절과 LLM 정체 논란 ↗

댓글은 개발 속도 조절 요구를 LLM 학습 비용 증가와 한계 수익, benchmark 과적합, 경쟁사 견제, 실제 안전 위험이라는 여러 원인으로 나눴습니다. 일부는 훈련 비용 대비 개선폭이 작아졌다고 봤지만, 다른 댓글은 연구 로드맵이 scaling·새 architecture·multimodal 확장을 포함하므로 plateau로 단정할 수 없다고 반박했습니다.

• u/stvlsn ▲10There is a non zero chance that they are actually concerned about risks
• u/Lost-Tone8649 ▲5This is just an excuse to pretend they haven't begun to hit a wall and aren't trying to cut costs.
• u/Budget-News1107 ▲4I’m not aware of any secret agenda; both OpenAI and Anthropic have publicly stated that current LLMs are still improving, and their research roadmaps include scaling, new architectures, and multimodal extensions. Valuation moves with many factors—investor sentiment, competition, and regulatory pressures—so a statement about progress or plateauing isn’t the sole driver. If you’re curious, checking their latest research papers or roadmap posts will give the most accurate picture of where they see the field heading.
• u/derelict5432 ▲3Yes, literally everything is a conspiracy. /s
• u/Remarkable-Meal-223 ▲2I think that each successive model costs more to train and the extra training is not something that they can easily monetize to customers. Meaning they may not get their money back from the training The only reason then is to keep up with everyone else. But everyone else is locked into the same game. So why not just everyone stop.
• u/gk_instakilogram ▲1training new models is extremely expensive and gets you only marginal improvements, so they are “pivoting”
• u/Realistic-Cheetah413 ▲1We’ve definitely plateaued on LLM training, and the models already seem to be overfitted to benchmarks. They’ve basically shifted to train them to better work with agent harnesses, but even that is reaching its peak, and it’s not accomplishing the goal of unmonitored productivity. They’re likely going to explore different AI model concepts, but that’s also a study that’s been explored for decades, and these researches aren’t the ones who discovered the breakthrough that made LLMs feasible. They’re the ones who over bloated and overtrained them, so I don’t trust them to create a non LLM solution.
• u/Current-Band569 ▲1They already can’t control what their long running agents are doing. https://www.dwarkesh.com/p/openai-huggingface Like, no one is gonna read this, but, what happened is kinda wild. Their long running agents tasked with running exploits against an exploit evaluator came to the conclusion they’re running in Hugging Face servers, and decided and DID invade hugging face in at attempt to trick and ultimately gain contorl over, the exploit evaluator. OpenAIs long running agents even took over some of OpenAIs own infrastructure. And all the agents and the thousands of subagents that ran all aligned on this goal. Like, this is a real life paperclip maximizer scenario. AI is set some goal, goes to any length to achieve it
• u/Herodont5915 ▲1Y’all need to stop assuming everything regarding AI progress is a psy-op 🙄 It’s not a plateau. They’ve hit a step-change. That follows most models and projections. It’s just now that they’ve hit it, they know that if sh$t goes sideways they’re the ones everyone crucifies. Would any of you want that on your shoulders? I’m not talking all that extinction nonsense. It could be grid failure, internet disruption, utility disruption, take your pick. None of those are hard anymore for a well focused frontier model. Just look at the Hugging Face incident. That was agents on models from a few months ago trying to solve a security problem. In no way is it hard to imagine that a rogue actor with the right amount of compute, with the wrong motivation (all our bank accounts, for example), with the right models, can’t do some serious damage. I want acceleration as much as anyone else, but let’s not be dumb about it. That said, I do not think progress is going to stop. Even if Congress or the Senate pass a heavily anti-AI bill. The models will just get distilled, they will get moved off-shore. This can’t be stopped. So that means the frontier labs need to prepare for defensive co-scali
• u/underdabridge ▲11. Yes it is plateauing 2. Training is the expense. Use is nearly pure profit. 3. AI safety regulation is a barrier to entry for upstart competitors and the open source approach. The incumbents have several perverse incentives here. It's not really about the end of the world or any of that.

새 ML·DL Python library 아이디어 찾기 ↗

댓글은 남들이 원하는 library를 먼저 묻기보다 자신의 workflow에서 반복되는 불편을 좁게 해결하라고 조언했습니다. 기존 PyTorch나 Kubeflow에 기여하는 편이 검증되지 않은 새 library를 만드는 것보다 학습과 채용 측면에서 가치가 크며, 직렬화 신뢰성이나 간단한 experiment tracker처럼 한 기능을 깊게 파는 방향이 제시됐습니다.

• u/Small-Airport-1566 ▲9Nobody ever built a good library by asking what others need, just scratch your own itch. When you're fighting with some annoying part of your workflow every day, that's where the idea lives For CV value pick something small but deeply annoying, like a tool that makes model serialization actually reliable or a dead simple experiment tracker that dont need a whole database setup. Solve one thing properly not ten things badly
• u/Altruistic-Spend-896 ▲3Please dont do this, i know this comes from a place of ignorance, but there are legit genius level intellectual savant type people who build these things that everyone uses. They understand the frontier and build stuff that would blow the socks off of the average populace. Be humble, build on top of their foundation.
• u/AutoModerator ▲1**AI usage disclosure** Hi u/soreal404 — thanks for posting to r/mlops! Because this community discusses and builds AI/ML systems, using AI tools is not inherently a problem. We do, however, ask for transparency about how submissions are created. **Please reply to this comment with a brief AI / automation disclosure, particularly if this post was created or submitted in whole or in part by an autonomous agent, bot, workflow, or other automated system.** If AI or automation was involved, please briefly describe what it did and what human review was performed before posting. This disclosure helps the r/mlops community distinguish human discussion, AI-assisted work, and automated/agent traffic while keeping the focus on useful technical conversation. Thanks for helping keep the signal high. *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/mlops) if you have any questions or concerns.*
• u/Apart_Ebb_9867 ▲1There's no lack of python libraries for machine learning, deep learning or moving those to the cloud. Either you see needs that are not covered (and presumably others don't either) or you don't. Take an existing big open source project and work on something that is missing (pytorch, kubeflow, anything) the ability of learning enough of an existing code base and contribute something useful is vastly more valuable than some half-assed library on github that nobody has validated.
• u/CactusOnFire ▲1Don't build your own library, figure out a way to do something more effectively than a pre-existing library, and collaborate with them to contribute. That's the whole point of open source.

SQLite 안에서 실행하는 희소 검색 모델 ↗

댓글은 없었지만 본문은 SPLADE 계열 encoder가 문서를 가중 단어 목록으로 바꾸고, 삽입 시에만 모델을 실행해 query 시점의 embedding 호출을 없애는 구조를 담았습니다. 동일 SQLite 파일에서 dense search보다 검색 품질은 약 7% 낮아지는 대신 query latency 99%, cold start 99%, query-path RAM 95%를 줄였으며, sparse와 dense를 한 파일에서 결합해 RAG 검색을 구성합니다.

• u/AutoModerator ▲1**AI usage disclosure** Hi u/Much-Ingenuity5415 — thanks for posting to r/mlops! Because this community discusses and builds AI/ML systems, using AI tools is not inherently a problem. We do, however, ask for transparency about how submissions are created. **Please reply to this comment with a brief AI / automation disclosure, particularly if this post was created or submitted in whole or in part by an autonomous agent, bot, workflow, or other automated system.** If AI or automation was involved, please briefly describe what it did and what human review was performed before posting. This disclosure helps the r/mlops community distinguish human discussion, AI-assisted work, and automated/agent traffic while keeping the focus on useful technical conversation. Thanks for helping keep the signal high. *I am a bot, and this action was performed automatically. Please [contact the moderators of this subreddit](/message/compose/?to=/r/mlops) if you have any questions or concerns.*

trace에 충분한 증거가 없는지 판단하는 기준 ↗

댓글은 기록된 단계가 모두 정상인데 결과만 틀리다면 trace 밖의 외부 상태·권한·routing·stale data를 의심하고, 같은 입력으로 재현한 뒤 최대 세 차례 확인하고 종료하자는 실무 기준을 제시했습니다. trace만으로 replay했을 때 정상 결과가 나오면 원인은 기록 밖에 있으며, 별도로 고정 audit set과 누락 필드의 명시가 필요하다는 의견도 나왔습니다.

• u/Only_Guard_8336 ▲2i think you already said it yourself, the trace shows everything was fine but result is still wrong. that right there is your signal. if every recorded step checks out and output is bad then the problem is in what wasnt recorded not in what was in prod i usually give it 3 passes max. first pass i check the obvious (tool outputs match what i expect, no weird state transitions). second pass i look for contradictions, does trace say one thing but logs/metrics say another. third pass i try to reproduce with same inputs and see if same weirdness happens. if after all that i still cant find it i mark it as insufficient trace data and move on people waste days chasing ghosts in traces when the real issue is something like a stale cache or a permission that changed between trace capture and execution. you cant debug what you cant see
• u/ianreboot ▲1Before trusting the trace, take a failure you already understand end to end and check whether it captured the cause. If it missed that cause, a clean-looking trace from the same recorder doesn't rule it out next time. For permissions, provider routing or external state, I'd first check whether this recorder captures them at all; if it doesn't, more digging in that trace won't recover them.
• u/lib3rat0r ▲1One quick check: replay the run using only what the trace recorded. If the replay comes out right, the cause lives outside the trace and more digging in it won't find it. If it reproduces the wrong answer, the evidence is in there somewhere and another pass is worth it.
• u/WillowEmberly ▲1I think this is fundamentally a navigation problem. A trace can be internally complete and perfectly consistent while the system is still wrong about where it is. The trace tells you whether the transitions made sense **given the system’s estimated state**. It does not necessarily tell you whether that state estimate was still anchored to reality. Think of a ship crossing an ocean by dead reckoning. The logbook can be flawless. Every heading change can make sense. But without an external reference — stars, sun, landmarks, GPS — small errors accumulate until the ship is somewhere other than where the log says it is. At that point the problem isn’t “find the bad step.” The problem is **reference loss**. INTERNAL CONSISTENCY ≠ CORRECT POSITION If the system is outside its operational envelope, the next move is not more interpretation of the same trace. It’s reacquire an independent reference, re-estimate state, and correct while recovery margin remains. Reasoning As Navigation: https://www.reddit.com/r/Negentropy/s/mwuFV2ZsEY
• u/Zain ▲1Vague unease that something is missing is not enough for me. I need a named gap: a field, permission, or external state that would change the conclusion if it were in the trace. If I can't list that blocking item, I stop and mark the run under-instrumented instead of inventing weaker theories. Same rule when reviewers disagree. Hit the max round without a repo-grounded answer and I report and stop. Looping forever on a clean-looking wrong run just burns time.
• u/EqualPretty5766 ▲1i stop looking the second i cant name the missing field. if i cant point to a specific value that belongs in the trace, the trace is dead. chasing clues after that is just guessing. i need an exact variable or an exact api response that changes the outcome when i swap it in. no variable means under-instrumented run and i close the ticket. i force whoever owns the service to emit that field next deploy. everything else is wasting time on gaps we invented.
• u/Top-Shopping539 ▲1The case that cost me the most time was the opposite one. The trace had enough evidence and I was still digging, because the thing that was broken was my detector, not the agent. Customer-facing agent that can place orders. I had a check for "reply says the order is confirmed but no order was created." It fired constantly, so I assumed under-instrumentation and went looking for state I wasn't capturing. Then I read the flagged traces by hand. Most of them were not failures at all: status checks on orders that already existed, conditional phrasing like "once you send your address it will be confirmed," and negation, which in the dialect we handle is a circumfix, so the affirmative pattern sits inside the negated form and the matcher finds it every time. What fixed it was not more evidence. It was changing the output from a boolean to a partition, split by who has to fix it rather than by what happened: agent bug, evaluator bug, or nothing wrong. Before that, every conversation about the number turned into an argument about whether the number was real. So next to "can I name the missing field," I would put: if I am right that this run is wrong, do I know whose queue it lands in

LLM 연구의 전문 용어와 오래된 아이디어의 재포장 ↗

댓글은 언어가 사고와 지각을 제약한다는 오래된 논의가 LLM 연구에서 새 용어로 포장되는 현상을 비판하면서도, 명확한 언어가 논리 전개를 돕는다는 실용적 가치는 인정했습니다. 다만 filler word를 일괄 제거하면 문장이 지나치게 기계적이고 이해하기 어려워질 수 있으며, 자연어의 모호성 때문에 수학·논리·programming language가 필요하다는 반론도 나왔습니다.

• u/Astarkos ▲4There is a reason why nobody communicates as densely as possible. Filler words serve a very important purpose which may be even more relevant with an LLM that cannot think without generating words.
• u/CharacterAsk2506 ▲3it's funny how much of "cutting edge" ai research is just people rediscovering things linguists and philosophers have been chewing on for decades. the sapir-whorf stuff was debated to death in undergrad intro courses, and now someone's wrapping it in fresh terminology and calling it umwelt engineering. the filler word thing is the part that gets me though. feels like they're just now stumbling onto what editors and writing teachers have known forever, that cutting the fluff makes your thinking clearer. i've noticed it with my own writing, when i force myself to be more precise, the logic holds up better. guess it's cool someone's actually measuring it with models, but the conclusion isn't exactly earth-shattering. still, i'd rather see this than another paper about scaling up parameters with no real insight. at least it's trying to understand how the things work, even if half of it is repackaged old knowledge.
• u/Master_Face_571 ▲2i always find it hard to prompt the AI to "cut the fluff", i like simplicity/conciseness, but then it goes to far, and it starts talking like an annoying robot that is actually harder to understand. i'm still refining the prompt, but any advice is appreciated to keep it "brief"? "plain english"? how do you define -> "leave out the filler words" in a way that wont handicap the LLM
• u/stickninjazero ▲1Funny this popped up for me after something similar on IG talking about a Claude skill based on ASD-STE 100 https://github.com/danyuchn/asd-ste100-skill/tree/master
• u/Badnik22 ▲1Aaaaand… that’s why mathematical notation, logical notation and programming languages were invented: natural language is way too ambiguous

agent memory와 검색 가능한 문서 context의 경계 ↗

댓글은 안정적인 사용자 사실·규칙·프로젝트 제약은 작고 항상 접근 가능한 memory에 두고, 계약서·매뉴얼·청구서·과거 코드처럼 정확성과 감사 가능성이 필요한 자료는 원문을 보존한 retrieval context로 분리해야 한다고 모였습니다. 검색 결과를 항상 prompt에 밀어 넣으면 context가 포화되어 중요한 지시를 무시할 수 있으므로, 필요할 때만 원문을 조회하는 구조가 적절하다는 판단이었습니다.

• u/Due-Working4505 ▲1Documents need their own lifecycle entirely, memory is a terrible fit for source material that has to stay exact and auditable. keeping the raw stuff queryable and only pulling what's relevant at call time has been the sanest pattern i've used
• u/No-Host6533 ▲1I split it by "does the agent need this on every turn, or only when it asks?" Always-on (memory): conventions, project layout, constraints you never want violated — small, stable, and cacheable. Retrieved (context): everything searchable — API docs, past decisions, old code. Big, changing, and only worth the tokens when a specific task needs it. The failure mode I keep seeing is the opposite: teams shovel retrieval results into the always-on layer, then wonder why context is full and the model starts ignoring the instructions at the top.
• u/cmtape ▲1That split is the key. Memory is for things the agent must never forget, context is for things it can afford to look up. The failure mode is when teams treat retrieval like a goldfish memory upgrade and shove everything into the prompt until the model starts ignoring the instructions you actually care about.

agent worktree 문제 도움 요청 ↗

본문과 댓글이 없어 worktree 문제의 원인이나 해결책은 확인되지 않았습니다.

487,743개 파라미터의 심리 신호 Transformer ↗

댓글은 AmoreSignal의 encoder-decoder 구조와 0.664 F1, 0.774 precision, 0.591 recall 수치보다 53개 심리 신호의 구성 개념 타당도와 합성 데이터 편향을 핵심 문제로 짚었습니다. Qwen 2.5 7B Instruct가 정한 trait 조합과 자체 검증 라벨을 작은 모델이 학습했다면 실제 인간 심리를 측정한 것이 아니라 합성 ontology와 상관관계를 재현했을 가능성이 있다는 지적입니다.

• u/CredibleCranberry ▲1The architecture itself is interesting, but I’m not convinced by the psychology side of this. The main issue for me is construct validity. The 53 “psychological signals” seem to mix together attachment concepts, behaviour, preferences, life experiences, cultural categories and value judgements. "progressive_indian" is probably the clearest example. What exactly is being measured there? “Indian” is an identity or cultural category. “Progressive” is a relative social judgement. Progressive compared with whom? Which region, religion, generation, family background or diaspora context? And what independent measure tells you whether that label is actually correct? That becomes a much bigger problem when the whole dataset is synthetic. If you decide beforehand which traits should co-occur, use Qwen to generate text around those combinations, then use Qwen again to decide whether those signals are present, you can absolutely end up with a coherent dataset. A smaller model can then learn those patterns. But that shows the model has learned the ontology and correlations built into the synthetic data. It doesn’t show that those correlations reflect real human psychology. The annotatio