A bug has been fixed that prevented finding smooth numbers as intended. Also, I promised well-tuned defaults; however, the best settings very often depend on the exact number being factored. By design, the smoothness bound, sieving bound, and smooth number limit cutoff were all scaled such that accepted or defensible heuristics should be the default at a value of `1.0`: these **are** the **most-general** best defaults. We **could** tune for a specific scale, like 64-bit semiprimes, but why is the software specifically being used for 64 bits? I am still carefully considering default tuning, but maybe the best we can do **in general** reflects the fact that simple defaults like `1.0` multipliers **already** match best general advice, but **expect to tune in any specific case on basis of your knowledge of the theory**.
**Full Changelog**: https://github.com/vm6502q/FindAFactor/compare/v5.0.6...v5.1.0
sha1sum results:
bad5d7a6b3d8949a404e3a191da7d45f72154276 FindAFactor-5.1.0-cp310-cp310-manylinux_2_35_x86_64.whl
c2295de00d285a87434b9e50b032337680d9b4de FindAFactor-5.1.0-cp312-cp312-manylinux_2_39_x86_64.whl
eb82a928e6671a82699e79adfdd06814463afb6d FindAFactor-5.1.0-cp312-cp312-win_amd64.whl
4c4ef7cfe4ecb39f63462c53a6a981aa353e18db FindAFactor-5.1.0-cp313-cp313-macosx_13_0_x86_64.whl
cc79fb2817600bc1811513553c9ef29b173a877d FindAFactor-5.1.0-cp313-cp313-macosx_14_0_arm64.whl
a7cd10002f4368b05b08e7a9e040f1e4bd61cedd FindAFactor-5.1.0-cp313-cp313-macosx_15_0_arm64.whl
2a53c382143b6d9b4c2092bc95d161e0fbb06c4f FindAFactor-5.1.0-cp38-cp38-manylinux_2_31_x86_64.whl
edbd0dfb682548edbbedc8bcc0f96e300a9e4591 findafactor-5.1.0.tar.gz