Zoom Link - 13:00-14:00 CET
Collect comments on previous meetings minutes (2024-01-19)
¶ Updates and Issues
- Infrastructure themes
- Operations themes
- Statistical themes
- Feedback from the ATHLETE GA
- Date: 2024-03-01, 13:00-14:00 CET
- Chair: Yannick Marcon
- Focus: Infrastructure
Demetris Avraam, Yannick Marcon, Stuart Wheater, Mariska Slofstra, Dick Postma, Florian Schwarz, Majda, Sofia Siampani, Andrei Morgan, Marije van der Geest
¶ Updates and Issues
General remarks: Florian: put zoom link of this meeting in calendar > Marije will do this.
Mariska (Armadillo):
- Release Armadillo 4
- Upcoming developments include audit logging in UI and views on the data
- Arrow issue → hope to release a version of Armadillo on cran without arrow dependency
- Question Yannick: arrow on R server side, arrow not on cran anymore? Will it be in the archive?
- Mariska: yes they will remove arrow, all maintainers with dependencies on arrow got an email, maintainers of arrow working on a fix.
- Dick: remove whole arrow packages, also from archive, because there is a binary file that violates the rules of cran.
- Armadillo >3.4 not running on systems of collaborators, trying to figure it out what is happening.
Yannick (Opal):
- Working on upgrading to java 17
Demetris:
- Attented ATHLETE GA and presented all ds packages. Already many people in the project that use DS. There will be new researchers starting soon as well.
- Issues were presented, most already fixed or working on. Summary:
- Updating servers takes time, mostly done by molgenis team, so sometimes there is a bit of a wait
- Updates packages takes time
- Simple manipulations complicated > Tim Cadman is planning to extend dsHelper?
- Some servers give a time out while working on the central analysis server
- You have to modify your script when a server goes down. Suggestion to continue analysis and get only a notification/error message for the cohort that is down
- Imputation (dsmice)
- Wary to put these things in dsBase, keep this simple and make another package
- Monitoring
- Andrei: Coral developed a tool, adapt that?
- Florian: only works for docker installations, how does it work with different installations
-
<ADD OTHER POINTS>
Roadmap for developments
- Google drive sheet with 1. new functions, 2. new packages, 3. modifications to existing packages
- Stuart: deprication of functions > workout how to deal with that.
- Andrei: put the list on the wiki, show people what is comping and prevent them for developing things themselves are already being worked on.
- Demetris: looking into if we can put this on the wiki (interactive table?)
- Suggestions for dsBase
- Andrei: Should we put everything in dsBase? Are these basic things + we mess people's research up with many changes.
Request to help with implementing developments, Demetris will start a new function soon and will have limited time!
Stuart:
- New DataSHIELD profile “Beach”: rock profile, includes dsBase and dsSurvival.
- Proposal on disclosure issues: if there is a potential issue discuss it in te community how to respond to that. See updates for link.
- Keep community informed and tools to deal with this.
- Comments Andrei: 1. we need an interim process before we agree to a full process. 2. It would be good to refer to existing community structure we have (acknowledge potential disclosure, inform steering group or tech core group > transparency). 3. Make it clear to the outside world who to contact within the community in case of a disclosure issue. 4. Notification within 24 hours to make clear it is acted upon.