openastroproject / openastro Goto Github PK

Just show tool tips for new features, even if they are otherwise turned off.

Not all UVC controls are currently supported in liboacam. Add them.

Currently only simple demosaic algorithms are implemented. Add more.

These URLs might help:

http://qt-project.org/doc/qt-4.8/widgets-tooltips.html

http://qt-project.org/doc/qt-4.8/graphicsview.html

Allow a pause to be specified after a change of filter rather than restarting recording immediately

Improve responsiveness of application to control changes due to delay loop in SXcontroller.c

Average deviation across the image, perhaps?

Ensure all library functions return a success/fail return code and an error code.

Possibly using an array of values and flags for each one to set?

Also could grab all the current settings at once in the same kind of way.

Expose all video formats to user in liboacam. Need to filter this out in the application rather than the library.

Obviously this is possible, but perhaps it should only work if the filters have different names. oacapture should only allow a named filter to be used in one slot?

Like the focus scoring image is.

Add some sort of blob detection code to find centre of planetary image

Add a feature to create a debug log to allow investigation of problems found by other people. Remove "qWarning()" statements in the core code once this is done.

Enable binning for this interface implementation

A more comprehensive help system is required

Eg. SX, Atik and QHY6 all allow binning at different levels on X and Y axes

Whatever that happens to be. Perhaps not all values should be set.

liboacam doesn't support all IIDC controls. Add them

Binning needs to work in the Point Grey libflycapture interface

There are some presentation issues with Qt5 that need investigation. Can't recall what they are offhand.

Improve responsiveness of application to control changes due to delay loop in QHY6controller.c

Add liboacam support for this camera.

Rescanning cameras or filter wheels should release existing device lists.

If a device doesn't below to the correct group on Linux, report the error in a user-friendly way when it can't be read.

Use telescope focal length (from library or entered manually?) to estimate focal ratio from size of target

IIDC and libflycapture2 allow controls to be turned off. Implement this in liboacam where it is allowed and expose the controls in the UI.

Fix bug where recording starts late when a filter is changed meaning that a recording is short. Correct on known bugs page.

Try to change these to something more appropriate

Try to make these two different types of cameras work well when both are connected. For example, GigE Blackfly and USB Chameleon.

All the outstanding libuvc changes in v1.1.0 need feeding back into the main libuvc project

Current frame formats for focus scoring are limited. Implement code to allow additional formats.

Use the V4L2_CID_AUTO_N_PRESET_WHITE_BALANCE ioctl() call if it is present to set the white balance

Improve responsiveness of application to control changes due to delay loop in atikSerialcontroller.c

Create access functions to do much of the work currently handled in outputSER.cc.

Add a function to indicate whether data is left- or right-justified for widths > 8 bits and < 16 bits

Image crop
Software binning
Flip image

Some filter wheels are synchronous, others not. Handling of two different types is messy and needs tidying up.

Should be obvious from frame format, so tidy this up

Add support for browsing session recordings.

Improve responsiveness of application to control changes due to delay loop in QHY5IIcontroller.c

Need some sort of ephemeris calculation to determine the expected size of a known target and from that the focal length and resolution of the optical train.

Make it possible to abandon an autorun session without having to complete it

Where cameras allow it, display the actual current values of each control when it is in "auto" mode.

Altair cameras have not yet been tested on the Mac. This needs to be done.

Should it really be necessary if it can be avoided?

Add a flag in liboacam interface to indicate whether a camera one-shot or streams a sequence of images.

As a command line option? Not quite sure how this should be specified.

When possible, read control values from a newly-connected camera and set the default values for the controls to those values

Either use a library of telescope focal lengths and camera pixel sizes or allow the data to be entered manually to create accurate angular size labels for the reticles

Not quite sure how to make this work. May need to record camera type and bus location and check for something similar next time around