Lanczos

Documentation for Lanczos.

See the Index for the complete list of documented functions and types.

The code, which is hosted on GitHub, is tested using various continuous integration services for its validity.

This repository is created and maintained by @singularitti, and contributions are highly welcome.

Package features

Installation

The package can be installed with the Julia package manager. From the Julia REPL, type ] to enter the Pkg mode and run:

pkg> add Lanczos

Or, equivalently, via Pkg.jl:

julia> import Pkg; Pkg.add("Lanczos")   Resolving package versions...
ERROR: expected package `Lanczos [f316c00f]` to be registered

Documentation

• STABLE — documentation of the most recently tagged version.
• DEV — documentation of the in-development version.

Project status

The package is developed for and tested against Julia v1.6 and above on Linux, macOS, and Windows.

Questions and contributions

You can post usage questions on our discussion page.

We welcome contributions, feature requests, and suggestions. If you encounter any problems, please open an issue. The Contributing page has a few guidelines that should be followed when opening pull requests and contributing code.

Manual outline

• Installation Guide
• • Install Julia
  • • Which version should I pick?
  • Install the package
  • Update the package
  • Uninstall and then reinstall the package
• Troubleshooting
• • Cannot find the Julia executable
  • Julia starts slow
• Contributing
• • Code of conduct
  • Join the community forum
  • Improve the documentation
  • File a bug report
  • Contribute code to Lanczos
  • • Step 1: decide what to work on
    • Step 2: fork Lanczos
    • Step 3: install Lanczos locally
    • Step 4: checkout a new branch
    • Step 5: make changes
    • Step 6a: test your code changes
    • Step 6b: test your documentation changes
    • Step 7: make a pull request
    • Step 8: respond to comments
    • Step 9: cleaning up
• Style Guide
• • Formatting
  • • Run JuliaFormatter
    • Use the Julia extension for Visual Studio Code
• Design Principles
• • Consistency vs adherence
  • Community contribution guidelines
  • Open source contributions are allowed to start small and grow over time
  • Generic code is preferred unless code is known to be specific
  • Internal types should match the types used by users when possible
  • Trait definition and adherence to generic interface is preferred when possible
  • Macros should be limited and only be used for syntactic sugar
  • Errors should be caught as early as possible, and error messages should be made contextually clear for newcomers
  • Subpackaging and interface packages is preferred over conditional modules via Requires.jl
  • Functions should either attempt to be non-allocating and reuse caches, or treat inputs as immutable
  • Out-of-place and immutability is preferred when sufficient performant
  • Tests should attempt to cover a wide gamut of input types
  • When in doubt, a submodule should become a subpackage or separate package
  • Globals should be avoided whenever possible
  • Type-stable and type-grounded code is preferred wherever possible
  • Closures should be avoided whenever possible
  • Numerical functionality should use the appropriate generic numerical interfaces
  • Functions should capture one underlying principle
  • Internal choices should be exposed as options whenever possible
  • Prefer code reuse over rewrites whenever possible
  • Prefer to not shadow functions

Library outline

Index