Activation foil classes

[RemDelaporteMathurin]

This PR moves away from get_decay_lines in favour of a class architecture for check sources.

This will be useful in #71

TODO:

• fix tests
• document

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.96%. Comparing base (bf88ee2) to head (1681225).
⚠️ Report is 128 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #73      +/-   ##
==========================================
+ Coverage   83.66%   83.96%   +0.30%     
==========================================
  Files          18       18              
  Lines        1114     1129      +15     
==========================================
+ Hits          932      948      +16     
+ Misses        182      181       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[cdunn314]

Looks pretty good, but the issue is that we can and sometimes do use several different check sources of the same nuclide. For example, we use both a Na22 source with an activity of 9.98 uCi on Sep 29, 2023, and another one that is 1 uCi on Jan 2006. I think creating several subclasses of CheckSources for Na22, Mn54, Cs137, Co60, and Ba133 with their half-lives, photon energies, and intensities built in, but for which the user specifies the activity, name and activity date.

[RemDelaporteMathurin]

Looks pretty good, but the issue is that we can and sometimes do use several different check sources of the same nuclide. For example, we use both a Na22 source with an activity of 9.98 uCi on Sep 29, 2023, and another one that is 1 uCi on Jan 2006. I think creating several subclasses of CheckSources for Na22, Mn54, Cs137, Co60, and Ba133 with their half-lives, photon energies, and intensities built in, but for which the user specifies the activity, name and activity date.

That makes sense to me. So instead of a subclass of CheckSource, we can create a class Nuclide that contains physical quantities like half-lives, energies, intensities

[cdunn314]

The energy of the gamma rays emitted by the nuclide in keV

[cdunn314]

Intensity doesn't need to sum to 1. For example, in Na22, 1.8 photons are emitted per decay due to positron annihilation creating two photons per beta+ particle being emitted.

[RemDelaporteMathurin]

Ok good point thank you. It needs to be relative to something though no? i guess it's photon per decay?

[cdunn314]

Just a couple little edits in the doc string