# AiiDA Team Meeting 2024-10-17 ###### tags: `team meetings` ###### time: 14:00 CET [TOC] ### Present * Marnik * Xing * Miki * Elliot * Alex * Giovanni * Julian * Ali ### Catch-up round *Max. 3 minutes each* Marnik: * Coding week notes - Agenda item see below. Miki: * No relevant updates (I mostly worked on aiidalab) - working on `StructureData` issues: [query](https://github.com/aiidateam/aiida-atomistic/issues/47), [kinds detection](https://github.com/aiidateam/aiida-atomistic/issues/46) and [immutability](https://github.com/aiidateam/aiida-atomistic/issues/48). Julian: * [[#6565] Refactor: Add the `_prepare_yml` method to `AbstractCode`](https://github.com/aiidateam/aiida-core/pull/6565): Merged * [[#6584] Add `get_total_size_on_disk` method to `RemoteData`](https://github.com/aiidateam/aiida-core/pull/6584): Calling `listdir_withattributes` method recursively for tree of the `RemoteData`. Used to issue warning about size when dumping remote process data. Takes a while, not sure if this can be made more efficient. * [[#6570] DRAFT: Add `verdi storage dump` and `raw/rich data dumping`](https://github.com/aiidateam/aiida-core/pull/6570): Lots of good input from GM. Will implement those and simplify things. Giovanni: * Mostly testing AiiDA-QE via the AiiDAlab demo server. Some comments/tasks that might also affect the plugin itself. Might be good to coordinate between Xing & co (on the app side) with the AiiDA-QE team (Michael, Timo, Marnik, ...) -> good to get a list of AiiDA-QE tasks, they could be prioritized in the coding week? Jason: * Not too much related to aiida-core. * The failed docker CI test should be fixed by two PRs: [#6581](https://github.com/aiidateam/aiida-core/pull/6581) [#6573](https://github.com/aiidateam/aiida-core/pull/6573), merge them? Xing: * Focused on AiiDAlab in the last few weeks. Nothing to report in aiida-core. Kristjan: * coding week comment: Carlo asked to check some errors in their/our NMR workflows, should I add this as a separate topic? * aiida docs * robots.txt added (https://github.com/aiidateam/aiida-metapkg/pull/9) * https://aiida.readthedocs.io/robots.txt * Google index still not good (maybe requires more time), good to set up google search console to check details * needs to be associated with a gmail account * (aiidateam@gmail.com possibly, but sometimes requires 2FA, and only Giovanni has access i think) * decision - use aiidateam@gmail.com and try to give access to multiple team members. * todo for docs - rank "topics" and "how-to-guides" high in search priority * e.g. searching for "group" doesn't really allow to easily find https://aiida.readthedocs.io/projects/aiida-core/en/stable/howto/data.html#how-to-group-nodes Ali: * Working on: * [Allow for file uploads/downloads to be async](https://github.com/aiidateam/aiida-core/pull/6079/files) * 15 issues are open on `aiida-core` label:priority/important & label:type/bug maybe we can assign people based on the responsibility team * Open PRs: * [PR aiida-core](https://github.com/aiidateam/plumpy/pull/288) * [PR plumpy](https://github.com/aiidateam/plumpy/pull/288) * version check on sqlite C-language [PR aiida-core](https://github.com/aiidateam/aiida-core/pull/6567) Alex: * Working on scicode-widgets and the SwissTwins W&C project, no real aiida-core ### Specific Agenda Items **AiiDA coding week:** Notes (WIP): https://hackmd.io/wvjf2VYBTWuYbkls0Y-I5g Documents on Google drive: https://drive.google.com/drive/folders/1tZ-TQSIxBO9nx6Ml5huyTy01WWx2RpkA * Dates: 18-22 Nov * Location: Leysin - [Hotel Central Residence](https://www.hotelcr.ch/accueil). * [Participants](https://docs.google.com/spreadsheets/d/1K8yj3nOqPkT_pd3lHQbs3MPdD4KTTzzRXAIe0JOi65U/edit?gid=0#gid=0): Still some maybe's - Deadline 5 Nov for final list of participants and when they will stay. @giovannipizzi can you forward mails of the people you contacted and I can hunt them down? * Topics: Alex already worked on this quite a bit (thanks!): see [the HackMD notes](https://hackmd.io/wvjf2VYBTWuYbkls0Y-I5g#Suggestions-for-program). Still hashing some things out, also re the schedule.