今日已更新 362 条资讯 | 累计 38219 条内容
关于我们

标签:#t

找到 18151 篇相关文章

AI 资讯

Is AI CAD the Future Or Is It Already Here?

The Framing Problem When industry analysts discuss "AI CAD," they are frequently conflating two fundamentally different computational paradigms: generative mesh synthesis and parametric feature modeling. This conflation has produced a decade of inflated expectations, underwhelming demos, and a persistent belief that real AI CAD is still "coming." It is not coming. For a specific and technically meaningful definition of AI CAD, it has arrived. Mesh Generation vs. Parametric Modeling: Why the Distinction Is Everything Contemporary generative 3D tools including neural radiance field reconstructions, diffusion-based mesh generators, and implicit surface networks produce geometry as an unstructured point cloud or polygon mesh. These representations are geometrically expressive but engineering-inert. They carry no feature history, no constraint graph, no dimensional intent. A mesh cannot be toleranced. A mesh cannot propagate a design change. A mesh cannot be submitted to a manufacturer without full reconstruction from scratch. Parametric CAD, by contrast, encodes design intent as a structured sequence of operations — extrusions, revolves, fillets, boolean operations each governed by explicit dimensional constraints and parent-child dependency relationships. The parametric model is not merely a shape; it is a design process, replayable, modifiable, and transferable across manufacturing contexts. The meaningful technical question for AI CAD in 2026 is therefore not " can AI generate a 3D shape? " that has been demonstrable since 2019. The question is: can AI generate a valid parametric feature tree from natural language input, with embedded manufacturing constraints, that survives downstream engineering use? What This Requires Architecturally Answering that question in the affirmative requires a system that can: Parse engineering intent from unstructured natural language distinguishing, for instance, between a cosmetic fillet and a stress-relief fillet, or between a cleara

2026-06-05 原文 →
AI 资讯

Looking for ideas how to use AI

Hi, everyone I am working as a Software engineer. The past few years I oversleep a little bit in scope of AI mostly because I am sceptical about it. I decided that I would like to move on and be more up to date with it and potential use of it. How do you use it in day to day habits or work? How to monetize it? submitted by /u/Blvckhype [link] [留言]

2026-06-05 原文 →
AI 资讯

For those doing heavy AI programming or running local models on mobile hardware: Is the current generation of iPhone Pro or Samsung Galaxy Ultra actually making a difference in your workflow, or is it mostly a gimmick right now?

For those doing heavy AI programming or running local models on mobile hardware: Is the current generation of iPhone Pro or Samsung Galaxy Ultra actually making a difference in your workflow, or is it mostly a gimmick right now? submitted by /u/Spirited_Good9789 [link] [留言]

2026-06-05 原文 →
AI 资讯

Steering Vectors: The Hidden Control Knobs Inside Large Language Models

Hello, I'm Shrijith Venkatramana. I'm building git-lrc, an AI code reviewer that runs on every commit. Star Us to help devs discover the project. Do give it a try and share your feedback for improving the product. What if you could change how an AI thinks without retraining it? Not by rewriting prompts. Not by fine-tuning billions of parameters. Not by collecting another mountain of training data. Instead, imagine finding a direction inside the model's internal representation space and nudging the model a little in that direction. A small push. A different behavior. This idea sits at the heart of one of the most fascinating areas of modern AI interpretability: steering vectors . Steering vectors suggest that many behaviors we care about—careful reasoning, honesty, coding style, security awareness, verbosity, and more—may already exist inside a model. The challenge is learning how to activate them. Let's explore what steering vectors are, how they're created, and why they might become one of the most practical tools for controlling AI systems. 1. What Exactly Is a Steering Vector? Large language models process information through layers of high-dimensional activations. At any point during generation, the model's internal state can be represented as a vector containing thousands of numbers. Researchers discovered something surprising: Different behaviors often correspond to different regions of this activation space. For example: Writing Python code Solving math problems Speaking French Explaining concepts carefully Producing insecure code Each tends to produce distinctive activation patterns. A steering vector is essentially the difference between two activation patterns. Suppose we gather examples where the model is: Careful Methodical Thorough and compare them to examples where it is: Rushed Superficial Incomplete The average difference between these internal states becomes a steering vector. At inference time, we can add that vector back into the model's activatio

2026-06-05 原文 →
AI 资讯

I Made a Battery Admit It Was Only 73% Healthy — On-Device, End to End

Voltage lies. Put a battery under load and its terminal voltage sags. Let it rest and the voltage springs back. A naive fuel gauge watching only voltage will happily tell you a worn-out cell is "fine" right up until it falls off a cliff. The number you actually care about — is this battery still good, or is it time to replace it? — isn't in the instantaneous voltage at all. It's in the capacity : how much charge the cell can still deliver between full and empty. That quantity fades as a cell ages. Tracking it is called State of Health (SoH) , and it's the difference between "the device says 80%" and "the device has 80% of the runtime it had when it was new." I wanted my open-source battery SDK ( ibattery-sdk , Apache-2.0) to learn SoH on the device itself — no cloud model, no floating-point, on MCUs with kilobytes of RAM. This post is the story of getting that working end to end: from a coulomb integral in firmware to a faded value showing up live on a Grafana dashboard. The idea: learn capacity from one full→empty trip You don't need a PhD-grade model to estimate usable capacity. You need two anchors and an ammeter. Full anchor — when the cell is at its full-voltage plateau, declare "this is full" and set the coulomb counter to the rated capacity. Discharge — integrate current over time (coulomb counting). Every milliamp-hour that leaves the cell ticks the counter down. Empty anchor — when the cell hits its empty-voltage threshold, look at how much charge actually flowed. A healthy cell delivers close to its rated capacity before going empty. An aged cell hits empty early — it simply has less to give. From the charge measured between those two anchors, you get the cell's real usable capacity, and SoH = measured / rated . The SDK runs it through an integer EMA (so one noisy excursion doesn't whip the estimate around) and a plausibility guard (reject anything outside 30–120% of rated — that's almost certainly a glitch, not a real measurement). The whole thing is inte

2026-06-05 原文 →