SENSORIUM is a competition on predicting large scale mouse primary visual cortex activity. We will provide large scale datasets of neuronal activity in the visual cortex of mice. Participants will train models on pairs of natural stimuli and recorded neuronal responses, and submit the predicted responses to a set of test images for which responses are withheld.
Join our challenge and compete for the best neural predictive model!
For more information about the competition, vist our website.
Have a look at our White paper on arXiv, which describes the dataset and competition in detail.
June 20, 2022: Start of the competition and data release.
Oct 15, 2022: Submission deadline.
Oct 22, 2022: Validation of all submitted scores completed. Preliminary winners are announced. Rank 1-3 in both competition tracks are contacted to provide the code for their submission.
Nov 5, 2022: Deadline for top-ranked entries to provide the code for their submission.
Nov 15, 2022: Winners contacted to contribute to the competition summary write-up.
Below we provide a step-by-step guide for getting started with the competition.
- install docker and docker-compose
- install git
- clone the repo via
git clone https://github.com/sinzlab/sensorium.git
You can download the data from https://gin.g-node.org/cajal/Sensorium2022 and place it in sensorium/notebooks/data
.
Note: Downloading the files all at once as a directory does lead to unfortunate errors. Thus, all datastes have to be downloaded individually.
cd sensorium/
docker-compose run -d -p 10101:8888 jupyterlab
now, type in localhost:10101
in your favorite browser, and you are ready to go!
We provide notebooks that illustrate the structure of our data, our baselines models, and how to make a submission to the competition.
Dataset tutorial: Shows the structure of the data and how to turn it into a PyTorch DataLoader.
Model tutorial: How to train and evaluate our baseline models.
Submission tutorial: Use our API to make a submission to our competition.
If you have any questions, feel free to reach out to us (Contact section on our website), or raise an issue here on GitHub!