# Technical Monitoring (notes) - 2024 April 09 :::info - **Date:** April 09, 2024, 12 pm EST - **Participants:** \<insert initials> ::: :::success ## Agenda 1. *MRIQC* under very active development: * Target: OE's oral at ISMRM (May 7, 2024) * Released 23.1.0 and a 24.0.0rc1 (probably 24.0.0rc2 by the time of the meeting). * Had to activate 2 factor authentification for the nipreps user in Pypi - * PRs of particular interest: * [#1239](https://github.com/nipreps/mriqc/pull/1239) changing *PyBIDS*' `BIDSLayout.__repr__()` -- great speed-up without cost to *MRIQC*. * [#1238](https://github.com/nipreps/mriqc/pull/1238) revised logging, now creating a log under `<output_dir>/logs/mriqc.log` and writing messages with colors on stdout. * [Example of logs in standard output](https://app.circleci.com/pipelines/github/nipreps/mriqc/1211/workflows/8fae8076-6b3d-40fe-8c51-f6c5fb8301a9/jobs/7321/parallel-runs/0/steps/0-110) * [Example of file stored under `logs/`](https://output.circle-artifacts.com/output/job/cdb97ddc-78ae-42af-9c4e-feeb05d30637/artifacts/0/tmp/t1w/derivatives/logs/mriqc.log) * A few new DWI metrics ([#1233](https://github.com/nipreps/mriqc/pull/1233), [#1229](https://github.com/nipreps/mriqc/pull/1229), [#1228](https://github.com/nipreps/mriqc/pull/1228), [#1227](https://github.com/nipreps/mriqc/pull/1227), [#1226](https://github.com/nipreps/mriqc/pull/1226), [#1225](https://github.com/nipreps/mriqc/pull/1225), [#1224](https://github.com/nipreps/mriqc/pull/1224)) * Migrated to ruff. * Added exclusion of short DWI runs ([#1240](https://github.com/nipreps/mriqc/pull/1240)). There is a related PR by Chris for BOLD ([#1120](https://github.com/nipreps/mriqc/pull/1120), however, we got stuck there with the datalad node). 2. *eddymotion* * Improvements to packaging, linting, etc. by Elodie and Jon Haitz. 3. Hackathon projects - OE has been brainstorming this morning, see https://hackmd.io/@NiPreps-technical-monitoring/2024-hackathon-agenda/edit * The idea behind the new approach to the brainstorming is to focus more on what kind of *teams* we can build and creating *working packages* that are realistic and of interest to those teams (or sub-teams). ::: ## Notes ### Item 1 * A note ### Item 2 * A note