# Reference¶

## Calculation and Parser classes¶

calcjobaiida_wannier90.calculations.Wannier90Calculation

Plugin for Wannier90, a code for computing maximally-localized Wannier functions. See http://www.wannier.org/ for more details.

Inputs:

• code, Code, required – The Code to use for this job.
• kpoint_path, Dict, optional – Description of the k-points path to be used for bands interpolation; it should contain two properties: a list path of length-2 tuples with the labels of the endpoints of the path; and a dictionary point_coords giving the scaled coordinates for each high-symmetry endpoint.
• kpoints, KpointsData, required – k-point mesh used in the NSCF calculation.
• local_input_folder, FolderData, optional – Get input files (.amn, .mmn, …) from a class FolderData stored in the AiiDA repository.
Namespace Ports
• call_link_label, str, optional, non_db – The label to use for the CALL link if the process is called by another process.
• computer, Computer, optional, non_db – When using a “local” code, set the computer on which the calculation should be run.
• description, str, optional, non_db – Description to set on the process node.
• dry_run, bool, optional, non_db – When set to True will prepare the calculation job for submission but not actually launch it.
• label, str, optional, non_db – Label to set on the process node.
• options, Namespace
Namespace Ports
• account, str, optional, non_db – Set the account to use in for the queue on the remote computer
• append_text, str, optional, non_db – Set the calculation-specific append text, which is going to be appended in the scheduler-job script, just after the code execution
• custom_scheduler_commands, str, optional, non_db – Set a (possibly multiline) string with the commands that the user wants to manually set for the scheduler. The difference of this option with respect to the prepend_text is the position in the scheduler submission file where such text is inserted: with this option, the string is inserted before any non-scheduler command
• environment_variables, dict, optional, non_db – Set a dictionary of custom environment variables for this calculation
• import_sys_environment, bool, optional, non_db – If set to true, the submission script will load the system environment variables
• input_filename, str, optional, non_db
• max_memory_kb, int, optional, non_db – Set the maximum memory (in KiloBytes) to be asked to the scheduler
• max_wallclock_seconds, int, optional, non_db – Set the wallclock in seconds asked to the scheduler
• mpirun_extra_params, (list, tuple), optional, non_db – Set the extra params to pass to the mpirun (or equivalent) command after the one provided in computer.mpirun_command. Example: mpirun -np 8 extra_params[0] extra_params[1] … exec.x
• output_filename, str, optional, non_db
• parser_name, str, optional, non_db
• prepend_text, str, optional, non_db – Set the calculation-specific prepend text, which is going to be prepended in the scheduler-job script, just before the code execution
• priority, str, optional, non_db – Set the priority of the job to be queued
• qos, str, optional, non_db – Set the quality of service to use in for the queue on the remote computer
• queue_name, str, optional, non_db – Set the name of the queue on the remote computer
• resources, dict, required, non_db – Set the dictionary of resources to be used by the scheduler plugin, like the number of nodes, cpus etc. This dictionary is scheduler-plugin dependent. Look at the documentation of the scheduler for more details.
• scheduler_stderr, str, optional, non_db – Filename to which the content of stderr of the scheduler is written.
• scheduler_stdout, str, optional, non_db – Filename to which the content of stdout of the scheduler is written.
• submit_script_filename, str, optional, non_db – Filename to which the job submission script is written.
• withmpi, bool, optional, non_db
• store_provenance, bool, optional, non_db – If set to False provenance will not be stored in the database.
• parameters, Dict, required – Input parameters for the Wannier90 code
• projections, (OrbitalData, Dict, List), optional – Starting projections for the Wannierisation procedure.
• remote_input_folder, RemoteData, optional – Get input files (.amn, .mmn, …) from a class RemoteData possibly stored in a remote computer.
• settings, Dict, optional – Additional settings to manage the Wannier90 calculation.
• structure, StructureData, required – input crystal structure

Outputs:

• interpolated_bands, BandsData, optional – The interpolated band structure by Wannier90 (if any).
• nnkp_file, SinglefileData, optional – The .nnkp file, produced only in -pp (postproc) mode.
• output_parameters, Dict, required – The output_parameters output node of the successful calculation.
• remote_folder, RemoteData, required – Input files necessary to run the process will be stored in this folder node.
• retrieved, FolderData, required – Files that are retrieved by the daemon will be stored in this node. By default the stdout and stderr of the scheduler will be added, but one can add more by specifying them in CalcInfo.retrieve_list.

class aiida_wannier90.parsers.Wannier90Parser(node)[source]

Wannier90 output parser. Will parse the centres, spreads and, if available, the Imaginary/Real ratio of the Wannier functions. Will also check if the output converged.

## Helper modules¶

### Writing input files¶

This submodule contains helper functions to create input files.

aiida_wannier90.io.write_win(filename, parameters, kpoints=None, structure=None, kpoint_path=None, projections=None, random_projections=False)[source]

Write input to a .win file.

Parameters

### Creating OrbitalData instances¶

aiida_wannier90.orbitals.generate_projections(list_of_projection_dicts, structure)[source]

Use this method to emulate the input style of Wannier90, when setting the orbitals (see chapter 3 in the Wannier90 user guide). Position can be provided either in Cartesian coordinates using position_cart or can be assigned based on an input structure and kind_name. Pass a list of dictionaries, in which the keys of each dictionary correspond to those below. Also note that radial and ang_mtm_mr_list both use 0-based indexing as opposed to 1-based indexing, effectively meaning that both should be offset by 1. E.g., an orbital with two radial nodes would use radial=2 (Wannier90 syntax), and then be converted to radial_nodes=1 (AiiDA plugin syntax) inside the stored orbital.

Note

The key entries used here do not correspond to the keys used internally by the orbital objects. For example, ang_mtm_mr_list will be converted to magnetic_number in the OrbitalData node (the internal key is mentioned in brackets).

Parameters
• position_cart – position in Cartesian coordinates or list of positions in Cartesian coordinates (position)

• kind_name – kind name in the input StructureData node (kind_name)

• radial – number of radial nodes (radial_nodes + 1)

• ang_mtm_name – orbital name or list of orbital names, cannot be used in conjunction with ang_mtm_l_list or ang_mtm_mr_list (see ang_mtm_l_list and ang_mtm_mr_list).

• ang_mtm_l_list – angular momentum (either an integer or a list), if ang_mtm_mr_list is not specified will return all orbitals associated with it (angular_momentum).

• ang_mtm_mr_list – magnetic angular momentum number must be specified along with ang_mtm_l_list (magnetic_number + 1). Note that if this is specified, ang_mtm_l_list must be an integer and not a list.

• spin – the spin, spin up can be specified with 1, 'u' or 'U' and spin down can be specified using -1, 'd' or 'D' (spin)

• zona – as specified in user guide, applied to all orbitals (diffusivity)

• zaxis – the z-axis of the orbital, a list of three floats as described in wannier user guide (z_orientation)

• xaxis – the x-axis of the orbital, a list of three floats as described in the Wannier user guide (x_orientation)

• spin_axis – the spin alignment axis, as described in the user guide (spin_orientation)