Integer Sequences cons
The following tool attempts to solve the problem of maintenace in the OEIS after NIST updates its CODATA. By the time I first ran this tool, it reported the following results:
SUMMARY: 123 consistent, 29 need update, 29 need fix, 148 missing, 34 skipped (fewer than 6 certain digits), 15152 cons sequences indexed.
The tool reported 29 constants published from NIST needs update to add more terms whilst 29 sequences need fixing from mistakes in sequences while 123 constants were consistent to the latest CODATA. The following tool automates the verification process and is packed as a REPL.
- pulls data from the OEIS sequence entries and the NIST constants
- checks for the entries to match the OEIS sequences
- pushes findings of malformed or incomplete sequences with missing constants in database
The following packages are required by debian-based systems:
build-essential cmake pkg-config libreadline-dev git curl For arch-based systems, these dependencies are required: base-devel cmake pkgconf readline git curl.
After cloning, provided the dependencies are met, use the following commands:
cd ~/iscons/build
cmake ..
make
sudo make install
./iscons
After that, within REPL update command can be used to pull out fresh repository updates to install. After building you may run the help command to show options:
List of commands:
help - List all available commands
quit - Exit the program
exit - Exit the program
version - Show build info
fetch - Clone or update the local oeisdata repository
update - Pull the latest iscons source and oeisdata, then rebuild
pull - Download the NIST physical constants table into oeis/cons/allascii.txt
run - Cross-check NIST constants against OEIS cons sequences
The rotation on first-use is: fetch, pull, and run.
The following things are limited to with no fixes yet:
- Keyword 'cons' must be in the sequences. Without it, the entries will be ignored.
- Unable to verify from filtered sequences if they are fixed on the main database as the git repository of data dump frequently takes larger time in a day to update.
- Offset findings are unstable and rigid based on NIST's offset while OEIS sequences might be different.
- Even with Fable 5 being used, the project remains a failure at large. Fable 5's suggested architecture was weaker than how I decided the architecture.
Use of AI was ONLY done to src/ext/run.cpp with descriptions of its functions given to Claude Fable 5. Other files had minor AI assistance of pointing me to correct
sources with my own design decisions. This waiver only allows src/ext/run.cpp to be used without LICENSE conditions, other work is still within scope of GPL.
This work is archived and might be erroneous due to AI generation in the main extension.