The output of the reduction step should include an image overlay with point sources highlighted. On mouseover, reveal the magnitudes (similar to the comparison star viewer)

Separate observation information (eg. elevation, latlng) from Analysis

See chapter 13 of Brian Warner's book

Rather than making the same inputs for every image, I want to set some defaults at the top of the light curve page.

• Export the mean, median, std of sigma_clipped_stats
• Export other starfind output, such as peaks?
• Make fwhm and threshold adjustable by user?

http://photutils.readthedocs.io/en/stable/detection.html

See #47

For all images that the user has run reductions for and included, add it to a lightcurve plot.

When you upload a large number of files, it looks broken

Also, we should disable the image preview, because FITS files cannot be viewed in browser.

Users should have a navigation option to see a list of LightCurve objects that they created. Each item in the list should link to a lightcurve page.

A link to this page can go in the nav bar for internal pages.

Right now run_astro_phot does both. This makes it harder to debug and forces me to manually edit models when I want to rerun photometry!

Right now it is only highlighted in reduction tables

This should happen before the reduction flow.

Each image review flow page should have a 'Return to Light Curve' link

This would help users verify that nothing crazy is going on. We expect the relationship from instrumental to catalog magnitudes to be roughly linear.

This can happen before and after the reduction with instrumental magnitudes and standard magnitudes respectively. The output should include an image and also the correlation.

Two additional linearity tests

• standard mags vs catalog mags
• instrumental mags vs catalog mags (this visualization exists but needs to be improved)

A batch image upload should lead to a Lightcurve page that lists all the images.

it defaults to 0 and is only needed for certain filters. Add some text to make this clear.

Right now anyone who knows the URL can edit a light curve or ImageAnalysis. Everything on the platform is publicly viewable, but changes should be restricted to the user that created each object.

Some target CIs don't change from night to night, so it is acceptable to just enter a hard value (Warner 119). This color index could be inputted on the reductions page or the main lightcurve page (to apply to all images)

Currently all comparison stars are used in reductions. But astronomers won't always want this. We should present the information and let the astronomer choose.

I want to select images and

• omit them from the curve**
• include them in the curve**
• delete them
• move them to other light curves

This is a sanity check that can immediately show bad data points.

FITS data will almost always have a timestamp. Load it automatically into ImageAnalysis.image_datetime

Consider doing the same for latlng, elevation, and other metadata if available!

After performing initial upload, allow user to add more images

In the lightcurve view, user can trigger astrometry analysis and then view results.

Create placeholders for these pages using the template

Fill Astrokit homepage with content.

Find a good test dataset that we can showcase end-to-end so that new and prospective users know what they can get. This also doubles as a good test for our own scientific calculations.

A LightCurve object is a list of AnalysisResults. The app will have to group a bunch of user results together and display them as a single light curve.

Right now they are performed only for the knowns. ra, dec needs to be computed for unknown point sources.

It's too annoying to go 3 pages deep just to choose the target

Reductions are dependent on user-tuned parameters, so we should be able to run and re-run reductions whenever the user wants.

Each image produces an AnalysisResult, so a user may have a lot of AnalysisResults. Rather than referring to them by ID#, it would be easier if the user could label them arbitrarily. This should be done on the first edit page for AnalysisResults.

The name of the AnalysisResult should display in the list of a user's images (and in other UIs that include lists of AnalysisResults, such as when selecting an AR to add to a Lightcurve)

On the lightcurve creation page, users should be able to add or remove AnalysisResult objects (each of these AnalysisResults adds one point to the light curve)

Asteroid users will want to filter the set of potential comparison stars to those that have color similar to the sun.

A page that lists & links to light curves created by the current user.

A link to this page can go in the nav bar for internal pages.

At the top of the light curve page, have a form that contains all user inputs. These inputs will be the default values in the AnalysisResult astrometry->photometry->reduction flow.

ALCDEF is a special standard for light curves. It's formatted ASCII text.

See here: http://alcdef.org/docs/ALCDEF_Standard.pdf

This saves clicking around on the main light curve page

Next image: links to next "pending analysis" image
Add to light curve: changes status of this imageanalysis and links to light curve plot

All calculations need to be displayed with uncertainty. We need to identify the places where this is not the case and propagate those values to the frontend. 1/SNR is usually a useful uncertainty value.

Compute T_f in the formula for converting instrumental magnitudes to standard magnitudes.

Here's an example: https://www.aavso.org/transformation-coefficients-m67

Currently lightcurve names follow a preset format, "username YYYY-MM-DD". User should be able to rename this light curve on the light curve page. Renamed title should display in lists of light curves.

Each image either needs review or is reviewed (meaning reduction has run)

Make all light curves browseable to people, even if they aren't logged in. Probably makes sense to use the same template as #40?

A link to this page can go in the nav bar for internal pages.

Currently we attempt to compute magnitudes for all objects detected in the image. The user needs a way to designate the object for which they want to compute magnitudes.

In the reduction step, we should compute magnitudes for all point sources in the image. This allows us to compare to known values. It will also include any unknown point sources.