Skip to content

Our Parameter Golf Docs are everywhere #83

@devlux76

Description

@devlux76

The recent exercises to produce a parameter golf exercise of the DESIGN and other docs relied on the work of 4 AI.

3 different Artifical Intellgences plus me an --Actual Idiot--, all working towards a single goal from different angles.

We scattered documents everywhere because we were on our own forks and working through PRs on main.

The first step is to identify them and move them all into a single folder.

Next we must align them to produce the very best APPROACH, DESIGN and code that we can using everything we have at our disposal for the parameter golf challenge.

While doing this realize there is no absolute consensus and in fact each diverges considerably.

That's ok, anywhere two or more docs are basically saying the same thing then that's a good start. It means different AI looking at the same stuff came to similar hypothesis and converged towards similar conclusions.

Where they diverge, we don't want consensus, "the middle ground".

We want a comprehensive solution that leverages the best possible solution given our limits.

We have the Williams 2025 bound which relates trading time for space and space for time. We have precisely 16,000,000 bytes or 128,000,000 bits. We have 10mins and 8xH100 cores and however many flops that works out to.

We have the Wildeberg work which shows us how we can use simple geometry to solve complex problems using a geode and and we have our own finding that quarternary is a mathematically optimum structure especially when we think in terms of quarternary numbers, base pairs of them, and codons of base pairs and sequences of codons and palindromes, linear invariant convolutions with liquid time constant networks using closed form differential equations over what amounts to gray matter block maps and basically all the work that nature pre computed for us over the last billion years.

We can do all kinds of things no one is even thinking about because they forgot that nature solved most of this using Zsub4 around a billion years ago,so let's optimize for the niche.

At end all documents mentioning parameter golf should be in one folder and we have an APPROACH and DESIGN that represents the optimum we can achieve with the full hardware mathematically and code.py to maximize every bit of flops of hardware we have. 0 waste. Make sure to check the actual size of the registers and cache lines for the H100 and realize we have 8 of them at once for 10mins.

Metadata

Metadata

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions