Henry Ferguson

Merging both of Erik's suggestions, and easing the time pressure, how about: Default -- 6 months and write down a plan for what notebooks or improvements are desired for the...

@whitmore999 That you can do already. In the case of aperture photometry it doesn't modify the positions anyway. In the case of psf-fitting photometry, you can set your psf_model to...

The current output doesn't have the aperture radii even in the metadata, so I would suggest adding that to the existing table, as well as providing the alternative format.

@larrybradley Good point! I had forgotten that apertures can be quite general. Storing the info somehow in the metadata rather than column names seems cleaner for the general case. Sounds...

I feel a bit the same way about the visualization stuff that is in Astropy core or photutils. It doesn't sit all that comfortably in those packages. As a user,...

I can see some benefit of leaving the API alone (for now), rather than adopting this partial solution. Since the documentation has to tell people how to deal with smoothing...

I agree with the general swing in favor of (2). I'm not sure I understand the reasoning behind just issuing a warning for the WCS case though. Seems like if...

I've often run into a problem where a single wavelength is repeated with two values (e.g. in model spectra at spectral breaks). I'm fine with not supporting this, but notifying...

I'm okay with requiring the user to deal with unit conversions now and considering that as a later enhancement, as long as it throws an error if the units aren't...

For what it's worth, I've had the most success with ```scipy.interpolate.UniverariateSpline```, although it generally takes several iterations of fiddling with ```s``` and ```k``` before I am happy or fed up....