I've considered several different implementations for how to store the underlying data

being reworked in <a class="issue-link js-issue-link" data-error-text="Failed to load

<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="63

Underyling structure of Mortality Tables about mortalitytables.jl HOT 2 CLOSED

juliaactuary commented on August 29, 2024

Underyling structure of Mortality Tables

from mortalitytables.jl.

alecloudenback commented on August 29, 2024

being reworked in #55

from mortalitytables.jl.

alecloudenback commented on August 29, 2024

#55 simplified things considerably. Instead of trying to overload q and p and make them do everything mortality-wise, simplify by:

Not layering the rates under hierarchies of types
Focusing on easy, convenient access to what's most commonly used: a vector of rates
Use OffsetArrays to index by attained age. This is a little awkward to handle non-one based indexing of rates... but then again it's awkward when rates aren't defined for all ages.
limiting the exporting of simple variable names like p, q and ω and making the names cumulative_decrement and survivorship more semantically meaningful and less mortality specific.

from mortalitytables.jl.