×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

New All Sky camera management software: indi-allsky

  • Posts: 255
  • Thank you received: 65
Image: Transparent clouds

cv2 matchTemplate
INFO:root:SEP processing in 0.3807 s
INFO:root:Deduplication in 0.0089 s
INFO:root:Total in 0.3896 s
INFO:root:Found 27 objects
 


scikit blob_dog
INFO:root:SEP processing in 4.9986 s
INFO:root:Found 4 objects
 
2 years 4 months ago #77464
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 255
  • Thank you received: 65
Image:  Full clouds (no stars)

cv2 matchTemplate
INFO:root:SEP processing in 0.3782 s
INFO:root:Deduplication in 0.0001 s
INFO:root:Total in 0.3783 s
INFO:root:Found 0 objects
 

scikit blob_dog
INFO:root:SEP processing in 5.0570 s
INFO:root:Found 0 objects
 
The following user(s) said Thank You: Jasem Mutlaq
2 years 4 months ago #77467
Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 255
  • Thank you received: 65
I also tried to use the python sep module, but ultimately, it would not accept any data from INDI.  INDI [mostly] produces 16-bit unsigned integer FITS data, where sep seemed to want 32-bit floating point FITS data.  I may have the types slightly wrong, but I never could get sep to accept FITS data from INDI.
2 years 4 months ago #77468

Please Log in or Create an account to join the conversation.

Great job Aaron! This method certainly provides an acceptable alternative to SEP for such applications! I gotta get running in my observatory!
2 years 4 months ago #77471

Please Log in or Create an account to join the conversation.

  • Posts: 278
  • Thank you received: 17
This looks really great :-)
2 years 4 months ago #77478

Please Log in or Create an account to join the conversation.

  • Posts: 255
  • Thank you received: 65
Status update...

In addition to the ZWO, Svbony, QHY, and Canon support, I have added support for the following vendors:
  • Touptek
  • Altair
  • Raspberry PI HQ camera
  • INDI Simulator (makes testing easier)
I have also added the ability to generate star trails from the all sky data, similar to Thomas Jacquin's allsky project.
The following user(s) said Thank You: Jasem Mutlaq
2 years 2 months ago #78998

Please Log in or Create an account to join the conversation.

  • Posts: 123
  • Thank you received: 10
Hello,
I use the soft of Thomas Jacquin for two years with a ASI 224MC. It's great but I would like to use a DMK41 usb instead the ASI224MC.
It's not possible with the soft AllSky of Thomas Jacquin..
Do you think is it possible whit your soft ?
Thank you,
Frank
2 years 2 months ago #79002

Please Log in or Create an account to join the conversation.

  • Posts: 124
  • Thank you received: 28
Hi Aaron, perhaps I could help as I use SEP on python with FITS files as well:

I use astropy for fits handling:and the image is used like this:So I know that SEP needs float, but it should work. If you need further help, please let me know.
Michel
The following user(s) said Thank You: Aaron Morris
2 years 2 months ago #79005

Please Log in or Create an account to join the conversation.

  • Posts: 200
  • Thank you received: 18
It seems like the new Pi zero 2 W might be well suited to running indi-all sky, it might be a little memory starved (512 MB) for full up StellarMate but it is the same cpu as Pi3 so should be OK for this?
2 years 2 months ago #79013

Please Log in or Create an account to join the conversation.

  • Posts: 255
  • Thank you received: 65
I believe the DMK41 is a v4l2 device.  My software will work with v4l2 devices, but there are caveats.

I have tested a couple of other v4l2 devices, mainly web cams.  None of the devices I tested had any adjustable gain settings (via INDI) and true exposures were limited to about 1 second.  Long exposures seemed to be simulated by internally stacking multiple frames together.  These cameras seem to be intended for video/planetary cameras and not really long exposure deep sky stuff.

I am willing to work with you if you want to do some testing.
2 years 2 months ago #79015

Please Log in or Create an account to join the conversation.

  • Posts: 255
  • Thank you received: 65
If I get back around to testing SEP again I will reach out to you.
2 years 2 months ago #79016

Please Log in or Create an account to join the conversation.

  • Posts: 255
  • Thank you received: 65
The Pi Zero is perfectly fine for just taking images, but I think generating timelapse videos will be a problem.  CPU power is not really a limiting factor, but memory is.  The downside of using python is it typically requires more memory than a more optimized C based program.  The 4 python processes spawned to run indi-allsky can easily take 400-500MB of RAM.

I have found that for 1K video (1920x1080) even with 1GB RAM (no swap) of memory you may end up with out-of-memory conditions where the linux kernel will kill the running ffmpeg process.  You need at least 100-200MB of swap in addition to complete the timelapse.

Memory usage of ffmpeg seems to scale fairly linearly with the resolution.  1K video requires ~512MB, 4K video will require 4x as much memory (2GB+) as 1K video.  If you scale 1920x1080 images by 50%, you might be able to get ffmpeg usage down to 256MB.

github.com/aaronwmorris/indi-allsky/#gotchas

As an alternative, you could use my software remotely from the Raspberry PI.  indi-allsky is just an indi client and can connect to remote indi servers over the network from a more powerful workstation.  There is a command line option in my software to connect to a remote indi server.
2 years 2 months ago #79017

Please Log in or Create an account to join the conversation.

Time to create page: 1.164 seconds