- Python 71.3%
- JavaScript 16.3%
- HTML 7.7%
- Shell 1.5%
- SCSS 1.3%
- Other 1.9%
|
Some checks are pending
autoupdate / autoupdate (push) Waiting to run
ci-cd / Code quality and migrations (push) Waiting to run
ci-cd / Tests (backend) (push) Waiting to run
ci-cd / Tests (frontend) (push) Waiting to run
ci-cd / Package and Deploy Services (push) Blocked by required conditions
* fix(frontend): show the real error when submission download fails Downloading from the All Submissions page showed an empty red banner on failure because the error handler only read `response.data.error`. A gateway timeout (502/504) returns an HTML page and DRF errors such as throttling (429) use `detail`, so `error` was undefined and the banner rendered with no text. When the request never reached the server, `response.data` was null and the handler threw a TypeError instead. The handler now falls back from `error` to `detail` to the HTTP status, and reports an unreachable server separately. The GET and POST branches share one callback instead of two identical copies. Co-Authored-By: Claude <noreply@anthropic.com> * ci: pin ci-cd runners to ubuntu-24.04 so Python 3.9.21 installs ubuntu-latest now resolves to Ubuntu 26.04, and actions/setup-python publishes no Python 3.9 builds for it (3.9.21 exists only up to 24.04). Every ci-cd.yml job failed in "Set up CI environment" within seconds, which has broken CI for all pull requests since late October. Pin the four jobs that install PYTHON_RUNTIME_VERSION to ubuntu-24.04 rather than bumping the runtime away from the version it mirrors. Co-Authored-By: Claude <noreply@anthropic.com> * docs(frontend): document the submission download error contract Co-Authored-By: Claude <noreply@anthropic.com> --------- Co-authored-by: Claude <noreply@anthropic.com> |
||
|---|---|---|
| .claude | ||
| .cursor | ||
| .github | ||
| apps | ||
| cloud-agent | ||
| docker | ||
| docs | ||
| evalai | ||
| examples | ||
| frontend | ||
| middleware | ||
| requirements | ||
| scripts | ||
| settings | ||
| static | ||
| tests | ||
| .coderabbit.yaml | ||
| .coveragerc | ||
| .dockerignore | ||
| .eslintrc | ||
| .git-blame-ignore-revs | ||
| .gitignore | ||
| .npmrc | ||
| .pre-commit-config.yaml | ||
| .presidiocli | ||
| .pylintrc | ||
| .readthedocs.yaml | ||
| AGENTS.md | ||
| bower.json | ||
| CODE_OF_CONDUCT.md | ||
| codecov.yml | ||
| docker-compose-production.yml | ||
| docker-compose-staging.yml | ||
| docker-compose.yml | ||
| gulpfile.js | ||
| karma.conf.js | ||
| LICENSE | ||
| manage.py | ||
| package.json | ||
| pyproject.toml | ||
| pytest.ini | ||
| README.md | ||
| setup.cfg | ||

EvalAI is an open source platform for evaluating and comparing machine learning (ML) and artificial intelligence (AI) algorithms at scale.
In recent years, it has become increasingly difficult to compare an algorithm solving a given task with other existing approaches. These comparisons suffer from minor differences in algorithm implementation, use of non-standard dataset splits and different evaluation metrics. By providing a central leaderboard and submission interface, we make it easier for researchers to reproduce the results mentioned in the paper and perform reliable & accurate quantitative analysis. By providing swift and robust backends based on map-reduce frameworks that speed up evaluation on the fly, EvalAI aims to make it easier for researchers to reproduce results from technical papers and perform reliable and accurate analyses.
Features
-
Custom evaluation protocols and phases: We allow creation of an arbitrary number of evaluation phases and dataset splits, compatibility using any programming language, and organizing results in both public and private leaderboards.
-
Remote evaluation: Certain large-scale challenges need special compute capabilities for evaluation. If the challenge needs extra computational power, challenge organizers can easily add their own cluster of worker nodes to process participant submissions while we take care of hosting the challenge, handling user submissions, and maintaining the leaderboard.
-
Evaluation inside environments: EvalAI lets participants submit code for their agent in the form of docker images which are evaluated against test environments on the evaluation server. During evaluation, the worker fetches the image, test environment, and the model snapshot and spins up a new container to perform evaluation.
-
CLI support: evalai-cli is designed to extend the functionality of the EvalAI web application to your command line to make the platform more accessible and terminal-friendly.
-
Portability: EvalAI is designed with keeping in mind scalability and portability of such a system from the very inception of the idea. Most of the components rely heavily on open-source technologies – Docker, Django, Node.js, and PostgreSQL.
-
Faster evaluation: We warm-up the worker nodes at start-up by importing the challenge code and pre-loading the dataset in memory. We also split the dataset into small chunks that are simultaneously evaluated on multiple cores. These simple tricks result in faster evaluation and reduces the evaluation time by an order of magnitude in some cases.
Goal
Our ultimate goal is to build a centralized platform to host, participate and collaborate in AI challenges organized around the globe and we hope to help in benchmarking progress in AI.
Installation instructions
Setting up EvalAI on your local machine is really easy. You can setup EvalAI using docker: The steps are:
-
Install docker and docker-compose on your machine.
-
Get the source code on to your machine via git.
git clone https://github.com/Cloud-CV/EvalAI.git evalai && cd evalai -
Build and run the Docker containers. This might take a while.
docker-compose up --buildBy default, this starts only the required services (
db,sqs, anddjango).
If you need worker services, start them using:docker-compose --profile worker up --build -
That's it. Open web browser and hit the URL http://127.0.0.1:8888. Three users will be created by default which are listed below -
SUPERUSER- username:
adminpassword:password
HOST USER- username:hostpassword:password
PARTICIPANT USER- username:participantpassword:password
If you are facing any issue during installation, please see our installation troubleshooting page.
Setup Instructions for EvalAI Documentation
If you're looking to contribute to EvalAI Documentation, refer to the docs specific setup instructions in docs/README.md to set up the docs builder locally.
Citing EvalAI
If you are using EvalAI for hosting challenges, please cite the following technical report:
@article{EvalAI,
title = {EvalAI: Towards Better Evaluation Systems for AI Agents},
author = {Deshraj Yadav and Rishabh Jain and Harsh Agrawal and Prithvijit
Chattopadhyay and Taranjeet Singh and Akash Jain and Shiv Baran
Singh and Stefan Lee and Dhruv Batra},
year = {2019},
volume = arXiv:1902.03570
}
Team
EvalAI is maintained by Rishabh Jain, Akansha Jain, and Dhruv Batra.
Past contributors
A non-exhaustive list of past contributors includes: Deshraj Yadav, Ram Ramrakhya, Gunjan Chhablani, Akash Jain, Taranjeet Singh, Shiv Baran Singh, Harsh Agarwal, Prithvijit Chattopadhyay, and Devi Parikh.
Contribution guidelines
If you are interested in contributing to EvalAI, follow our contribution guidelines.
