Manual
This is the main user-facing manual for GaussletBases.jl.
If you are using the package as a scientist, this is the section to read first. The manual is intentionally small. It tells you:
- what the package can already do reliably
- which workflow is the recommended starting point
- where the mature radial/atomic workflow, the newer ordinary/cartesian workflow, and the advanced research line currently stand
- which pages are background material rather than first-read documents
Detailed basis-construction and operator-construction recipes live in the Algorithms section. The Manual tells you what to read and run; Algorithms records how the main constructions are built.
The scientific motivation throughout is the gausslet one from the papers: localized, orthonormal Gaussian-built basis functions with systematic spacing refinement and a two-index or diagonal Coulomb structure. The manual is organized around the workflows that currently realize that idea most cleanly.
Who this manual is for
Read this section if you want to:
- build and use gausslet bases
- reproduce the current radial and atomic workflows
- understand whether the ordinary Cartesian branch is ready for your use case
- find the right example or workflow page without digging through note history
If you already know the object or function you want, jump to the Reference. If you want the exact construction order for a basis or operator path, jump to Algorithms.
Recommended reading order
For a new reader, the shortest useful path is:
That path gets you from basis construction to a real hydrogen calculation and then to the current atomic examples.
Branch-specific paths
If you want atom-centered radial and atomic work:
If you want the ordinary Cartesian branch:
The ordinary branch is worth reading after you understand the radial line. It is the right place to learn the current mapped and hybrid ordinary workflows, but it is not the best first entry point into the package.
If you want the active experimental angular line:
That page is intentionally narrow. It is there to mark the current research boundary, not to present a finished angular workflow.
If you want more depth later
After the main workflow pages are clear, the next useful documents are:
The Developer Notes section is where the design history, architecture background, and narrower supporting notes live. It is there when you want more depth, without crowding the main manual.