Jason Nochlin

Rebased my fork with latest main and ensured `test.sh` passes

The original results excited me because the difference was small, but this change always had the min time. Not true after rebasing. Seems like it may be a wash for...

I added output of the raw times in addition to the trimmed means, eg: ```bash fork,trimmed_mean spullara,0.52814592528 royvanrijn,0.49758428661333337 fork,raw_times spullara,0.51465599528,0.53491328628,0.52979903628,0.51972545328,0.53921453728 royvanrijn,0.49466057828000004,0.49655945328,0.49698236928,0.4992110372800001,0.50892974428 ```

New look, based on: https://github.com/gunnarmorling/1brc/issues/105#issuecomment-1881557239

@gunnarmorling Yes, we can do `hyperfine --output `, I'll take a look at `process_output.java` shortly

Remaining TODO: - [ ] Save output to file - [ ] Incorporate functionality from `process_output.java`

`process_output.java` is used as follows: 1. Expected output is created via `./eval.sh baseline; cp baseline.out out_expected.txt` 2. Fork output is created via `./eval.sh $fork` 3. Invoke process.sh `./process.sh $fork` 4....

Ugh, `hyperfine --output ` overwrites FILE on each run... it doesn't append. For now we'll only check the output of 1 run unless we can find a workaround

>So if we run this script multiple times for multiple contenders, will we check the output of the last run for all contenders (ok)? Or just the last run of...

I pushed all the changes from `process_output.java`! New look: ## Happy Path ## Verification failed Going to do another round of testing on a Fedora box too