---
# System prepended metadata

title: AiiDA Team Meeting 2024-03-07
tags: [team meetings]

---

# AiiDA Team Meeting 2024-03-07

###### tags: `team meetings`
###### time: 14:00 CET

[TOC]

### Present

* Julian
* Ali
* Sebastiaan
* Kristjan
* Xing
* Miki


### Catch-up round

*Max. 3 minutes each*

Sebastiaan:
 * [ORM: Switch to `pydantic` for code schema definition](https://github.com/aiidateam/aiida-core/pull/6190): Last chance, I am going to merge this early next week unless there is opposition.
 * [ORM: Use pydantic to specify a schema for each ORM entity](https://github.com/aiidateam/aiida-core/pull/6255): I would like to move ahead with this proposal. It is backwards compatible, so we don't risk to break anything. But it would be good to have feedback to see if it provides the required functionality and the UI/UX makes sense.
 * [Refactor: Abstract message broker functionality](https://github.com/aiidateam/aiida-core/pull/6303): This is a precursor to make it easy to run AiiDA without RabbitMQ. It essentially centralizes all RabbitMQ related code to a `Broker` class. This already prepares it so it is made pluginnable, possibly allowing plugins to provide different broker implementations in the future. For now, I also implement it for a case *without* a broker. The open question is whether this is necessary or whether it is easier in the code to have the `Manager.get_broker()` method just return `None` and have the caller explicitly check.
 * [CLI: Add the `verdi blitz` command](https://github.com/aiidateam/aiida-core/pull/6305): Builds on top of the previous PR. The `verdi blitz` command creates a profile using the `core.sqlite_dos` storage plugin and the no-comms broker and so it requires no services. This makes it a lot easier to use and enables user to quickly try out AiiDA. Now `pip install aiida-core && verdi blitz` are sufficient to have an environment that is ready for use. Any good ideas what the name should be? `blitz` is just a working title. Didn't think `verdi quickstart` was a good idea since it is easily confused with `verdi quicksetup`.

Julian:
* Making Renkulab work again
    * Updated AiiDA version and provided new docker image
    * Which database setup? Postgres not working due to missing `sudo` access in post-setup on Renku.
    * `verdi quicksetup` only allows Postgres?
    * Currently using `core.sqlite_dos` via `verdi profile setup`, but getting `Critical: ... NotImplementedError` on archive import -> Missing migration of database?
    * Just for inspection of archive, RabbitMQ likely not needed
    * Include AiiDA setup in Docker image build? Would either require rebuilding image at start-up (probably undesired) or with fixed username and mail when image is provided
    * Could be a use case for `blitz` setup
![image](https://hackmd.io/_uploads/BJ6ScEwT6.png)
* Doc: [Updated and improved the cheat Sheet](https://github.com/aiidateam/aiida-tutorials/issues/345#issuecomment-1973692737) (maybe one more day to finish with it)
* `verdi calcjob/workchain dump` [PR](https://github.com/aiidateam/aiida-core/pull/6276) in principle ready to be merged
    * `yaml` dumping still unclear -> Wait until `pydantic` PR merged?
    * Tests missing

Ali:
* `aiida-firecrest`:
    *  implemented bulk transfer using `aiohttp` and `async`
    *  collecting issues to be raised to Firecrest team
    *  trying to understand how monitoring works
* Doc: referencing to tutorials is done.

Kristjan:
* https://github.com/aiidateam/aiida-core/pull/6069
    * json file that includes: profile_name, profile_uuid, and storage_backend
        * when making backup, check that json file matches
        * if no json file, make sure folder is empty and create the json file
    * logging decision ?


Xing:
* try to finished these PRs [#6206](https://github.com/aiidateam/aiida-core/pull/6206), [#6203](https://github.com/aiidateam/aiida-core/pull/6203).


### Specific Agenda Items