我的收藏提交工具
FOXAI SEARCH

全站搜索

新闻报道 211

b12362

The latest release of llama.cpp (b12362) includes optimizations for grammar matching through left factoring, improved handling of character class boundaries, prevention of infinite expansion, and enhanced code clarity with ASCII comments and deduplicated logic. It reverts prior changes related to AST refactoring and alternative limits, while introducing shared immutable rules and removing performance benchmarks. The release supports multiple platforms including macOS, Linux, Windows, Android, and iOS, with various backend options such as CUDA, Vulkan, ROCm, OpenVINO, and SYCL.

翻译服务暂未运行,当前显示原文。
llama.cpp releases

Build a Robot Pick-and-Place Simulation with SimReady Assets

This walkthrough demonstrates how to create a beverage can pick-and-place task using the UR17G robot arm, Robotiq 2F-140 gripper, and a beverage can in Isaac Sim. The process involves downloading SimReady assets from SimReady Central on Hugging Face, assembling the robot and gripper, validating joint and physics settings, and using an AI agent to generate and run control code for the task. The simulation tests grasp accuracy, object stability during movement, and placement precision, with validation reports confirming compliance with SimReady profiles. The workflow supports reuse of validated assets and encourages developers to contribute their own SimReady-compatible robotics content.

翻译服务暂未运行,当前显示原文。
Hugging Face Blog

Route coding agent requests to the right model on Amazon Bedrock with NVIDIA NeMo Switchyard

Coding agents work in tasks, and the number that matters is cost per solved task, not price per token. In this post, you use the AWS CDK to deploy LiteLLM with the NVIDIA NeMo Switchyard routing plugin on Amazon Bedrock, then measure cost per solved task for a routed model group against single-model baselines.

翻译服务暂未运行,当前显示原文。
AWS Machine Learning Blog

Show HN: FieldRook – a local-first Windows troubleshooting workstation

Please have a look at my opensource project FieldRook, here is a short description over it.I am working as a Onsite Technichan in Sweden and i got tired of trying to puzzle togheter different windows-logs and throubleshooting steps to get forward in our tickets, and the logging started to get a real nightmare. Specially to prove for the users why it actually solved the problem and not just giving them a random "Well, it said so in the guide i read"-Type of answer.So I started building a Windowsapp that actually collects diagnostics, traceable observartions, hypothesis and verificiations. AI is a chooseble option and not something that gets direct access to run commands and such.This is a first hand version, it's currently unsigned and needs a much larger field-testing on windowsmachines. I have a hard time testing it inside our work-domain thanks to all of our security policys and such, so have mostly been running it on my local PC at home. If someone would like to have a go at it, please check out the GitHub-repo and download it and give me some feedback on what you liked and not. What worked and not.If other people that work in IT-support actually tried it, do you think it would actually help out in a day-to-day basis? What would you change in it, what is missing and how would you concider the securitymodel at the moment?Thanks in advance! Comments URL: https://news.ycombinator.com/item?id=50495476 Points: 1 # Comments: 0

翻译服务暂未运行,当前显示原文。
Hacker News Show HN

XYBench: Helping with the problem behind the question

XYBench, a benchmark of 8,115 real-world questions spanning programming and everyday tasks, tests AI assistants' ability to recognize and respond to users' misconceptions—such as asking how to thicken frosting when the real issue is warm cupcakes. Developed with researchers from Carnegie Mellon, NVIDIA, and Johns Hopkins, XYBench measures whether models identify underlying goals (X), address them effectively, and steer users away from flawed approaches (Y). Evaluations of models like Claude Sonnet 4.6, GPT-5, Gemini 3.1 Pro, Qwen3.5-9B, and DeepSeek-V4 Pro showed they frequently focused on the stated request rather than the actual goal, with limited success in misconception identification. Human reference answers outperformed all models, highlighting a gap in pragmatic reasoning. The benchmark uses automated and human evaluation to assess pragmatic solution, emphasis, and misconception identification, offering a tool for researchers to improve AI assistants’ ability to provide helpful advice even when users ask the wrong question.

翻译服务暂未运行,当前显示原文。
Hugging Face Blog