Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

retcode field in DiffEqArray

Open
#197 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
julia
Domain
data

Research direction

Start by reviewing the DiffEqArray definition and its construction and use sites. The issue proposes an optional retcode field for reduced ensemble solutions; done means DiffEqArray can preserve that status while retaining its existing (u,t) representation.

Written by the indexing model from the issue text.

Description

As discussed in Slack. DiffEqArray is a convenient way to reduce Solution type and wrap (u,t) results, it seems reasonable to add optional retcode field to DiffEqArray. What do you think? My current setup is: I run ensemble simulations and reduce each simulation to a DiffEqArray storing just (u,t) . Some parameters sets may result in Unstable retcode or Terminated if some termination criteria is present. To filter such simulations I define a solution type like

struct MySol
 sol::DiffEqArray
 retcode::Symbol
end

to save both solution and it's retcode

Dominant language
Julia
Stars
233
Forks
76
Avg merge
2h 17m
Merged PRs (30d)
9

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SciML/RecursiveArrayTools.jl

All issues in SciML/RecursiveArrayTools.jl

Similar issues

More Julia issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.