Fixed calculate_distance_line showing nu_diff < 0

[Rodot-]

Description

When running calculate_distance_line, once in a while nu_diff would be computed as a negative number. In the C version, when computing the distance to a line, there is first a check to see if we're at the last line in the list. If we are, we return MISS_DISTANCE instead. The numba code had a check that returned MISS_DISTANCE but it checked if nu_line was 0 instead of checking if we were at the last line.

How Has This Been Tested?

I've run an example tardis config with both the numba and C versions. The numba version no longer complains about negative nu_diff values and the spectra seem consistent between eachother.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have assigned/requested two reviewers for this pull request.