---
# System prepended metadata

title: NiReports initial meeting for NiPreps Hackathon 2022

---

# NiReports initial meeting for NiPreps Hackathon 2022
**Date:** 9th June, 2022
**Start Time:** 4pm GMT+1([Check your time zone](https://arewemeetingyet.com/London/2022-06-09/16:00/NiReports%20meeting))
**End Time:** 5pm GMT+1
**Attendees:** 
-- Eilidh MacNicol (contact: eilidh.macnicol@kcl.ac.uk)
-- Oscar Esteban
-- Céline Provins
-- Chris Markiewicz
-- Zvi Baratz
-- Daniel Halls
-- Dhritiman Das
-- Guiomar Niso

**Apologies:**
-- Lennart Frahm

## Meeting Objectives
This meeting intends to give context to and set targets for the `NiReports` project of the NiPreps 2022 hackathon. The expected outcomes of the meeting are:

- Meet each other ahead of 24th June
- Discuss the role of `NiReports` (in `NiPreps`and beyond)
- Propose milestone targets to achieve on 24th June

## Agenda
- Welcome and introductions
- Introduction to [NiPreps](http://www.nipreps.org)
- `NiWorkflows` - NiPreps' existing reporting and visualisation utilities
- Potential obstacles
- Plan of action
- Any Other Business

*Please contact @eilidhmacnicol to add items to the agenda*

## Notes and Decisions
- MRIQC to import NiReports (existing MRIQC reportlets to migrate into NiReports)
- Issues to be addressed on the day (and before) are opened in the [NiReports milestones](https://github.com/nipreps/nireports/milestone/1)
- Work to put into packaging vs identifying code
- Dependencies:
-- Drop PyBIDS as a dependencies (if possible - might not be an achievable goal for one day)
--NiLearn is the only large non-standard dependency; matplotlib and seaborn dependencies should also be explicitly listed
-- [Oscar's notebook code](https://github.com/nipreps/niworkflows/blob/master/niworkflows/viz/notebook.py) vs [Nanslice](https://github.com/spinicist/nanslice)
- Environment:
-- Python 3.8 (maybe 3.9) - most recent Python version.
-- We should avoid Docker as an environment, using CI to test across all versions.
- Identification and addressing bugs as we go
-- CI (PyTest) set up early so that it's clear there is a failure
-- (ideally before day of; CM might need to do it in the morning)
- Ideas for new reportlets?
- Documentation in jupyterbook
-- following [Numpydoc](https://numpydoc.readthedocs.io/en/latest/format.html)  standard for docstrings

## Action Items
- CM has added everyone on the call to github team to allow access
- ZB set up issue for CI set up
- OE define structure (module for reportlets and another for visual report system; separate code)
- OE added documentation issue
- EM Circulate a doodle poll for meeting next week

