Evaluating the pipeline stability though the libmath fuzzy environment #201
Description
Project info
Evaluating the pipeline stability though the libmath fuzzy environment
Title:
Evaluating the pipeline stability though the libmath fuzzy environment
Project lead:
Ali Salari: @ali4006
Greg Kiar: @gkiar
Valerie Hayot: @ValHayot
Yohan Chatelain: @yohanchatelain
Timezone:
UTC-4
Hub:
The Americas
Description:
Data analysis pipelines are known to be impacted by the operating system updates, presumably due to the creation, propagation, and amplification of numerical noises. These are uncontrolled noises that are originated in updates of low-level libraries by third-party developers.
In practice, these numerical instabilities are caused by truncation and round-off errors due to
the precision limitation of the floating-point arithmetic.
The finite precision of the floating-point numbers leads to represent an approximation of
a real number that may be different on the computers with various precision formats.
A possible method to investigate operating system related effects more comprehensively
is to introduce controlled numerical perturbations in the math library functions (libmath), which could be done by introducing noise in floating-point computations through Monte-Carlo Arithmetic (MCA) using the Verificarlo tool.
For the hackathon we'll be looking to test the validity of the instrumented libmath library functions and also evaluate the stability of the existing neuroimaging pipelines.
Link to project:
https://github.com/gkiar/fuzzy
Mattermost handle:
@ali.salari, @gkiar, @valeriehayot, @yohan.chatelain
Goals for the OHBM Brainhack
Validating the instrumented math functions and evaluating the stability of the FSL tool
Good first issues:
- Preparing tests to validate the instrumented libmath library functions
- Finding neuroimaging pipelines to evaluate
Skills:
Any of the following skills would be useful for the project.
- Python and c++ programming languages
- Familiar with FSL tool
- Familiar with Monte Carlo Arithmetic (MCA) technique and Verificarlo tool
Chat channel:
Video channel:
Please have a look at the Mattermost channel (pinned posts) for the URL of the video channel, or alternatively, please contact to @ali.salari, @gkiar, @valeriehayot, @yohan.chatelain
on Mattermost.
Image for the OHBM brainhack website
Project submission
Submission checklist
Once the issue is submitted, please check items in this list as you add under 'Additional project info'
Please include the following above (all required):
- Link to your project: could be a code repository, a shared document, etc. See here
- Include your Mattermost handle (i.e. your username). If you do not have an account, please sign up here.
- Goals for the OHBM Brainhack: describe what you want to achieve during this brainhack. See here.
- Flesh out at least 2 "good first issues": those are tasks that do not require any prior knowledge about your project, could be defined as issues in a GitHub repository, or in a shared document, cf here.
- Skills: list skills that would be particularly suitable for your project. We ask you to include at least one non-coding skill, cf. here.
- Chat channel: A link to a chat channel that will be used during the OHBM Brainhack. This can be an existing channel or a new one. We recommend using the Brainhack space on mattermost, cf. here.
- Video channel: Please create a video channel that will be used during the OHBM Brainhack and share it in your chat channel above. This can be an existing channel or a new one. For instance a jitsi meet room, cf. here.
- Provide an image of your project for the OHBM brainhack website
You can also include information about (all optional):
- Number of participants, cf. here
- Twitter-size summary of your project pitch, cf. here
- Set up a kanban board on your repository to better divide the work and keep track of things, cf here
- Project snippet for the OHBM Brainhack website, cf. here
We would like to think about how you will credit and onboard new members to your project. We recommend reading references from this section. If you'd like to share your thoughts with future project participants, you can include information about (recommended):
- Specify how will you acknowledge contributions (e.g. listing members on a contributing page).
- Provide links to onboarding documents if you have some.