---
# System prepended metadata

title: AiiDA Team Meeting 2023-02-23
tags: [team meetings]

---

# AiiDA Team Meeting 2023-02-23

###### tags: `team meetings`
###### time: 10am CET

[TOC]

### Present

* Sebastiaan
* Giovanni
* Chris
* Jason
* Francisco
* Marnik

### Catch-up round

*Max. 3 minutes each*

Sebastiaan:
 * [Process functions: Infer argument valid_type from type hints](https://github.com/aiidateam/aiida-core/pull/5900): This will add automatic type validation based on type hints in process functions. (I was thinking to optionally also add parsing of docstring to get the help string). By adding this functionality, it would become very easy to expose process functions in a wrapping workchain and still have the benefit of having `valid_type` and `help` attributes automatically set on the input ports.
     * Nice, three years later but got there eventually 👌 https://github.com/aiidateam/aiida-core/issues/3724 
 * [Should the use_login_shell property of the AuthInfo also be considered in the submission script shebang](https://github.com/aiidateam/aiida-core/issues/5895)
 * [Fixtures: Add argument `use_subprocess` to `run_cli_command`](https://github.com/aiidateam/aiida-core/pull/5846)

Chris:
- Road map
- Fircrest

Marnik:
 * Nothing much to report on the AiiDA-core front.
 * Organise some documentation/tutorial days in May/June?


Jason:
 * Require feedback and advices for how to manage the [QeApp releases](https://hackmd.io/NH9ok_KcR8G9IA46DyXXIA#Some-notes-on-QeApp-release) 
 * The Gsoc 2023 is ready for students, I am adding tags of [good first issue](https://github.com/aiidateam/aiida-core/labels/good%20first%20issue) to issues that should be easy to go and not involved too much with core. More such issues are welcome.


Giovanni

* CSCS is planning some transition solution to allow easier use of SSH keys with expiration while people convert their code to FirecREST
* aiida-firecrest: one first task could be to check verdi computer test on CSCS/Eiger. Second: to run a QE calculation. Good to have simple instructions (even internal, for now) on how to setup firecrest.
* aiida tutorial demo: at least link properly the demo from the tutorial, otherwise it's not findable. Do we still want to upload the video?
* https://github.com/aiidalab/aiidalab-qe/issues/355 is actually a aiida-qe issue (CRASH file should be read if the error is not in the main IO MPI process)
    * Jason: also want to mention this one https://github.com/aiidateam/aiida-quantumespresso/issues/887 :)
* AiiDA-qe replacement of parsers and policy for QE version support?
    * SPH: I have a working branch that changes the parsing of `pw.x` to be mainly from XML and just supplements from stdout where necessary (currently it is the reverse). There have been (small) problems with the schemas that I have discussed with Pietro Delugas (see [this PR on their repo](https://github.com/QEF/qeschemas/pull/14)). He says the changes are now final and would like our help with testing. Anyone have time to help with testing the various versions and their schemas? Specifically also the upcoming QE v7.2
* AiiDA-qe: look into new auto parallelism options of QE?
* ACWF repo: paper is going to be shared soon. After it's published we should plan for migration of the package to 2.0
    * SPH: I opened an [issue for this on the repo](https://github.com/aiidateam/aiida-common-workflows/issues/300). Currently we have 6 out of 11 codes with a v2.0 compatible release. There are a 3 packages that seem to have a compatible branch, but just require a PyPI release.



### Specific Agenda Items