Closed sphuber closed 2 years ago
The new required functionality will be provided by https://github.com/aiidateam/aiida-core/pull/5713 once merged and released.
With the new functionality the output of verdi process list
would instead look like:
(aiida_dev) sph@invader:~/code/aiida/env/dev/aiida-shell$ verdi process list -a -p1
PK Created Process label Process State Process status
---- --------- --------------------------------- --------------- ----------------
100 1h ago ShellJob<pdb_fetch@localhost> ⏹ Finished [0]
108 1h ago ShellJob<pdb_selchain@localhost> ⏹ Finished [0]
116 1h ago ShellJob<pdb_delhetatm@localhost> ⏹ Finished [0]
124 1h ago ShellJob<pdb_tidy@localhost> ⏹ Finished [0]
Currently, the
process_label
of aShellJob
is set toShellJob
. The output ofverdi process list
then typically looks like:This is the default behavior for all
CalcJobs
as defined byaiida-core
. Normally this is good enough because eachCalcJob
implementation will have a name that is specific to the code that is normally run with it. For example, the plugin forpw.x
of Quantum ESPRESSO is calledPwCalculation
.For the
ShellJob
this is not that informative though as a huge variety of codes can be run with it and they will all be listed asShellJob
. It would be great if this could at least include the shell command that was run and ideally even the computer. So when runningecho
on localhost it would beecho@localhost
for example and if runningpp.x
on the remote computerdaint
we'd getpp.x@daint
.This would most likely require a change in
aiida-core
to provide a hook for aCalcJob
implementation to override the generation of theprocess_label
attribute. It could then set it ascode.full_label
which would reproduce the behavior described above.