惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

博客园 - 三生石上(FineUI控件)
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
月光博客
月光博客
博客园 - 【当耐特】
Hugging Face - Blog
Hugging Face - Blog
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
爱范儿
爱范儿
大猫的无限游戏
大猫的无限游戏
S
SegmentFault 最新的问题
博客园_首页
雷峰网
雷峰网
量子位
有赞技术团队
有赞技术团队
博客园 - 叶小钗
博客园 - 聂微东
V
V2EX
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园 - 司徒正美
小众软件
小众软件
The Cloudflare Blog
阮一峰的网络日志
阮一峰的网络日志
Apple Machine Learning Research
Apple Machine Learning Research
Jina AI
Jina AI
人人都是产品经理
人人都是产品经理

Hacker News - Newest: "AI"

AI can't read an investor deck AI as an attorney? Student uses ChatGPT, Gemini to sue UW over alleged racial discrimination Hacking MCP Servers in AI Systems – The Rug Pull: Tool Changes After Approval GitHub - MeepCastana/KubeezCut: Free Web based video editor Can AI judge journalism? A Thiel-backed startup says yes, even if it risks chilling whistleblowers Coming soon: 10 Things That Matter in AI Right Now DARPA built an AI to fact-check enemy weapons claims What explains heterogeneity in AI adoption? When AI Meets Muscle: Context-Aware Electrical Stimulation Promises a New Way to Guide Human Movements - Department of Computer Science AI Changed How We Build. It Did Not Change What Matters. Linux rules on using AI-generated code - Copilot is OK, but humans must take 'full responsibility for the… Meta spins up AI version of Mark Zuckerberg to engage with employees Code Mode: Let Your AI Write Programs, Not Just Call Tools | TanStack Blog GitHub - Delavalom/graft: Go framework for building AI agents. Type-safe tools, multi-provider (OpenAI, Anthropic, Gemini, Bedrock), zero vendor SDKs. India's TCS tops estimates, says new AI models did not dent services demand Gen Z's fading AI hype Strong feeling: we are in a folded AI reality GitHub - machinarii/total-recall-catalog: A reference catalog of latest knowledge retrieval, memory & RAG systems GitHub - mensfeld/code-on-incus: Give each AI agent its own isolated machine with root, Docker, and systemd. Active defense detects and stops threats automatically.. Quantization, LoRA, and the 8% Problem: Benchmarking Local LLMs for Production AI Iran war: We spoke to the man making Lego-style AI videos that experts say are powerful propaganda Powell, Bessent discussed Anthropic's Mythos AI cyber threat with major U.S. banks GitHub - immartian/bellamem: Persistent belief-graph memory for AI agents. Retrieves decisive context by importance — not recency, not RAG, not /compact. recursive-mode: The Repo-Native Operating System for AI Engineering After the attack on Sam Altman's home, will AI CEO's go on the offensive? The biggest advance in AI since the LLM Opus 4.6 vs GPT 5.4 One Prompt Unity World Generation Test “AI polls” are fake polls Client Challenge Can AI be a 'child of God'? Inside Anthropic's meeting with Christian leaders
GitHub - sammysltd/euromesh: A sourced model and short re...
smashini · 2026-06-15 · via Hacker News - Newest: "AI"

A sourced model and short report on a single question:

Can Europe stand up a sovereign frontier-class AI model now, by federating the public compute it already owns, while the gigawatt datacenters it is planning take years to connect to the grid?

The answer the model gives is yes, as a stopgap. Europe already operates tens of exaflops of public AI compute across the EuroHPC supercomputers and the national AI Factories. A 1 GW campus, by contrast, waits a mean of 7.6 years for grid power. Federated with low-communication (DiLoCo-style) training, the compute Europe already has can deliver a frontier-class model around 2028, against around 2033 for a new gigawatt campus.

Read this first

The report is paper/compute-at-home.pdf (built from paper/compute-at-home.md). It is a short, sourced read aimed at a general audience. Title: "Do We Need OpenAI or Anthropic? Europe Has Tens of Exaflops at Home."

What is in the repo

euromesh/
├── README.md
├── requirements.txt
├── paper/
│   ├── compute-at-home.md / .pdf   the report
│   ├── grid_queue_dataset.md       sourced 1 GW vs 40 MW grid-connection lead times
│   ├── eurohpc_substrate.md        sourced EU public-compute inventory + "is it enough" math
│   ├── build_pdf.sh, _report.typ   PDF build (pandoc + typst)
│   └── figures/                    generated charts (PNG + SVG)
└── model/
    ├── MODEL_SPEC.md               the model specification (equations, params, invariants)
    ├── RESULTS.md                  full results, scenarios, sensitivity, caveats
    ├── run.py                      regenerates every CSV and figure
    ├── src/                        the three-layer model (efficiency, ramp, regions)
    ├── params/                     hardware.yaml, training.yaml, regions.csv + SOURCES
    ├── results/                    generated CSVs (do not hand-edit)
    └── tests/                      pytest suite (52 tests) + invariant self-checks

The model in one paragraph

Three layers. Layer 1 is the per-FLOP efficiency of low-communication training (how much the DiLoCo penalty costs). Layer 2 is time-to-availability (when sites energize and how fast cumulative compute accrues). Layer 3 is a per-region scorecard on time, cost, carbon, and feasibility. The headline result is set almost entirely by Layer 2: it reduces to one inequality, the federation wins if its sites are online before a gigawatt campus is. The training efficiency penalty is second-order, confirmed by the sensitivity tornado.

Run it

python3 -m venv .venv
.venv/bin/pip install -r requirements.txt
.venv/bin/python -m model.run          # regenerates all CSVs in model/results and figures in paper/figures
.venv/bin/python -m pytest model/tests/ # 52 passed
bash paper/build_pdf.sh                 # rebuilds paper/compute-at-home.pdf (needs pandoc + typst)

The run is reproducible from a clean tree: deleting every output and re-running exits 0 and regenerates everything.

Data and sources

  • Grid-connection lead times: paper/grid_queue_dataset.md, seven regions, per-region primary sources, anchored by the AWS "up to seven years" statement and the IEA 2-to-10-year range, with limitations stated.
  • EU public compute: paper/eurohpc_substrate.md, the EuroHPC flagships and the 19 AI Factories, accelerator counts and the training-time math.
  • Model parameters: model/params/SOURCES.md and model/params/SOURCES_hardware_training.md, with confidence tags.

Honest caveats

The point of this repo is clarity, not novelty. The thesis rests on grid-queue lead times, which are sourced central estimates rather than observed figures (no European operator has yet energized a 1 GW point load). The compute is owned but not yet usable for one coordinated run: the EuroHPC machines are shared, batch-scheduled, and heterogeneous, so the addressable fraction is a political decision rather than a hardware fact. Frontier-scale distributed training is unproven above about 10B parameters today, so the target is a credible frontier-class model rather than a guaranteed 405B. All of this is in model/RESULTS.md and the report's caveats section. Figures and dated events are as of June 2026. This is an independent model and analysis, not peer-reviewed.