Bring Dev back on track with main#123
Merged
Merged
Conversation
Improved Algonauts 2023 NSD datasets (`Algonauts23_Net2Brain` and `Algonauts23_shared_Net2Brain`): proper metadata files linking fMRI rows to image filenames, NSD IDs, COCO IDs and captions, explicit per-subject ROI availability, and recomputed RDMs for the shared split.
Development
…oints + max + baseline-correction
Add wrapper class CT-RSA for RSA over multiple neural and model timepoints + max + baseline-correction
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Contributing to Net2Brain
Thank you for your interest in contributing! To keep the codebase clean and reviewable, please follow the guidelines below.
Workflow
1. Fork and branch from
developmentAlways branch off from the
developmentbranch — notmain. This keeps the main branch stable and ensures your changes are integrated through proper review.Use a descriptive branch name that reflects what you're working on, e.g.
feature/add-my-modelorfix/rdm-bug.2. Make your changes
Keep your changes focused. One feature or fix per PR makes reviewing much easier.
3. Write a clear PR description
When opening your pull request, please explain:
4. Open a PR into
developmentOpen your pull request against the
developmentbranch — notmain.5. Assign a reviewer
Always assign @ToastyDom as a reviewer.
Questions?
Feel free to open an issue if you're unsure about anything before diving in.