←back to thread

15 points obius_prime | 1 comments | | HN request time: 0.207s | source
Show context
obius_prime ◴[] No.46143868[source]
If anyone wants to collaborate or has questions or just wants to tell me off, my email is SylvanGaskin@gmail.com All are welcome. I'd tell myself off but ive done that already and it didn't help, i'm still doing this shit and cant seem to stop... maybe i need an intervention. XD
replies(2): >>46144163 #>>46144765 #
RyanCavanaugh ◴[] No.46144765[source]
If you overlay 30 prime number frequency waves plus 30 more even frequency waves, you're going to have an enormous number of local peaks.

Look at a chart of sin(x) + sin(x/2) + sin(x/3) + sin(x/5) + sin(x/7) + sin(x/11) + sin(x/13) + sin(x/17) + sin(x/19) + sin(x/23) + sin(x/29) + sin(x/31) + sin(x/37) + sin(x/43), you can find a local peak close to practically any number; the chart is effectively entirely composed of peaks.

It's extremely unsurprising that you would find peaks near mathematically relevant numbers, since there are peaks near any number whatsoever. You could pick ten random numbers out of a hat and fine tune those to 99.999%+ accuracy as well using the same scaling procedure.

replies(1): >>46144861 #
RyanCavanaugh ◴[] No.46144861[source]
I modified hamilton_perfect_finder.py to have new values:

# Target constants CONSTANTS = { 'fine_structure': 131.11, 'phi': 1.9, 'pi': 3.6, 'e': 2.4, 'sqrt_2': 1.1, 'sqrt_3': 1.2, 'sqrt_5': 2.5,

Best results: L = 3017.391610 s = 0.042000 Average: 94.848564% Minimum: 82.509479%

  Constants:
    sqrt_2                   : 100.00000000%
    sqrt_3                   : 99.99236291%
    phi                      : 99.93928922%
    pi                       : 99.89806320%
    e                        : 99.88623436%
    sqrt_5                   : 99.85340314%
And this is before any fine-tuning of the parameter set!
replies(3): >>46145067 #>>46145117 #>>46145291 #
1. obius_prime ◴[] No.46145117[source]
You're right — that script (hamiltonian_perfect_finder) IS a parameter search tool. It will find matches to whatever targets you give it. That's not the core claim. The core claim is in the white noise tests and the basic resonance chamber: with FIXED geometry and RANDOM input, the same constants keep appearing. We're not searching for them — they emerge. Try running topology_wave_generator_tests.py with white noise input. No parameter optimization. See what ratios appear without being told what to look for. The question isn't 'can we fit these numbers' — it's 'why do these specific numbers keep showing up when we're not looking for them?