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

Add new components for radiation energy density

Open
#1,775 51 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
backend

Research direction

Start by reviewing the existing state.xn component and the auxiliary composition implementation, especially how RHS and Jacobian support are defined. Determine which component interface can represent state.rad without aion, zion, EOS coupling, or 0–1 bounds. Done means a documented implementation path is agreed for evolving radiation energy density with state.xn and T.

Written by the indexing model from the issue text.

Description

To implement a photoionization network, we will need radiation energy density as a state components, call it state.rad. It has a RHS (ydot) that depends on T, state.xn, and state.rad, and it should evolve along with state.xn and T. However, it differs from state.xn in three different ways:

  1. it does not have aion and zion;
  2. it won't affect the EOS
  3. it's not limited to 0 -- 1.

Is there an existing component that can work this way? Any suggestion on how I should go about adding this new component?

It seems to me that the auxiliary composition won't work, because it does not have a RHS and Jacobian, but I might be missing something.

Dominant language
C++
Stars
44
Forks
46
Avg merge
3d 15h
Merged PRs (30d)
9

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 AMReX-Astro/Microphysics

All issues in AMReX-Astro/Microphysics

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.