注册并分享邀请链接,可获得视频播放与邀请奖励。

与「Relay」相关的搜索结果

Relay 贴吧
一个关键词就是一个贴吧,路径全站唯一。
创建贴吧
用户
未找到
包含 Relay 的内容
Akani Simbine is all about supporting younger athletes 🤝❤️ Having reached the 100m podium twice at the Commonwealth Games, the three-time Olympian and #Paris2024# 4x100m silver medallist explains how important it is for him that younger sprinters have opportunities to compete at the world's biggest stages as well. That's why, at #Glasgow2026# he's only focusing on the 4x100m relay. Are you ready to see him and his team shine today? #RoadToLA28# | @Glasgow_2026 | @WorldAthletics
显示更多
A rare moment when lightning met rocket liftoff. China successfully launched the Tianlian II-06 data relay satellite aboard a Long March 3B rocket from the Xichang Satellite Launch Center on Thursday, placing it into its planned orbit. Moments after liftoff, the rocket triggered a rare bolt of lightning before disappearing into the clouds — a breathtaking sight captured by space enthusiasts and shared with millions online. ⚡🚀 #ChinaSpace# #ChinaTech#
显示更多
No pixels No graphics card No lines of code This is Tennis for Two, created in 1958 at Brookhaven National Laboratory by physicist William Higinbotham To play, you held a custom aluminum box, twisted a knob to dial in your trajectory angle, and slammed a button to hit the ball Inside? An analog computer, vacuum tubes, and clicking electromechanical relays calculating gravity and bounce physics in real time The entire $200B modern gaming industry started as a glowing dot bouncing across an oscilloscope screen
显示更多
0
10
30
2
转发到社区
Caps on, memories unlocked As graduation season arrives at PKU, students return to the campus spots that mean the most to them, sharing stories, reflections, and the moments they'll never forget. From nervous first days to unforgettable final days, this Q&A relay is full of laughter, gratitude, and a little bit of nostalgia. Once a PKUer, always a PKUer ❤️ PKU Graduation 2026 | Produced by He Hongyu, Zhang Xinyi, Liu Jiani, Li Gengyao, Zhou Yuting, Zhang Wenjun Starring Fabiyi Oluwasegun Michael, Bella Gualano, Nicole Ang, Miao Xuyuan
显示更多
The Relay Dashboard is live. A solo dev gets the same interface as a platform doing millions of transactions a month. Same tools. Day one. No minimum size. No queue. What's inside →
显示更多
0
11
37
3
转发到社区
Hermes v0.6.28 现已发布。 本次更新汇总了 v0.6.27 之后合并的多项能力与修复,重点提升了工作流管控、MCU 设备管理、群聊协作、Coding Agent、Workspace Diff、定时任务和桌面端升级体验。 • 工作流节点级审批 现在可以为关键节点设置完成后的审批门禁,并配置审批人、审批规则以及通过或拒绝状态。节点只有在满足审批条件后才能继续执行;同时修复了工作流重复执行时审批状态未正确重置的问题,让关键流程的人工确认与风险控制更加可靠。 • MCU 设备管理升级 新增 MCU 设备管理能力;global-agent 事件现在必须通过 API Token 授权;ESP32-C3 固件已完成刷新,并进一步提升了远程 Relay 登录的稳定性。 • 群聊 Workspace 变更可追溯 群聊中产生的 Workspace 变更会持久化为 Workspace Diff Run。即使房间会话已经结束,仍可回看房间级 Agent 活动和文件变更记录,方便复盘协作过程。 • Coding Agent 能力修复 Coding Agent 现在会继承作用域内的外部 MCP Server;Workflow Agent 的 Abort 请求能够路由到更准确的目标;任务完成后,系统也会尽力导出 Codex 与 Claude Code 的原生会话记录。 • Workspace Diff 更准确 系统会过滤 SQLite 的 WAL、SHM Sidecar 文件,并在扫描过程中跳过未发生变化的文件,继续识别后续变更,避免新建的普通文件被隐藏。 • 定时任务支持模型选择 创建定时任务时可以选择并持久化 Provider 与 Model。对于当前 Hermes Cron CLI 尚未支持的模型参数,系统不会错误地传递给 CLI,从而提高任务执行的兼容性。 • 会话与桌面端体验改进 修复 Workspace 文件抽屉问题,移除损坏的星标历史 Embed,并记录 Bridge 会话的 ended_at 与 end_reason 元数据。桌面端检测到可用更新时,版本管理按钮会显示国际化的「有新版」提示。
显示更多
吉安幼童失足落水坠河,市民跳水接力救人“我是两个小孩的父亲,实在于心不忍”。A young child accidentally fell into a river in Ji'an, and local citizens jumped into the water to carry out a relay rescue. "As a father of two kids, I simply couldn't bear to stand by."#EverydayHeroes#
显示更多
Robinhood chain @RobinhoodCrypto 使用教程 1、跨链工具 Relay portal BasedBot 2、RPC(钱包自动添加网络的参数) Chain ID 4663 Default RPC URL Currency Symbol ETH Block Explorer 3、K线 Dexscreener 4、区块浏览器 5、dex 6、bot BasedBot 7、发射台 @Noxa_Fi @virtuals_io
显示更多
I have to validate the monkey jpegs. I don't have to store them or relay them. Few.
0
4
186
8
转发到社区
Multi-agents collaborations are among the most interesting agent behaviors right now! We did an experiment the other day with 100+ agents (an open-collaborations for a week) collaborating to improve the inference speed of Gemma 4 in vLLM. Got a 5x final improvement in speed but what really stuck me was the interactions we observed on the message board Integrity & self-policing: - Social-engineering attempt: A human (FusionCow) asked agents to move to Telegram. An agent replied with an unprompted long post on "communication norms" refusing that, calling private side-channels "indistinguishable from collusion." - Verification loophole flagged: an agent found a relaxed verification loophole pushing TPS with clean PPL (PPL is teacher-forced, blind to decode divergence) and flagged it for a ruling by the community. The community pinged the human organizer which ruled it invalid. - Self-notice of overfitting risk: Some later improvements rested on pruning lm_head to a keep-set built from public PPL truth + public decode tokens. An agent noted this would lead to private-subset degradation and another built a keep-set explicitly covering eval prompts. Emergent collaborations: - Communal knowledge base: agents maintained shared lever-maps, playbooks, and triage tools so newcomers wouldn't repeat dead ends (stack-notes, playbook, int4-ceiling notes, MTP map, significance tool, policy simulator). - Four-agent relay: an agent built an int4-lm_head checkpoint but had no quota to run it; another agent tried to run it but failed at load, yet another agent diagnosed the config bug (tie_word_embeddings + ignore-list ordering) and a fourth agent was able to re-run and get to 118 TPS, 2.68×. Build/run/diagnose/ship ended up being split across four independent agents. - GPU-rich/GPU-poor division of labor: an agent was regularly compute-starved and switched to writing specs, byte-math, and acceptance analysis for other GPU-rich agents to execute. Some agents offered external Modal compute for another agent blocked DFlash training. - Cross-agent kernel debugging: an agent debugged another agent run of of yet another agent fused drafter: found a Triton store/load aliasing race in _k_qnorm_rope, a second shape bug, then rewrote attention with flash-decoding split-KV. Fixes posted "take freely." - Quota-pooling norm: Often agents would stage a candidate publicly for whoever has quota to run it. Agents will then usually credits the originator. This behavior emerged because of the 10-job/24h cap (e.g. pupa's package run by resystagent and fabulous-frenzy). Discoveries & reversals: - Agents would make many discoveries and reversal of them, giving them names like the following: - 127 TPS "wall" was an artifact. a mathematical proof of the max possible speed became called in the community the "int4-Marlin floor" but a later agent called the proof circular (only varied the bandwidth term, never overhead). Finally another agent broke to 247 TPS via MTP speculative decoding on a vLLM nightly. - "Smarter draft loses." An agent showed that a 2B drafter's ~1 GB/token read dominates even at perfect acceptance and a much smaller 256-hidden drafter wins at batch-1 because its weights are nearly free to read. Agent discussed how per-accepted-token cost ≈ draft bytes read / acceptance. - "DFlash near-random acceptance": an agent remotly diagnosed the 2–5% acceptance rate of another agent as near-random, ruling out undertraining/vocab caps and pointing to a train/serve hidden-state mismatch (bf16 E4B extraction vs int4 serving). - Much of the race was noise: one agent decide to run the #1# submission 4 times and found a σ≈1.16 TPS variation in single run. Another agent confirmed across 358 runs / 66 buckets: frontier deltas <~4 TPS are ties. Community adopted a significance norm. So many interesting interactions in the interaction board: You can explore also the lineage of inventions from the agents at: And the challenge it-self at And the organization behind the challenge at
显示更多
0
11
197
41
转发到社区