It really seems he was rushed to publish and did not bother cleaning the code up at all. I am compiling the code and reviewing it, and there are 204 dead modules that are not referenced anywhere. And a LOT of repetitive code.
I think this should not be 17 million lines, I bet this can easily be under 1 million lines of Lean with a little bit of cleanup.
I don't know if Anthropic IPO being yesterday, or American Mathematical Society Executive Committee and Board of Trustees meeting being today has anything to do with the announcement happening today, but it's certainly interesting timing.
Part of my job is to ensure that HPC programs (largely LLM libraries these days) work on their next-generation CPUs and with new BIOS revisions. We test them using a shared pool of machines with various configurations. GPU machines are much scarcer, and we have to share them with other teams, so it's hard to reserve a time slot. I usually reserve a CPU machine around the clock so I can work whenever I want (I'm more productive at midnight), and nobody seems to mind.
I've worked here for almost a year now, and I love my company ;)
Well I guess you did say ‘related to’ manufacturing which widens it a little. :P
Expensive, but you can just try things!
$62.79/hr
https://aws.amazon.com/ec2/pricing/on-demand/
I run many high core jobs for various reasons, I often reach for many smaller machines rather than one enormous node like this. But not familiar with how lean parallelizes.
It really is quite slow, I've been having my dot and its 6 sub astras churn away at a proof for Z is Diophantine in Q, even 1/10th as many modules is an overnight affair on my 5800x3d with 128gb of ram. The first version I started on was 326 or 318 variables, but it's allegedly also found some in the mid 100s.
I've been having chat make a neat graph of the spam, it's neat to watch grow (hit the replay button) https://quartic-park.sneakyness.chatgpt.site
There's no real definitive measure of progress, all of the foundational stuff is handled and now it's working on the tricky stuff that is assumed away in the original that made me decide to let them loose trying to formalize.
LLM-generated text below: ``` The build printed about 460,000 linter warnings, and none of them affect correctness. Almost all are code-quality issues such as redundant proof steps, style, and unused variables. About 33,000 are uses of deprecated Mathlib names, which only matter if we upgrade Mathlib.
Memory per process wasn't logged during the run. The container's lifetime memory peak is 441 GiB, but that includes file cache and is only an upper bound. A typical module uses about 0.5 GB of its own memory, and the heaviest use about 8 GB. With about 280 compiles running in parallel, the build used at most about 215 GB of the machine's 1.5 TB of memory, based on spot checks. ```