Brett M. Morris

Thanks @pllim, looks like it's all fixed now. Thanks @kecnry and @rosteen!

Neat, thanks! We used to prevent problems due to internet access this with mocks like this: https://github.com/astropy/astroplan/blob/7880daad50733fc4d5c6df0a6fd077bac3fefe39/docs/conf.py#L159-L160 Could you add the `--remote-data` flag to the test matrix, e.g. here: https://github.com/astropy/astroplan/blob/f1bd5036534667e81339dc8f582c7ca0a03bdca2/tox.ini#L76

Hi @dsliski! For context here on GitHub, the code that @dsliski is trying to run looks like this: ```python from astropy.table import Table observability_table = Table() observability_table['targets'] = ['a', 'b',...

That's a neat idea, I've wanted but never seen a measured table for azimuthally-resolved altitude constraints. I'm curious – what kind of observations do you do so near to the...

@jegpeek could you elaborate on the workflow? Are you drawing subsets on background objects to exclude and then doing photometry on the foreground?

I'm re-milestoning this one to 4.0, since the related upstream GWCS changes (https://github.com/spacetelescope/gwcs/pull/498) are in draft pending strategizing and discussion from @nden and @mcara.

This PR is now failing on tests related to fixes that @cshanahan1 is working in her latest ticket on surface brightness in units of pix^-2. Waiting for progress on [JDAT-4520](https://jira.stsci.edu/browse/JDAT-4520).

Hi @krassowski. Is there a chance that this accepted request will be handled in the near future? If not, is this something that new jupyterlab contributor could get started on?

This PR will need to bump the pin on specutils after its next release (with https://github.com/astropy/specutils/pull/1156).

The specutils-related notebooks now pass the tests. The remaining failure is due to breaking changes in the photutils v2.0 release, which @larrybradley will be fixing shortly.