---
# System prepended metadata

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

---

# AiiDAlab Meeting Notes 2023-02-01

###### tags: `Meeting`

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

1. General Updates (Based on Roadmap) `30 min`
1. Technical discussions (This time we'll focus on XX) `30 min` 

- **Participants:** (Remove who not participate)
    - Jason [PSI] (jy)
    - Sasha [Empa] (ay)
    - Xing [PSI] (xw)
    - Giovanni [PSI] (gp)
    - Marnik [EPFL] (mb)
    - Carlo [Empa] (cp)
    - Daniel [ISPG] (dh)
    - Andres [Empa] (ao)
    - Dou [EPFL] (dd)
    
- **Host:** jy
- **Reference:** 
    - [Last week meeting minute](https://hackmd.io/DIuDvxP9TwWyKQXf2fXhLw)
    - Roadmap: https://bit.ly/3HyKx63

:::

[TOC]

### Tasks not assigned yet

*(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?)
- Deploy AiiDAlab on PSI. (who? when?)


### Catch-up round

*Max. 3 minutes each*

Jason:
 * 1st RP:
     * [x] [aiidalab-launch #166](https://github.com/aiidalab/aiidalab-launch/pull/166) Polish aiidalab-launch default profile settings, The documentation needs to lead to the working path. (ddl: 2023-02-01)
     * [x] Clean up GitHub roadmap. (ddl: 2023-02-01)
     * [x] Writing down the hands-on for THEOS testing, in-person test with Taylor. (ddl: 2023-02-01, co-author with Xing)
     * [x] MarketPlace AiiDAlab DO k8s deployment fix and online. (ddl: 2023-02-01)
     * [ ] QeApp repo: take screeshot even the test stuck and fail. (ddl: 2023-02-15)
     * [x] microk8s deployment template: [aiidalab-microk8s-deploy](https://github.com/aiidalab/aiidalab-microk8s-deploy)
 * TBD:
    * ~~Do we need a mailing list?~~
    * Steps of removing AWB as an app.
    * Bandsplot dos issue, any progress? https://github.com/osscar-org/widget-bandsplot/issues/24 @dou (Urgent)


Sasha:
* Worked on [viewer representations PR](https://github.com/aiidalab/aiidalab-widgets-base/pull/373). Tested together with Carlo. Welcome to have a look.
* AiiDAlab tutorial for Empa & IBM people
* Need to switch the AiiDAlab account to icp021 from icp010. Asked Stephano Gorini to extend icp010 project till the end of March. Tentatively, it is going to be extended.
    * GP: I don't think it makes a lot of sense, it's a lot of work for nothing, can they just rename the account?
    * Sasha: we need to update machine to AiiDA-2.0 anyways. It makes no difference in terms of load.
* Policy for the main machine for non-Marvel members. See the email from Adolfo Avella
* TODO:
    * agree on the release timeline and release policy in general

Xing:
- wrote the hands-on for THEOS testing with Jason.
- updated the aiidalab website https://aiidalab.github.io/, ready to go public.
- todo: replace the aiidalab link on materials cloud web site https://www.materialscloud.org/work/aiidalab

Giovanni:
- add examples to load to QE app to make it very easy even without CPU/running
- Replace big QE logo (turned out not to be intuitive) to a list of notebooks with links.
- Have a demo instance (where we delete everything after say 12 hours, and this is clearly written) on Azure using the K8S recipes
    - Check costs
    - Ensure there is a clear hard limit on costs
    - link AAI to something where there is no risk of people mining bitcoins (SwitchAAI?)
    - Have everything needed for a demo already there, no need for the user to go an install (use a custom image to reduce startup times?)
- how to manage deployments, how many to have:
  - drop the EOSC one?
  - how many users need to be migrated (really, i.e. actively logged in multiple times recently? I guess few?) from the MC one? We need something working well to be used easily by any MARVEL member and/or reviewer by mid March. Suggestion: move the old machine to legacy-aiidalab, create a new one with the new software stack, directly support migrating those few users
- aiidalab website status? Date for switch? (Add also MC news in the timeline)

Daniel: 
 - Pinning the PostgreSQL version
 - AWB 2.0 when? What are the blockers?

