pytorch/ignite

High-level library to help with training and evaluating neural networks in PyTorch flexibly and transparently.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 39 minutes ago
Added to GitGenius on September 17th, 2024
Created on November 23rd, 2017
Open Issues & Pull Requests: 190 (+0)
Number of forks: 715
Total Stargazers: 4,777 (+0)
Total Subscribers: 56 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 10.8 hours
Mean response time: 192.1 days
90th percentile: 453.3 days
Tracked items: 141

How this project is maintained

Around half of the issues opened in the past year never receive a reply. 64% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "question" is answered fastest, typically in under an hour, while "module: metrics" waits about 2 days. Only 3% of issues opened in the past year have been closed. Three people close 87% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 90
New in 7 days: 1
Closed in 7 days: 1
Avg open age: 1,483 days
Stale 30+ days: 85
Stale 90+ days: 65

Recent activity

Opened in 7 days: 1
Closed in 7 days: 0
Comments in 7 days: 1
Events in 7 days: 1

Top labels

  • bug (307)
  • enhancement (290)
  • help wanted (230)
  • question (123)
  • good first issue (101)
  • docs (48)
  • Hacktoberfest (40)
  • ci (39)

Detailed Description

PyTorch Ignite is a high-level library to help with training and evaluating neural networks in PyTorch flexibly and transparently.

Ignite addresses the complexity of implementing training loops by providing abstractions that handle common patterns while remaining transparent about what happens under the hood. The library uses an event-driven architecture where a trainer engine manages the training loop and fires events at key points—epoch start, batch completion, validation steps—allowing users to attach handlers that customize behavior without rewriting core logic. This approach lets developers build sophisticated training workflows by composing simple, reusable components rather than writing monolithic training scripts.

The tool suits projects where you want structured training workflows without sacrificing control or clarity. It works well for researchers and practitioners who need to experiment with different training strategies, metrics, and validation schemes while keeping the training loop logic maintainable and reproducible. Ignite is particularly valuable when you need to integrate multiple metrics, handle distributed training, or coordinate complex interactions between training phases and callbacks.

The project receives issues from both core maintainers and external users, indicating real adoption beyond the immediate team without creating an unsustainable support burden. Maintainers typically respond to new issues and pull requests within a day. Work in the issue tracker centers on enhancements, metrics-related improvements, and user questions, suggesting the community actively shapes the library's direction while the team remains engaged with incoming feedback.