SciML/NeuralPDE.jl
Physics-Informed Neural Networks (PINN) Solvers of (Partial) Differential Equations for Scientific Machine Learning (SciML) accelerated simulation
In plain words
Only 4 outside PRs in the last four months, too few to rate.
Outside PRs merged
Not enough data
2 merged, 2 closed, 0 still open
First human reply
Not enough data
median of 4 outside PRs, 0 unanswered
Outside PRs opened 30 to 120 days ago, so each has had time to be answered. A figure needs at least 5 pull requests, otherwise it reads "Not enough data". How this is calculated · A number looks wrong?
Your first steps here
If you have never contributed to this project, do these in order.
- 1
Read the README
No contributing guide was found, so the README is where setup is explained.
Open the README - 2
Find something small
No first issue is free right now. Look for a typo, a missing test or an unclear error message, or ask where help is wanted.
Browse open issues - 3
Know where to ask
Questions go to the project's zulip, or on the issue itself. Not in private messages.
Open it - 4
Open a small pull request
Link the issue in it. Too few outside pull requests here to say how long a reply takes.
What happens to an outside pull request
Every pull request opened by someone outside the core team, 30 to 120 days ago.
- Opened by outsiders4100%
- Got a human reply4100%
- Merged250%
Time to first reply
Not enough data: fewer than 5 outside pull requests in the period.
The last 52 weeks
Outside pull requests opened each week, and how many of them have been merged.
Starter issues
Issues labelled for beginners, with their real state. Available means open, unassigned, no linked pull request, nobody has claimed it in the last 14 days, and it was updated in the last 60 days.
- Available
- 0
- Claimed
- 0
- Has a pull request
- 0
- Stale
- 3
- StaleHelping to solve complex system of DAE by NeuralPDE.#721
- StaleInteractive plot script analysis of results#331
- StalePINNs Lorenz param estim : kink in the output path of the predicted variables #284
Issue replies: first human reply in Not enough data (median of 11 issues).
When replies arrive
All maintainers counted together. Shown only when at least 3 people replied in the last 90 days, so it never describes one person.
Replies are most likely between 18:00 and 21:00 (India time).
Show as table
| Hour (India time) | Replies, all weekdays |
|---|---|
| 00:00 | 2 |
| 01:00 | 1 |
| 02:00 | 4 |
| 03:00 | 4 |
| 04:00 | 1 |
| 05:00 | 0 |
| 06:00 | 2 |
| 07:00 | 2 |
| 08:00 | 2 |
| 09:00 | 1 |
| 10:00 | 0 |
| 11:00 | 2 |
| 12:00 | 2 |
| 13:00 | 1 |
| 14:00 | 1 |
| 15:00 | 1 |
| 16:00 | 2 |
| 17:00 | 2 |
| 18:00 | 3 |
| 19:00 | 8 |
| 20:00 | 7 |
| 21:00 | 2 |
| 22:00 | 2 |
| 23:00 | 2 |
How to start
- Contributing guidenot found
- Code of conductfound
- Issue templatesnot found
- Dev container for one-step setupnot found
- No CLA or sign-off requirement was found.
Where the project talks
Activity
- Commits, 90 days
- 74
- Releases, 12 months
- 23
- Active maintainers
- 5
- Last push
- 5 Oct 2026
Stack
Similar repositories
Same main language (Julia), most shared frameworks and topics first, then the faster reply.
Scientific machine learning (SciML) benchmarks, AI for science, and (differential) equation solvers. Covers Julia, Python (PyTorch, Jax), MA
- First reply