Scripts¶
This page documents the usage of the AbiPy scripts, the subcommands available and the options supported by each subcommand.
To analyze the cystalline structure stored in FILE, use abistruct.py
.
To operate on a single FILE, use abiopen.py
.
To compare multiple FILES of the same type, use the abicomp.py
script.
If the analysis requires the execution of additional logic
(e.g. the computation of phonons with anaddb from the DDB file), use abiview.py
.
To generate a minimalist input file for Abinit, use abinp.py
.
For a command line interface to the Abinit documentation, use abidoc.py
.
Finally, use abicheck.py
to validate your AbiPy + Abinit installation before running AbiPy flows
and use abirun.py
to launch Abinit calculations.
Important
Each script provides a --help
option that documents all the commands available
and provides a list of typical examples.
To list of the options supported by COMMAND use e.g. abicomp.py COMMAND –help.
abistruct.py
- Named Arguments
- subcommands
- Sub-commands
- spglib
- abispg
- convert
- has_quad
- traj2xdatcar
- supercell
- abisanitize
- primitive
- irefine
- conventional
- proto
- wyckoff
- tensor_site
- neighbors
- interpolate
- xrd
- oxistate
- ipython
- notebook
- panel
- kpath
- bz
- ngkpt
- ktables
- abikmesh
- lgk
- kstar
- keq
- visualize
- mp_id
- mp_match
- mp_search
- mp_ebands
- cod_search
- cod_id
- animate
- chemenv
abiopen.py
abicomp.py
abiview.py
abinp.py
abidoc.py
abicheck.py
abirun.py
- Positional Arguments
- Named Arguments
- subcommands
- Sub-commands
- single
- rapid
- scheduler
- status
- set_status
- cancel
- restart
- reset
- move
- open
- abiopen
- abibuild
- doc_scheduler
- explain_works
- explain_tasks
- autoparal
- panel
- new_manager
- tail
- timeit
- deps
- robot
- cycles
- dims
- inspect
- inputs
- abivars
- structures
- ebands
- hist
- doc_manager
- events
- corrections
- history
- handlers
- notebook
- ipython
- tar
- tricky
- debug
- debug_reset
- reset_jobids
- group
- diff
- networkx
- graphviz
- listext
abips.py
oncv.py