There are currently classes for energy levels (Level) as well as a class to hold all transitions (Transitions). However, they aren't terribly useful and also do not interact with one another.
One possible way to refactor this would be to create a Transition class and have Transitions hold many instances of Transition instances. Similarly, each transition could emit a Level class for the upper and lower levels that it represents a transition between. The Transitions class would hold many of the same properties that it currently does, but would derive them from these higher-level classes rather than directly from the underlying data itself.
There may be some performance issues with this approach, e.g. every time we want to list all transition wavelengths, it would not make sense to have to rebuild this Transitions object from scratch.
There are currently classes for energy levels (
Level) as well as a class to hold all transitions (Transitions). However, they aren't terribly useful and also do not interact with one another.One possible way to refactor this would be to create a
Transitionclass and haveTransitionshold many instances ofTransitioninstances. Similarly, each transition could emit aLevelclass for the upper and lower levels that it represents a transition between. TheTransitionsclass would hold many of the same properties that it currently does, but would derive them from these higher-level classes rather than directly from the underlying data itself.There may be some performance issues with this approach, e.g. every time we want to list all transition wavelengths, it would not make sense to have to rebuild this
Transitionsobject from scratch.