You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ verdi help
List of the most relevant available commands:
* calculation Query and interact with calculations
* code Setup and manage codes to be used
* comment Manage general properties of nodes in the database
* computer Setup and manage computers to be used
* daemon Manage the AiiDA daemon
* data Setup and manage data specific types
* devel AiiDA commands for developers
* export Create and manage AiiDA export archives
* graph Utility to explore the nodes in the database graph
* group Setup and manage groups
* help Describe a specific command
* import Import nodes and group of nodes
* install Install/setup aiida for the current user
* node Manage operations on AiiDA nodes
* profile List AiiDA profiles, and set the default profile.
* quicksetup Quick setup for the most common usecase (1 user, 1 machine).
* rehash Re-hash all nodes.
* restapi verdi command used to hook up the AiIDA REST API.
* run Execute an AiiDA script
* setup Setup aiida for the current user
* shell Run the interactive shell with the AiiDA environment loaded.
* user List and configure new AiiDA users.
* work Manage the AiiDA worflow manager
* workflow Manage the AiiDA legacy worflow manager
Before each command you can specify the AiiDA profile to use, with 'verdi -p <profile> <command>' or 'verdi --profile=<profile> <command>'
Use 'verdi help <command>' for more information on a specific command.
$ echo $?
1
verdi help is pretty much the only command that can be tested without setting up an aiida profile, so this is a real problem for testing whether aiida-core is properly installed in our conda-forge pr.
This should be fixed in 0.12.3
The text was updated successfully, but these errors were encountered:
In 0.12.2, verdi help returns exit status 1:
verdi help
is pretty much the only command that can be tested without setting up an aiida profile, so this is a real problem for testing whether aiida-core is properly installed in our conda-forge pr.This should be fixed in 0.12.3
The text was updated successfully, but these errors were encountered: