P. L. Lim

This GitHub issue should really belong in https://github.com/spacetelescope/stcal though moving it on GitHub might confuse the JIRA bot. 🤷‍♀️

Looking here https://github.com/astropy/specutils/blob/d16d91a077417a7aacdee06d2b259fa887908b14/specutils/fitting/fitmodels.py#L61 I think it is basically an existing `astropy.modeling` behavior. How did we patch the doctest for `astropy.modeling`? The same trick would probably work here. 👎 on blind...

Looking at the log again ``` - Model: Gaussian1D - Inputs: ('x',) - Outputs: ('y',) - Model set size: 1 - Parameters: - amplitude mean stddev - Jy um um...

The varying line length is indeed surprising... and what does that have to do with numpy rounding? 🤯

`estimate_line_parameters(sub_spectrum, models.Gaussian1D())` basically returns a model object. So might be possible to change the narrative to not print out the whole model, but rather specific things that the example is...

I still get pinged by Actions about this once a week or so.

It was for possible future additions. Added by @eteq in https://github.com/astropy/astropy/pull/3758 as suggested by @astrofrog

> the IAU list is the only one that defines borders between constellations Well, other cultures have their own constellations too. They don't currently publish the borders for us, but...

Is this `logical-null-handling` branch tied to a PR?

Thanks. I will let FITS maintainers decide. Personally, I am getting a little confused with multiple PRs and similar issues on this subject (VLA in FITS).