Adding Explanations to Spectrum Configuration

[bartnikm]

Description
Added Explanations to the Spectrum Configuration Section of the Documentation

Motivation and context
The original did not have a description of how to edit method parameters, so this would be nice for newer users

How has this been tested?

• Testing pipeline.
• Other.

Examples

https://bartnikm.github.io/tardis-bartnikm/branch/spectrum_configuration/io/configuration/components/spectrum.html

Type of change

• Bug fix.
• New feature.
• Breaking change.
• None of the above.

Checklist

• My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • (optional) I have built the documentation on my fork following the instructions.
• I have assigned and requested two reviewers for this pull request.

[codecov]

Codecov Report

Merging #1827 (8205ee0) into master (f52044a) will decrease coverage by 0.38%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1827      +/-   ##
==========================================
- Coverage   58.04%   57.65%   -0.39%     
==========================================
  Files          66       66              
  Lines        6747     6809      +62     
==========================================
+ Hits         3916     3926      +10     
- Misses       2831     2883      +52     

Impacted Files	Coverage Δ
...dis/montecarlo/montecarlo_numba/numba_interface.py	35.46% <0.00%> (-10.69%)	⬇️
tardis/tardis/montecarlo/montecarlo_numba/base.py	25.00% <0.00%> (-1.22%)	⬇️
tardis/tardis/analysis.py	30.16% <0.00%> (ø)
...rdis/tardis/montecarlo/montecarlo_configuration.py	100.00% <0.00%> (ø)
tardis/tardis/montecarlo/base.py	88.94% <0.00%> (+0.17%)	⬆️
.../montecarlo/montecarlo_numba/single_packet_loop.py	29.78% <0.00%> (+2.66%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f52044a...8205ee0. Read the comment docs.

[tardis-bot]

Before a pull request is accepted, it must meet the following criteria:

• Is the necessary information provided?
• Is this a duplicate PR?
  • If a new PR is clearly a duplicate, ask how this PR is different from the original PR?
  • If this PR is about to be merged, close the original PR with a link to this new PR that solved the issue.
• Does it pass existing tests and are new tests provided if required?
  • The test coverage should not decrease, and for new features should be close to 100%.
• Is the code tidy?
  • No unnecessary print lines or code comments.

[isaacgsmith]

Lines 11-13 could use some better explanation and clean-up (I know you did not write them). Start should not be capitalized and I'd probably say "value with units" as opposed to "quantity with units" as they are not expressed as astropy quantities. Also, I don't entirely like how it uses "frequency space" as I think we can explain that with less technical vocabulary.

[isaacgsmith]

Other than these quick fixes (you can just commit them directly from github) it looks good to go!

[isaacgsmith]

Great!