OK same tests but using v283

Results :-

1. Dreaded blue spinning wheel of death gone from ASTAP - a lot more responsive - tick

2. 5 x 35mb FIT files were processed and stack displayed in 2 mins - initial stack displayed in 15secs - faster than AT for FULL display - tick

3. Images with NO darks so same files (only one set RAW and the other FIT) produced finished images as attached but with col adj in AT - could find equiv in ASTAP - Sliders and or Stretch auto or otherwise didn't help.

4. Loss of Colour - but maybe down to the convertion of RAW to FIT's - see note (a) below

So far better experience for me than first test but still nots some refining but hell pretty good in a couple of days - big slap on your back Han's

Would I change fro AT (or that matter DSS Live) - yes if it runs on a RPI4 and the user interface was tidied / simplified - I would like the Col Adj to be a popup modal window that appears/disappears without the other "clutter" so its like DSS Live or AT.

Dont want a lot do I - LOL

So its getting there , from my point of view. Thanks Han's

Haven't got a RPI4 so cant help you with testing else I would.

Notes.
A - I haven't any FIT's files on my test machine so I used ASTAP to convert my 5 RAW(CR2) files used in the test so this may or may not have caused colour loss.!

Thanks for the info. If Ekos can convert to FITS then there is the advantage that the mount position will be added (presumably). That will be better for detection a new position = new stack.

Stash,

Thanks for testing. I'm glad it starts working for you.

Conversion to colour can be specified in the tab "stack method". Since intermediate result is shown after each stack step, final colour correction has to wait after the stack.

Making a separate "live stacking" program makes it more difficult to maintain. Now all parts are benefiting from each other. The viewer, stacking , solving combination is beneficial.

I hoped the menus are understandable .

I have the raw conversion implemented but not released yet. It was a little more difficult then anticipated. Do you think jpeg will be ever be used for stacking?

Now some more testing and I will try the Pi4 in the next days.

Han

Lots of great progress here! Regarding FITS images, INDI encodes the RA/DE of the current mount position. Looking forward to test this in a couple of days until I finished the ASTAP astrometry work.

How about a compromise - add direct connection from Top Menu to the Live Stacking Window

Use of Jpeg - As politicians should know - "never say never" - would give speed increase I would have thought and maybe other uses I can't think of (others might ) If its not much extra work and no extra difficult support needed then why not !

I just uploaded ASTAP version 0.9.284. Live stacking will work with FITS, RAWs, JPEG and TIFF, PNG

I also uploaded 32 and 64 bit version for Raspberry Pi. Below the test result of live stacking expressed in time required per image. For Pi4 you have to set your exposure times for an mono image of 2328x1760 pixels at around 10 seconds or more . Note the memory card used are slow. Class 10?
Above these dimensions, the process time becomes too much to use.

Time required for live stacking per image:


My Pi3 was running out of disk space, so maybe it slowed done the processing.

Han

This happened to me after I installed it (apparently) successfully (all dependencies satisfied) on an RPi4, running Ubuntu MATE 18.04, with amd64 architecture added.



What am I missing?

Jo

Did you download the Raspberry Pi4 rather than the Linux version?

No, this is running on an Ubuntu MATE install, not on Raspbian.

As I wrote, install using the Gnome Debian Installer went without a hitch, but the program won't start. Unfortunately, the feedback I am getting when trying to start it from the Terminal is only marginally more informative than the 'nada' I am getting when just starting it from the App Menu.
ASTAP seems to be compiled for AMD64, the Pi4 is running on ARM64 architecture, so I suspect although I added that architecture (wouldn't have been able to install otherwise), the OS still doesn't like it.

I'm running ASTAP on ubuntu mate on an Odroid-N2, but I chose the raspberry pi install as it was arm64 rather than amd, and it works for me.

Far too simple a solution, really.....

Worked like a charm. It pays to read the instructions, but then again, I never ask for directions either...



Thanks, Jerry!

El Corazon, the debian package installer should have warned you about the wrong architecture unless DPKG was used.


Correction in my table the first row 10 seconds processing time is without dark. The dark is kept in memory, so it adds only 1 second to processing (10 seconds to 11 seconds). I assume a lot of time is lost by reading from memory card.

Han