It looks like ra_pareto was also broken on amd64 (probably for the same
"two variables with the same name" reason, though I haven't tested
this), giving a constant output within its range circle, and the
ra_pareto.out reference used that broken version (it's identical to
ra_disk.out).
Hence, I now consider it likely that the two fixes above do work, and
the test references are wrong.
Furthermore, the documentation doesn't match the actual behaviour (with
or without these fixes):
- It shows amortized_disk as a cone; it's now actually 1/(1+distance).
- It shows nonzero output extending outside the distance=range circles,
which is now not possible (hyantes_run.c:82).
The definitions of amortized_disk and pareto are also weird in that they
change shape (not just scale) when range is changed.
Upstream appears to be abandoned (last commit 6 years ago, last upload
by the sole Uploader (who is also upstream) nearly 7 years ago).
