# AiiDAlab Meeting Notes 2024-02-15

###### tags: `Meeting`

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

- [25 min] Go through
- [Urgents of Roadmap](https://github.com/orgs/aiidalab/projects/15/views/2) (click me)
- [priority panel of Roadmap](https://github.com/orgs/aiidalab/projects/15) (click me)

- [5 min] Prepare session: go to ["hackmd notes"](https://hackmd.io/team/aiidalab?nav=overview) (click me) for general issues to discuss.

- [~30 min] Hackmd session: The catch up round for everyone and bring general topics about AiiDAlab. Buffer for discussion: Continue of hackmd session if not finished and focus on one or two general discussion.
- main purpose is to make sure all participants speak and give update.

- **Participants:**
Before the meeting, the host should check and update the list below.

- Jason [PSI] (jy)
- Sasha [Empa] (ay)
- Xing [PSI] (xw)
- Giovanni [PSI] (gp)
- Marnik [PSI] (mb)
- Carlo [Empa] (cp)
- Daniel [ISPG] (dh)
- Andres [Empa] (ao)
- Miki [PSI] (mib)
- Edan [PSI] (eb)

- **Host:** jy

:::

[TOC]

### Catch-up round

*Max. 3 minutes each*

Jason:
* AiiDAlab demo server:
* The QEapp container start time > 3 mins.
* Memory leak or just the process mornitor widget keep on collecting text but not cleaned up?
* The cull strategy and data destroy policy.
* ipyoptimade:
* Do we remove it from AWB? See the discussion [when it added into AWB](https://github.com/aiidalab/aiidalab-widgets-base/pull/554#issuecomment-1925487019).
* Do not make PR from repo to repo, but always from fork.
* Get many requests for Copilot integration of AiiDAlab on GitHub, what happened?
* Edan bring up the question: why in aiidalab-launch, the `~/.conda` folder need to be seperately mounted to a volume? Can it be just included in home volume mount?
* We should add extra infos in the email reply to the access request of MC, to redirect people to following AiiDA Discourse and we can get them on board once the demo deployment is ready.
* demo server on Azure:
* ORCID as Oauth. There is an issue that ORCID is for the individual user, we can not get a public OAuth ID for the team. (https://info.orcid.org/documentation/api-tutorials/api-tutorial-get-and-authenticated-orcid-id/, and more [detail](https://github.com/jupyterhub/oauthenticator/pull/657/files) on how to set ORCID for Jupyterhub.)

Sasha:
* AiiDAlab demo server (demo.aiidalab.io): problems with Azure Terraform deployment.
* We had a "Deployment meeting" where we agreed on how to move forward. More on that [here](https://hackmd.io/@aiidalab/SysVrwC9p).
* aiidalab-launch on windows? Shall we recommend WSL as a default path?
* I will have a look: https://aiidalab-qe.readthedocs.io/installation/access_aiidalab/container.html

Edan:
* Progress on QB widget
* Will soon export Group widget from AiiDAlab-Aurora
* Easy test case for Jason's widgets-for-aiida concept
* Will use this in QB widget (easy grouping of query results)
* Learning a good deal about best-practices for MVC design from QB widget work
* Will present soon

Xing:
* Integation of AiiDAlab and Materials Cloud Archive, [aiida-archive-inspect app](https://github.com/superstar54/aiida-archive-inspect/pull/1) [**First version**]
* click a url including the record_id and archive filename, e.g., http://localhost:8897/apps/apps/aiida-archive-inspect/load_overview.ipynb?file=export_PdTe_11_12_KKR.aiida&record_id=1801&appmode_scroll=0, the `openapp` will open the `aiida-archive-inspect` app, and download the file, import the data, and show the statistic data.
* Provide a button to open a normal jupyter-notebook with the data loaded.
* Next steps:
* use a temporary profile
* inspect how to authticate the user for online services
* add the AiiDAlab icon for MC archive entry.

* QEapp XPS plugin [PR](https://github.com/aiidalab/aiidalab-qe/pull/518) is merged.
* Todo: update the XPS doc PR
* [WEAS-widget](https://github.com/superstar54/weas-widget): A widget to visualize and **edit** atomistic structures in Jupyter Notebook.

Peter:
* XAS plugin demonstration video coming soon (BIG-MAP requirements).
* Upload location to be confirmed shortly (BIG-MAP AppStore page?).
* Final check of BIG-MAP requirements to be done tomorrow
* XAS plugin and doc **Nice work!** (xw)