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

[Bug] Delayed neutron precursor data all loads from group 2 in h5 xs generation script

Closed Beginner friendly
#577 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

A pull request for this has already been merged.

  • #579 by @hansenkyle — merged

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
85/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
data

Research direction

Open tools/data_library_generator/neutron/generate.py at the two reported locations, lines 474 and 505, and trace the loops over delayed neutron precursor groups. Check how the generated HDF5 data uses each group's fractions, decay rates, and fission spectra. Update both indices as specified in the issue, then generate data for a fissionable material and confirm the groups no longer all use group 2.

Written by the indexing model from the issue text.

Description

continuous energy neutron

Describe the bug.

In the neutron .h5 cross section generation script generate.py, all delayed neutron fractions and decay rates are identical to each other, since they all read from precursor group 2. See line 474:

        for i in range(N_DNP):
            idx = 1 + 1  # this should be i+1
            data = dnp_block.precursor_group_data(idx)

The issue is also present for the delayed fission spectra at line 505.

Steps to reproduce the bug.

This bug appears when generating h5 data for any fissionable material

What is the expected behavior?

idx should be i+1 (converting zero-indexed python i to one-indexed precursor group, within a for i loop)

How can this issue be closed?

  • Fix typo on line 475
  • Fix typo on line 505
Dominant language
Python
Stars
61
Forks
39
Avg merge
2d 2h
Merged PRs (30d)
21

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No 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 mcdc-project/mcdc

All issues in mcdc-project/mcdc

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.