# AiiDAlab Meeting Notes 2023-04-12

###### tags: `Meeting`

:::info
- **Location:** https://psich.zoom.us/j/69116696576 *(Please request password on slack)*
- **Date:** April 12th, 2023 14h (CET)
- **Agenda**

- [5 min] Prepare session: update the status in the [current sprint panel](https://github.com/orgs/aiidalab/projects/7/views/9) [1] and go to [hackmd notes](https://hackmd.io/team/aiidalab?nav=overview)[2] if you have general issues to discuss.

- [20 min] Roadmap session: Go through current sprint by each developers in the current sprint, the speaker share the screen and go through the tasks they have been assigned. The goal is to let other team members notice what are the new things/changes to the AiiDAlab. The meeting host (the host who the project manager need to go to roadmap and rearrange the issues in his own opinion) then open the [priority panel](https://github.com/orgs/aiidalab/projects/7/views/2) [3] set for the next sprints and assign the tasks to developers. Or move the issue to lower priority if it is not urgent. The goal is to let developers have more focus on the coming sprints.

- [~15 min] Hackmd session: Move to Hackmd notes, this is the session where will bring the issues to high priority list of roadmap. The catch up round for everyone and bring general topics about AiiDAlab.

- [~20 min] Buffer for discussion: Continue of hackmd session if not finished and focus on one or two general discussion.

- **Participants:**
- Jason [PSI] (jy)
- Sasha [Empa] (ay)
- Xing [PSI] (xw)
- Giovanni [PSI] (gp)
- Carlo [Empa] (cp)
- Daniel [ISPG] (dh)
- Andres [Empa] (ao)

- **Host:** jy
- **Reference:**
- [Last week meeting minute]([/s/template-meeting-note](https://hackmd.io/lKE9DVcTTcm7cJRVXM2G4g))
- [1] https://github.com/orgs/aiidalab/projects/7/views/9
- [2] https://hackmd.io/b33_dO9HQOCohuNrIB8VOg
- [3] https://github.com/orgs/aiidalab/projects/7/views/2

:::

[TOC]

### Catch-up round

*Max. 3 minutes each*

Jason:
* refactoring the QeApp workchain:
* Arch and plan: https://github.com/aiidalab/aiidalab-qe/issues/383
* Moving workchain into package: https://github.com/aiidalab/aiidalab-qe/pull/379
* Adding test for checking builder from widgets: https://github.com/aiidalab/aiidalab-qe/pull/382

Xing:
* Demo of AiiDAlab with AiiDA REST API, https://docs.google.com/presentation/d/1vUAXN0fgvADSkhXH0bjgEAXlHoePQOeuy5hqNoRZgiA/edit#slide=id.g215ace58908_2_47

### Meeting notes

- Introduce Edan, and everyone to Edan.

Xing give the demo for the restapi integration

- Sasha, in what use case we want to use RestAPI? (Gio: the performance and want to have a lightweight AiiDAlab client.)
- Gio: for performance, collect the querys and discuss with Seb. The text file is ugly don't have nice parser.
- Gio: we need to think about if the aiida engine can be moved out from aiidalab container where the aiida goes, still stay in aiidalab or goes somewhere else, how to easily deploy that?
- Jason: The RestAPI way means that we need an daemon process running in background to handle the RestAPI request, is this convinient? (Gio: we need move to a bit complex to RestAPI but it is worth to do if we can get lots of performance gain.)

Jason give a presentation on the plan to refactoring the architechture of QeAppWorkChain and how it interacts with widgets. (The arch description is in https://github.com/aiidalab/aiidalab-qe/issues/383)

- Gio: The override of parameters functionalities going to be used in the new implementation share the same use case and had been discussed in the ACWF but not actually used there. Can have a extra discussion on how to make it possible and useful in the QeApp case.
- Xing: the setting parameters for report and summary viewer do not need to get from builder but can directly parse from every widgets to avoid lost informations. (Jason: may not be a good solution to interact with all widgets, can follow up discuss offline.)

Round catch for everyone's plan on next phase (within next two month)
- Sasha: app migration, data migration.
- Daniel: release the first stable of the app.
- Andres: tags and hubbard settings.
- Xing: XPS, and XAS combine and integrate to QeApp. (also include the works with Peter.)
- Carlo:
- The stabilizing, the visulizer, need things on how to visulize the charge density etc. +
- The multiple properties calcualtion in the QeApp.
- Mention that the arm64 support is required by students and should be put to high priority. (Jason: we have experience on it for old stack, will work on it ASAP.)
- Gio:
- understand the duplication of between PSI and EMPA, the common widgets etc.
- Add more properties, which bing more impact to the MARVEL.
- In parallel, try the restapi @xing.
- Should start to think about the demo deployment in Azure to having a website to can r