brugada.net · What’s standing
Updated 16 July 2026
The previous round claimed four compounds survived its longest test. The files underneath that claim don’t agree with it, and this page is why.
Here is the short version for anyone who doesn’t want the forensics.
A scoreboard file in this project is labelled the “verdict of record”. It says four compounds passed the long test. When I went and read the actual simulation files it was supposedly summarising, they told a different story — and for two compounds, the opposite story.
The scoreboard calls it a survivor. Every simulation that still exists shows it letting go — including the longest run in the entire project.
The scoreboard calls it the shaky one. Every simulation that still exists shows it holding. The number the scoreboard cites as its failure appears in no file anywhere.
Recorded as three successful runs. There is exactly one. It’s clean — but one is not three, and nobody should round it up.
Isn’t on the survivor list at all. Three runs, all holding. On the surviving evidence it outranks two compounds that are. Nobody has looked at it.
And the fact that undercuts the whole stage: the test was specified as 100 nanoseconds, three times over. No simulation ever reached 100 nanoseconds. The longest is 90.5. Most are about ten.
This is not fraud, and I don’t think it’s even carelessness. An automated cleanup script deleted several finished simulations before anyone had extracted their results — the log records it happening. So those scoreboard numbers may well be real measurements of runs that no longer exist. Unverifiable isn’t the same as invented, and I’m not going to pretend it is. But it does mean the headline result can’t currently be reproduced from the project’s own files.
Every long-test simulation that still exists, drawn against the time it actually ran rather than the time it was supposed to. Blue holds the grip. Pink lets go. The dashed line is where 100 nanoseconds would be.
Nothing reaches the dashed line. Tegaserod’s long run — the longest anywhere in this project at 90.5 ns — is the pink one climbing away from the grip and never coming back. Alniditan’s three are all blue. Drawn from the raw frame-by-frame data, not from the scoreboard.
Read straight from the per-seed reduction files. The rule is the project’s own: HOLD needs second-half occupancy ≥ 0.70 and a second-half mean ≤ 3.2 Å; ESCAPE is occupancy < 0.30.
| Compound | Seed | Actual ns | 2nd-half mean (Å) | Occupancy | Verdict |
|---|---|---|---|---|---|
| ZINC000004286767 | seed1 | 88.9 | 2.887 | 0.967 | HOLD |
| ZINC000004286767 | seed2 | 13.6 | 3.801 | 0.214 | ESCAPE |
| ZINC000004286767 | seed3 | 9.7 | 3.037 | 0.918 | HOLD |
| ZINC000006819928 | seed1 | 87.3 | 2.724 | 1.000 | HOLD |
| ALNIDITAN | seed1 | 87.8 | 2.725 | 0.998 | HOLD |
| ALNIDITAN | seed2 | 10.1 | 2.754 | 1.000 | HOLD |
| ALNIDITAN | seed3 | 9.9 | 2.724 | 1.000 | HOLD |
| TEGASEROD | seed1 | 90.5 | 10.556 | 0.000 | ESCAPE |
| TEGASEROD | seed3 | 10.2 | 8.717 | 0.000 | ESCAPE |
| TEGASEROD | seed2 | 10.0 | 4.556 | 0.036 | ESCAPE |
| ZINC000002430405 | seed1 | 89.6 | 2.764 | 1.000 | HOLD |
| ZINC000001702464 | seed1 | 89.1 | 9.658 | 0.193 | ESCAPE |
| ZINC000002430405 | seed2 | 12.4 | 2.792 | 0.997 | HOLD |
| ZINC000001702464 | seed2 | 12.3 | 4.662 | 0.199 | ESCAPE |
| ZINC000002430405 | seed3 | 9.9 | 2.809 | 1.000 | HOLD |
| ZINC000001702464 | seed3 | 9.6 | 2.733 | 1.000 | HOLD |
Sixteen runs across six compounds. Six are genuine long runs (87–90 ns); ten are stubs of about ten nanoseconds that were labelled “100ns” anyway.
RESULTS_ONLY_20260711/02_verdicts_reductions/*_seed*_100ns_clip.json
Nothing in the project writes it. Searching every Python and shell script for its filename returns zero hits. The project’s own README says the scoreboards can be regenerated. They cannot.
It states a rule that no code implements. The scoreboard says a compound’s verdict is the majority of its seeds. No code anywhere implements a majority rule. The one classifier that does exist does the opposite: HOLD only if all seeds hold; ESCAPE if any seed escapes. Under the project’s own rule, tegaserod and alniditan are both ESCAPE — and that unimplemented majority rule is precisely what turns them into survivors.
Every seed 1 matches perfectly. Nothing else matches at all. All seven compounds’ seed-1 numbers match their long trajectory to three decimals. Every seed 2, 3 and 4 matches no file — not the long runs, not the short runs, not any truncation of either, and not the archive on the external drive.
One of those seeds is about nine nanoseconds. Alniditan’s seed 4 survives on the drive at roughly 8.8 ns — 44 thinned frames, 139 MB against ~1.3 GB for comparable runs. It is counted as a ≥100 ns success.
One measurement would settle it. Re-run the reduction against tegaserod’s seed-2 long trajectory on the external drive. If it returns 2.777 Å at occupancy 1.0, the scoreboard measured something real and this extract is just incomplete. If it returns 4.556 Å at 0.036, the scoreboard is wrong. Until someone runs it, both stay live and this page says so.
None of these are drugs. Two are catalogue numbers with no safety data of any kind. The two that are real medicines were approved to do something else entirely, and nothing here suggests anyone should take them. This is a list of things that would be worth an afternoon of somebody’s bench time. Nothing more, and nothing less.
onwards.