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

标签：#open

找到 2882 篇相关文章

开源项目

🔥 didilili / ai-agents-from-zero - 🚀 2026 最系统的 AI Agent 速成指南｜智能体实战教程 · 完整学习路径 + 实战项目 + 面试题库 · 对

GitHub热门项目 | 🚀 2026 最系统的 AI Agent 速成指南｜智能体实战教程 · 完整学习路径 + 实战项目 + 面试题库 · 对标大模型应用开发工程师岗位 · 覆盖LangChain / LangGraph / Coze / Dify / MCP / skills / LLM / RAG / 提示词 · 企业级部署与微调 · 从0到企业级落地 + 从学习到上线项目 + 面试准备一体化 | Stars: 3,439 | 43 stars today | 语言: Python

2026-08-05 原文 →
AI 资讯

Is the future of AI local?

Is the Future of Enterprise AI Local? For the past couple of years, the standard approach to AI has been pure brute force: take the biggest, most expensive cloud-hosted frontier model you can get hold of and throw it at every single problem. But this "one-size-fits-all" approach is not going to last forever. We are approaching a transition phase where the capabilities of local models will soon pass the threshold of "good enough," just as the growing costs of frontier models become impossible for businesses to ignore. Here is why I believe the pendulum is about to swing firmly toward local, controlled hardware. 1. The Looming API Cost vs. Value Reality Check Right now, companies are actively encouraging their staff to jump on the AI bandwagon. But this honeymoon phase will eventually hit a wall. In the near future, businesses are going to start heavily scrutinising the cost-versus-reward ratio of their AI deployments. Consider the typical enterprise token burn: If an engineer is burning through £10,000 worth of tokens each month on API calls, are they actually adding £10,000 worth of value? Or have they just established an expensive new habit to climb the internal AI usage leaderboard? When CFOs eventually demand budget cuts, teams relying entirely on cloud APIs are going to be forced to unlearn those expensive habits overnight, or find alternative options. Beyond raw cost, cloud providers will likely continue introducing workflow friction. We've already seen instances where providers shrink token allowances, enforce dynamic rate-limiting based on the time of day, or push traffic to lower-tier models during peak utilisation. Building your core workflows on a third-party API means you will never truly control the throttle. This is not even considering the data ownership issue, up until now the only powerful models were closed weight and there was not much choice in ownership, however now that open weight models are available that can offer similar performance and can

2026-08-05 原文 →
AI 资讯

From Snoring to Science: Fine-Tuning OpenAI Whisper for Sleep Apnea (OSA) Screening

Is your snoring just a nuisance, or is it a health warning? Obstructive Sleep Apnea (OSA) affects nearly 1 billion people worldwide, yet most remain undiagnosed due to the high cost of clinical polysomnography. Today, we are pushing the boundaries of AI Healthcare by repurposing OpenAI Whisper from a speech-to-text powerhouse into a clinical screening tool. In this tutorial, we will explore how to leverage Audio Signal Processing , Hugging Face Transformers , and Librosa to detect breathing patterns. By fine-tuning Whisper on non-speech acoustic events, we can transform a standard smartphone recording into a high-precision OSA screening device. Pro-Tip : If you're looking for more production-ready examples and advanced architectural patterns for AI-driven health monitoring, be sure to check out the deep-dives over at WellAlly Tech Blog . The Architecture: From Raw Audio to Clinical Insight To build an OSA screening algorithm, we don't just need to hear the sounds; we need to understand the rhythm and absence of sound. We use Whisper's robust encoder to capture the spectral features and a custom classification head to identify Apnea-Hypopnea events. graph TD A[Raw Sleep Audio .wav] --> B[Preprocessing: Librosa] B --> C[Noise Reduction & VAD] C --> D[Segmenting: 30s Windows] D --> E[OpenAI Whisper Encoder] E --> F{Event Classification} F -->|Normal| G[Healthy Breathing] F -->|Snore| H[Snore Phase Analysis] F -->|Silence/Choke| I[Apnea Event Detected] I --> J[AHI Index Calculation] J --> K[Final OSA Risk Report] Prerequisites To follow this advanced guide, you'll need: Tech Stack : Python 3.9+, transformers , librosa , torch , and evaluate . Dataset : Ideally, the UCD Snore Database or similar PSG-synchronized audio data. Step 1: Audio Preprocessing with Librosa Before feeding audio into Whisper, we need to clean the signal. Sleep environments are noisy (fans, traffic, etc.). We use librosa to normalize the audio and detect "Voice" (or in our case, Breath) Activity. im

2026-08-05 原文 →
← 上一页 下一页 →