This repository contains the source of the official registry of AiiDA plugins.
If you are starting to develop a new plugin (e.g. using the AiiDA plugin cutter) or if you already have one, please register it here. We strongly encourage to register at early stages of development, since this both "reserves" the name of your plugin and informs the developer community of your ongoing work.
- Fork this repository
- Add your plugin to the
plugins.json
file, e.g."new": { "name": "aiida-new", "entry_point": "new", "state": "registered", "plugin_info": "https://raw.github.com/aiidateam/aiida-new/master/setup.json", "code_home": "https://github.com/aiidateam/aiida-new", "documentation_url": "http://aiida-new.readthedocs.io/" },
- Create a Pull Request to this repository
The name under which your plugin will be distributed.
By convention, names of AiiDA plugins are lowercase and prefixed by aiida-
.
Examples:
aiida-quantumespresso
aiida-gaussian-datatypes
The prefix of all entry points provided by the plugin.
By convention, a plugin aiida-xxx
should use entry_point: 'xxx'
.
Example: aiida-quantumespresso
uses the entry point prefix quantumespresso
and provides numerous entry points, all of which start with quantumespresso.
.
One of
registered
: plugin is not yet in a working state. Use this to secure a specific name before starting developmentdevelopment
: plugin adds new functionality but isn't stable enough for production usestable
: plugin can be used in production
A URL or PyPI package name for installing the most recent development (state: 'development'
) or stable (state: 'stable'
) version of the package with pip.
Examples:
"pip_url": "aiida-quantumespresso"
for a package that is registered on PyPI"pip_url": "git+https://github.com/aiidateam/aiida-wannier90"
for a package not registered on PyPI
URL pointing to a JSON file containing the keyword arguments passed to the setuptools.setup
function when installing your package.
For an example, see the setup.json
file of the aiida-diff demo plugin.
The link to the homepage of your plugin, for example its github repository.
The link to the online documentation for your plugin, for example on readthedocs.org .