jonyardley / astroview Goto Github PK

This will be useful to get actual pixel values and for image analysis

This is so alignment of features is possible.

The user should be able to upload a single FITS file into the application which is then parsed and stored as an object.

• Check URL for .fits extension
• App loader whilst downloading file
• Error checking
• File too large
• Wrong extension
• Server Error (500, 404, 403)
  @Gissues:{"order":50,"status":"backlog"}

This will have to be integrated into the render image so that it will work within the webworker renderer.

The final image as a result of layering should be available in JPEG format and optionally PNG and/or TIFF.

The images should be additive so for example red+green = yellow

The user should be able to assign a colour 'mask' to the preview and subsequently to the full scale image when the user has finished tinkering with the preview image.

Using a query string, create a node.js proxy to server up a fits file from another external url.

... both before and after layering.

The user should have the ability to name & edit the name of the images which are loaded into the app

E.g. if we are going to do photometry, the exposure time keyword will need to be understood. For measurement of sizes, scaling information will need to be in the header somewhere etc.

• styling
• close button
• cancel button

The user should be able to load more than one FITS image into the app and display them in a list. The list should have a menu item so that the user can review the images at any point.

The user should be able to view a 1:1 scale image with the applied options defined from the values that the user selects when manipulating the preview image.

http://docs.travis-ci.com/user/deployment/openshift/

For example, the changes at the lower end of the slider for 👍 http://afit.eu01.aws.af.cm/?file=http://www.schoolsobservatory.org.uk/goobs/tmpdata/img/6374F000.fits is very different to that for:
http://afit.eu01.aws.af.cm/?file=http://www.schoolsobservatory.org.uk/goobs/tmpdata/img/6374F000.fits

A non-linear relationship between the slider position and the associated pixel value may be needed to get good control at the lower end (I find that a blend of linear and some sort of "histogram-equalisation" usually works well).

The loaded fits file should be displayed as a preview. At the moment I think that an arbitrary scale of 0.25 would suffice.

This will also need a toggle to allow the user to scale up to the maximum pixel value.

This would be particularly useful when aligning images.

Possibly CMY and white

Wherever there is a file input to load a FITS file the user should also have the option to provide a URL to load in an externally hosted image.

• Hook into preview

The user should be able to remove an image they have loaded from the image list view

If we expect raw FITS to be loaded then we will need to be able to scale and colour in the same tool or between tools in the application.

Standardise the communication between components and the ImageActions methods using the id rather than passing the whole image where possible.

The user should be able to scale the preview image in near real time, changing the min/max values and also the function which scales. These functions are yet to yet to be defined.

The user should be able to apply a colour scheme to the preview and subsequently the full image. There should be an array of colour scheme options by where the colour is defined by the original pixel count to help the user distinguish between objects in the image which may appear the same brightness when scaled in grey but in actual fact may be magnitudes apart.