Contribute & contact

This page is for asking BootLoops to build, port or link a tool, reporting a problem or sending a fix, asking a question, and sharing your work. Tools, code and work to share go through GitHub issues and pull requests under the organization BootLoops-ai. Questions on the science or the tools, media inquiries and other correspondence go by email to the addresses under Other questions/issues.

Grow the harness

• Build a new tool. You have a calculation that needs an instrument BootLoops does not have. Describe the problem, the input you have, the output you need, and a reference value if one exists.
• Port a tool. There is an existing package you want driven from BootLoops, or made to run without a proprietary dependency. Name the package and its license, and say which part you need.
• Link your tool. You maintain software that BootLoops should call or list. Send the repository, a one-paragraph description, and a test we can run.

For any of the three, open a Tool request issue on GitHub and pick the kind.

Report a problem or send a fix

Problems and fixes both go through GitHub. A bug in a tool, a wrong number a tool produces, or a broken page, script, data file or download goes in an issue opened with the forms at github.com/BootLoops-ai/feedback (bug, page correction, suggestion). A useful report names the tool or page, says what you ran or read, what you expected and what you saw, and gives the version or commit if code is involved. Issues and replies are public. Fixes are released under the same file names with a changelog line.

A fix is a pull request against the repository that holds the code, under the GitHub organization BootLoops-ai: bootloops-dev (the toolkit), jackandjill-dev (JaCK & Jill), amflow-cpp-dev, kira-dev and blade-dev (the engine forks of AMFlow.cpp, Kira and Blade), and skills-dev (the skills). A pull request carries a one-paragraph description of what it changes and why, a test or a reference value that shows the change is right, and code under a license compatible with MIT. The engine forks keep their upstream licenses.

Comments on the science of a paper go to science@bootloops.ai, below.

Other questions/issues

Anything that is not a tool request, bug report, code change or work to share goes by email. Pick the address that fits.

• Questions or comments on the science: science@bootloops.ai.
• Questions or comments about the tools: tools@bootloops.ai.
• Media inquiries: media@bootloops.ai.
• Other correspondence: general@bootloops.ai.

Share your work

Did you do something neat with BootLoops? Tell us about it and we can link to your work here. Open an Application issue on GitHub with a short description, the field, and a link to the paper, repository or page. Selected work gets a link or a web summary on this site, with credit to you.

Record of contributions

A contribution can be a newly closed integral, an independent check of a published number, a tool improvement, a new tool, or an application. Substantive ones are credited in this table, which documents results and improvements with BootLoops since its release.