lowellobservatory / all-sky Goto Github PK

Created 2 subdirectories under the Docs and Src directories to include the camera_ops and "presentation" portions of the project. There is no action required other than to be aware of these changes.

There is an odd limit on the number of files that can be written with the current test scripts when using the PyIndi python client. The limit is 510 files and the issue appears to be a problem with the python client and perhaps not the specific implementation of the python client.

Please read and comment on the All Sky Camera Requirements Document.

Perhaps not really an issue as much as an observation. The test camera has bias level of 0 with images taken with the shortest possible exposure while the camera is in complete darkness. However, images taken at 3 seconds and above exhibit some "noise" with adjacent pixels still at 0 ADU. Dark frames taken at 60 seconds subtract fine from images also taken at 60 seconds.

Once testing begins with a camera using prototype software there will be several options for controlling the camera to explore.

The use of GoQat has already been tested but needs more testing. The most recent version of GoQat was unable to recognize the allsky camera at DCT, so that will have to be addressed. Another is to use INDI drivers for controlling the camera and some testing using INDI has already been done. Another possible option will be to talk directly to the camera via the USB port using Python.

Is it better to pursue all camera control options more or less in parallel, i.e., nearly simultaneously, or will it be better to exhaust one method of controlling the camera before moving on to the next method?