---
# System prepended metadata

title: AiiDAlab Meeting Notes 2023-02-15
tags: [Meeting]

---

# AiiDAlab Meeting Notes 2023-02-15

###### tags: `Meeting`

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

1. Input status updates `5 min` or before the meeting
1. Based on the roadmap sprint and sprint update by assignee `15 min`
2. Catch up round `3 min` max each
3. Technical discussions

- **Participants:**
    - Jason [PSI] (jy)
    - Sasha [Empa] (ay)
    - Xing [PSI] (xw)
    - Giovanni [PSI] (gp)
    - Carlo [Empa] (cp)
    - Daniel [ISPG] (dh)
    - Andres [Empa] (ao)
    - Dou [EPFL] (dd)
    
- **Host:** jy
- **Reference:** 
    - [Last week meeting minute](/s/template-meeting-note)
    - Roadmap: https://github.com/orgs/aiidalab/projects/7/views/9

:::

[TOC]


### Catch-up round

*Max. 3 minutes each*

Sasha:
- MFA
    + Schedule a meeting with Maxime from CSCS to discuss an extension of key-pair lifetime. It should be one week and not one day.
    + Trying to request 1-year long keys for the active aiidalab users, see [CSCS ticket](https://jira.cscs.ch/plugins/servlet/desk/portal/1/SD-57619).
- Setup dev-aiidalab server (ready to be tested and used for the migration).
- Discuss a bit the interface of the aiidalab app installations
- Production release of the AWB?

Jason:
- Is it a good practice to combine some project managements in to AiiDAteam?
    - mailing list by sub-group?
    - Roadmap using team-compass?
- Do we need to move bandsplot-widget to `aiidalab/bandsplot-widget`?
- The THEOS test is not very active, how to push?
- Workflow issue "bad fermi energy" encountered in running band structure workflow by QeApp https://github.com/aiidateam/aiida-quantumespresso/issues/887
- Helping to migrate apps, touch base with app developers and sit together? I spend 30 mins with Daniel Marchand from SINTEF and makes migrated done.

Giovanni:
- created a few issues on usability after testing the QE app on the EPFL server. I feel others might encounter them as well, so I would try to include (some of) them in the next sprint. Important discussion: audience of the App. I feel it's for non-AiiDA users (and possibly non-QE users) who still however know what it means to do a SCF/relax/bands/DOS calculation, so name should be clear to them. Still, for QE and/or AiiDA experts, if they want to check what has been going on, they should be understanding the details (e.g. see the raw QE files, see the name of AiiDA workflows and nodes etc.). But this should not be the primary thing that our main audience should see. Example: instead of `PwBandsWorkChain` say `DFT self-consistent and band workflow (PwBandsWorkChain)`
- Deployment inside PSI
  - VM ready (dev-aiidalab), and some deployment was performed already
  - SSL certificates issue - maybe not critical in the testing phase
  - main outcome for me: is the VM OK (fast IO, fast CPU/mem, etc) for 20+ users? I need to understand if it's usable or we should buy some machines, then compare the costs of bare-metal machine vs VM.
  - have also the code registry having the codes in merlin
- CSCS 2FA follow up
  - AiiDAlab: 1 year token?
  - ask for >1 day for normal tokens?
  - create simple app to manage tokens (Carlo/Sasha)


### Tasks not assigned yet or long-term projects or misc

*(The list of tasks that come to your minds that might be important but you don't know who should do or you don't want to do. The items will either 1. being assigned to a specific developer with clear priority in his list in next section (for short-term tasks); 2. go to the roadmap and assigned to a specific developer; 3. or just being ~~removed~~)*

- Announce the new QE app release with compatible with AiiDA 2.0. (who announce? ddl?)
- Have some pre-run calculation to show to the reviewers. (who run? in which server? ddl?)