Jump to content

sgl_imaging_challenge_2021_3.thumb.jpg.30e9b298c34c80517e8b443ce153fce3.jpg

Annoucement : Astro Live Stacker software


deufrai
 Share

Recommended Posts

Hi everyone

I am a proud member of a team working on a multi-platform live stacking solution : ALS (Astro Live Stacker => https://als-app.org)

spacer.png

It runs fine on PC (GNU/Linux and Windows 7 to 10), OSX and RaspBerry.

Current stable version is very basic : Polling a folder to detect new images (any FITS or DSLR RAW) then align + stack (Mean or Sum) + autostrech + levels + RGB balance.

ALS also has a built-in webserver so your pals at the astroclub can see the results, provided everyone is on the same network.

We are working hard on new features like Dark subtraction + Hot pixel removal and are providing nightly builds for you guys to try it out. Check out https://als-app.org/nightlies/

Handling image capture directly inside ALS using INDI protocol is on our roadmap too. check out our Github repo to know more about it

If you could give it a try and help us make ALS a fun & easy way to see and share all those wonders above our heads, that would be much appreciated !

Clear skies to all !

-- 

Fred

  • Like 5
Link to comment
Share on other sites

41 minutes ago, R26 oldtimer said:

That's interesting. Would you consider an android app?

Hi

In a not too distant future, the integrated webserver will expose a full-fledged web application, so you can control ALS from any device that is able to run a web browser. But ALS core will still have to run on a computer / rpi.

  • Thanks 1
Link to comment
Share on other sites

Straight into a missing bit for me - doesn't do FITS - Tiff,JPG,PNG only 😞

Properties should have a blob that says you cant change properties until after you have stopped Monitor etc - yes its greyed out but still needs to be hightlighted IMO

Doesn't create missing Work folders

Nothing to say min 25 images - if you change to lower figure it just resets back to 25 - Really min 25 images - way too high IMO especially when using a  DSLR

Not being negative but thats the items found in just a few minutes - perhaps I will try on a later version.

 

Edited by stash_old
Link to comment
Share on other sites

12 minutes ago, stash_old said:

 

Hi ! :)

12 minutes ago, stash_old said:

Straight into a missing bit for me - doesn't do FITS - Tiff,JPG,PNG only 😞

You mean : saving results as FITS format ? Sure, why not

13 minutes ago, stash_old said:

Properties should have a blob that says you cant change properties until after you have stopped Monitor etc - yes its greyed out but still needs to be hightlighted IMO

Excellent point : thanks. See https://github.com/gehelem/als/issues/114

13 minutes ago, stash_old said:

Doesn't create missing Work folders

This is done on purpose : It would be too easy to make wrong assumptions about where everyone would agree to have ALS create its work folder, I guess. But we are all ears if we manage to reach reasonable consensus

15 minutes ago, stash_old said:

Nothing to say min 25 images - if you change to lower figure it just resets back to 25 - Really min 25 images - way too high IMO especially when using a  DSLR

This threshold is not about image count. This is used during frame alignment : When ALS finds matches (common points) between new frame and reference frame, it rejects its findings if matches count is lower than this threshold. This is used to guarantee alignment quality and is, as you may have seen, user definable

17 minutes ago, stash_old said:

Not being negative but thats the items found in just a few minutes - perhaps I will try on a later version.

Negative, maybe not. A bit harsh, surely. But what can we expect from a Brit talking to a Froggie ;)  ? No biggie at all.

  • Haha 1
Link to comment
Share on other sites

For test (simulation - cloudy times) purposes would it be possible to allow a folder of already saved images to be stacked, either at maximum rate, or perhaps a specified rate e.g. one every 30 seconds? I found with the Windows 10 version I could feed a capture folder with one fits file at a time and watch the ALS actions, but couldn’t do so on my RPi4 which is obviously very busy when ALS is executing (presumably because all cpus/threads are active with ALS in the present version).
 

I normally control my RPi4 for capture guiding etc. from my laptop running VNC viewer over the RPi4 (Astroberry) wifi hotspot. I suppose I could use something like SyncThing on both machines to copy over captured images and then run ALS on the laptop which would have spare processing capacity. Am I missing any obvious alternative?

Thanks

 

  • Like 1
Link to comment
Share on other sites

Hi again @Avocette :)

12 minutes ago, Avocette said:

would it be possible to allow a folder of already saved images to be stacked,

This has been asked by many, so I guess it is a real need. And couldn't cost too much to implement

11 minutes ago, Avocette said:

I suppose I could use something like SyncThing on both machines to copy over captured images and then run ALS on the laptop which would have spare processing capacity. Am I missing any obvious alternative?

You could share a folder on your windows machine and have your RPI write captured images to that.

Link to comment
Share on other sites

5 hours ago, deufrai said:

Hi ! :)

You mean : saving results as FITS format ? Sure, why not

Excellent point : thanks. See https://github.com/gehelem/als/issues/114

This is done on purpose : It would be too easy to make wrong assumptions about where everyone would agree to have ALS create its work folder, I guess. But we are all ears if we manage to reach reasonable consensus

This threshold is not about image count. This is used during frame alignment : When ALS finds matches (common points) between new frame and reference frame, it rejects its findings if matches count is lower than this threshold. This is used to guarantee alignment quality and is, as you may have seen, user definable

Negative, maybe not. A bit harsh, surely. But what can we expect from a Brit talking to a Froggie ;)  ? No biggie at all.

I am Not a "Brit" 🙂  but I do live in the UK -    so dont be so quick to make assumptions 🙂

Not that it counts for much but as I say I will look at it again at a later version - always good to have another tool in the box!

Link to comment
Share on other sites

8 hours ago, stash_old said:

Not that it counts for much

It does. 

there's always something useful to take from users' advice. Thanks for the time you spent testing and reporting

Clear skies !
 

  • Thanks 1
Link to comment
Share on other sites

Another biggy - no support for DSLR (canon and other ) RAW format files(CR2/CR3 etc)  that I could see !

If you know Astrotoaster it works well but needs bringing up todate so if same features could be added ,such as list of files being stacked with option to omit and restack etc  - thats where IMO it should look like in terms of features 🙂

Link to comment
Share on other sites

13 minutes ago, stash_old said:

 

Hi

13 minutes ago, stash_old said:

Another biggy - no support for DSLR (canon and other ) RAW format files(CR2/CR3 etc)  that I could see !

As stated on ALS website : https://als-app.org/ : ALS is meant to support quite recent camera RAW files. Complete list is here : https://www.libraw.org/supported-cameras.

And yes, sorry, CR3 files are not yet supported. See : https://github.com/gehelem/als/issues/95

So it seems you just found a bug, which is a good thing. Would you be kind enough to provide the following information so we can investigate and solve the issue :

- Operating system's name and version

- what version of ALS you got that bug with : Version is displayed in the about box. *in case of a nightly build : current version will always display v0.7-dev. If you remember what nightly build you got, it's good for us*

- an image file that reproduces the issue

20 minutes ago, stash_old said:

such as list of files being stacked with option to omit and restack etc

Could you please elaborate on this ? I'm having a hard time to understand. Sorry, English is not my first language

 

Thanks again for your time :)

Link to comment
Share on other sites

2 hours ago, deufrai said:

Hi

As stated on ALS website : https://als-app.org/ : ALS is meant to support quite recent camera RAW files. Complete list is here : https://www.libraw.org/supported-cameras.

And yes, sorry, CR3 files are not yet supported. See : https://github.com/gehelem/als/issues/95

So it seems you just found a bug, which is a good thing. Would you be kind enough to provide the following information so we can investigate and solve the issue :

- Operating system's name and version

- what version of ALS you got that bug with : Version is displayed in the about box. *in case of a nightly build : current version will always display v0.7-dev. If you remember what nightly build you got, it's good for us*

- an image file that reproduces the issue

Could you please elaborate on this ? I'm having a hard time to understand. Sorry, English is not my first language

 

Thanks again for your time :)

No sure if the CR2 is a bug as I could not find a way to list files currently being stacked - may have just missed it 🙂

As for the feature to select only certain files in a folder and be able to deselect a file to restack see attached screen prints.

Nightly build ALS nighlty build 2020-05-08-77e1b4e02

als-1.png

als-2.png

als-3.png

Link to comment
Share on other sites

Hi again

So we went from

4 hours ago, stash_old said:

Another biggy - no support for DSLR (canon and other ) RAW format files(CR2/CR3 etc)  that I could see !

to

2 hours ago, stash_old said:

No sure if the CR2 is a bug as I could not find a way to list files currently being stacked - may have just missed it

:)

Would you mind confirming if CR2 are actually correctly read by ALS on your system (which I assume is win10) ?

 

Regarding the feature you are referring to, indeed, that would be nice, when and if ALS is made to handle already-populated folders. You are welcome to file an issue on our issue tracker for that matter.

Thanks again for your time & efforts

--

Fred

Link to comment
Share on other sites

31 minutes ago, deufrai said:

Hi again

So we went from

to

:)

Would you mind confirming if CR2 are actually correctly read by ALS on your system (which I assume is win10) ?

 

Regarding the feature you are referring to, indeed, that would be nice, when and if ALS is made to handle already-populated folders. You are welcome to file an issue on our issue tracker for that matter.

Thanks again for your time & efforts

--

Fred

yes becuase its confusing ALS only picks up new files in the monitored folder - so if I forget to start ALS it wont do anything with the existing files it just says running. If I delete the files and add them back in while ALS is up and running then it springs into action. IMO not a good work flow as it should process files already in the monitored folder or have a list of ones it has already processed from the monitored folder. Sorry thats my comments on its work flow.

So CR2 files are processed SO LONG as they are added after ALS is started and running the monitoring process.

FITS on the other its does not like and gives an error for the FITS files I use - ok in CCDCIEL,ASTAP etc etc

Please see attached screen prints which I hope will help you understand whats happening. The Astrotoaster program screen print is there to show the same files being processed ok!

here is a link to 1 of the FITS file for your team to test.  https://drive.google.com/open?id=1iIdVWzHPn_EXZGiOu9PdaHdCNm6q-qz9    32mb file

 

And yes its Win 10 being used for ALS but the FITS files were from INDI(RPI) via CCDCIEL(Win10) !

alsa-1.png

alsa-2.png

alsa-3.png

Edited by stash_old
  • Thanks 1
Link to comment
Share on other sites

2 hours ago, stash_old said:

yes becuase its confusing ALS only picks up new files in the monitored folder

Hi again,

How can it be confusing ?The very first line describing ALS features on the website states as follow :

"ALS polls a folder on your machine and aligns + stacks any new picture saved into that folder."

If this is not clear enough, I'll think of a better way to phrase it.

Regarding the issue on the FITs file you provided, this will be fixed by tomorrow. We determine file types by their name extension, and '.fts' is obviously handled incorrectly. Thanks for pointing it out

Link to comment
Share on other sites

1 hour ago, deufrai said:

How can it be confusing ?The very first line describing ALS features on the website states as follow :

"ALS polls a folder on your machine and aligns + stacks any new picture saved into that folder."

OK I didn't read the line 😞

 

Link to comment
Share on other sites

.fts file extension handling is now fixed

But @stash_old, don't be mad. ALS still cannot process your good M31 frames.

Your FITS file does not contain the header describing the CFA pattern used by your camera. And ALS still does not provide the user with the ability to specify one. See : https://github.com/gehelem/als/issues/113

Thanks for helping us with your tests and reports

Edited by deufrai
Link to comment
Share on other sites

From a fellow open-source Python EAA tool developer I fully applaud your efforts! I see we have gone down different lines with the main libraries we are using (I'm using scikit-image and Kivy for instance), but if there are any ways we can help each other out algorithmically then let's do so.

I would absolutely love to see open-source Python-based platform-independent capture tools that can be used (but unfortunately lack the low-level skills to produce them myself). Maybe a topic for another thread?

Martin

  • Like 2
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Chefliam
      Hello fellow astronomers, I have come to the forums as I have depleted all other options.
      I own an NEQ5 GoTo with a Skywatcher 72ED. I have connected the mount to my computer using an EQDIRECT cable. 
      I am trying to use stellarium with ascom and eqmod to slew the mount to a desired object. I have configured my scope using the “telescope control” plugin in stellarium. In the past I had successfully achieved slewing through stellarium. 
      The problem is that now, one month later, when opening stellarium and trying to slew the telescope to a selected object (using either the “slew telescope to” panel or the shortcut (control + 1)) the mount moves for a fraction of a second and then stops, stellarium freezes and then the scope indicator in stellarium slides quickly to the horizon, and EQMOD control panel displays “horizon limit horizon limit” error. (Let’s call this the “main failure mode”.)
      Note that : 
      I can use EQMOD and slew the scope manually without problem.  If using it in tandem with stellarium, when I do so the scope indicator in stellarium moves without issue.
      I have used the “resync encoders” button on EQMOD to establish the home position, but this does not affect the behavior.
      I can use ascom device hub to slew the scope manually without a problem as well. 
      The main failure mode described above happens most of the time.  However, I sometimes get other erratic behavior in stellarium:
      Sometimes, when trying to slew the scope in stellarium, the mount moves for a second then stops (as described above), yet the scope indicator in stellarium moves to the selected object not the horizon, then the mount starts to track (even though it has not yet slewed). 
      Or, rarely, when trying to slew the scope in stellarium, the mount physically moves (seemingly to the object) and starts tracking, the scope indicator moves to the selected object -- appearing to work normally.  But then, when trying to slew the scope a second time to a different object, it fails again as described in the main failure mode above.
      I have tried opening stellarium as administrator but I still get one of the three outcomes when trying to slew. 
      Does anyone have any insight on this ? 
    • By Btmackd
      I have a CPC 800 Edge HD as well as an Orion Starshoot Autoguider.  I recently ordered a ZWO ASI294 MC Pro colour camera.  In terms of the auto guide function I had planned on using PHD2 (which I already downloaded onto my Mac laptop).   In terms of researching software that would allow for control of the camera I understand there are a number of options. I considered purchasing an ASIair, however, I understand that is not compatible with the Orion Starshoot Autoguider, and therefore I would need to replace that with a ZWO.  I am hesitant to want to do that, even though it would be convenient not to have to bother with laptop connectivity.  Right now I've been using my iPhone for goto functionality with Starsense and Skyportal wifi.  I understand there are a number of options available for Windows based PCs in terms of control of camera and image acquisition.  BackyardEOS (for DSLR cameras), Astrophotography Tool, and Nebulosity.  These seem to be the most popular.  However, it looks to me as though APT is just for Windows based PC.  As well, not sure the extent to which Nebulosity is seamless when it comes to Mac compatibility.  Is there a recommended Image Acquisition software for Mac users?  Is a Windows PC laptop dedicated for astrophotography the best approach (e.g. second hand etc)?  I would appreciate your recommendations.  Thanks
    • By SamK
      After many hours of fiddling round with Registax wavelet settings to process my own solar system images, I've always been curious as to how it actually works. In doing so I've put together my own image sharpening program which does something similar to Registax wavelets. For comparison, I've also added some general purpose deconvolution techniques which you'll probably be familiar with from other image processing software (like Wiener inverse filtering, Richardson-Lucy, etc). In choosing a point spread function to deconvolve with, one suprising result was that the typical stack outputs from Autostakkert work best with a Lorentz point spread function (with a minor modification). Deconvolving with a Gaussian point spread function doesn't really work. Deep-sky images seem to deconvolve best with a Moffat point spread function (which is to be expected - it's already well established that star profiles in long exposures are best approximated with a Moffat function).
      On the whole, it's unlikely that you can sharpen solar system images much more in this program than you already can in Registax. You can see results from Registax wavelet (sharpening layers), inverse filtering (e.g. Wiener), and iterative deconvolution (e.g. Landweber) below. They all give very similar results. In all the techniques there's a similar trade-off between less noise but less detail vs more noise but more detail.
      There are some quick start notes on the first page of the Readme here:
      https://github.com/50000Quaoar/Deconvolvulator/blob/main/Readme.pdf
      There are some examples of deconvolved images here (move mouse over image to see before/after):
      https://50000quaoar.github.io/Deconvolvulator/
      Image credits are on the hyperlinks
      The Windows download is here:
      https://github.com/50000Quaoar/Deconvolvulator/raw/main/Deconvolvulator32.zip
      Example solar system tifs to experiment with are here:
      https://github.com/50000Quaoar/Deconvolvulator/tree/main/image%20examples
      And the project page is here (with Source code in the src folder)
      https://github.com/50000Quaoar/Deconvolvulator
      If anyone finds it useful, do post here how it compares to other tools you use for solar system image sharpening.
      The download and the source code are free, you can use it unrestricted for any purpose. The OpenCV and OpenCVCSharp components which my program use have licence information at the end of the Readme.pdf.
      Sam
       

    • By alexwolf
      Yesterday we released version 0.20.4 of Stellarium.
      The major changes of this version:
      - Added Calendars plugin
      - Many changes in AstroCalc tool and core of Stellarium
      - Many changes in plugins
      - Updated DSO catalog 
      - Removed Compass Marks plugin (the feature moved into core)
      Download binary packages for Windows, Mac and Linux you may here: https://github.com/Stellarium/stellarium/releases/tag/v0.20.4
      Thank you very much to community for bug reports, feature requests and contributions!
      Full list of changes:
      - Added Balinese Pawukon calendar into Calendars plugin
      - Added notes on polygonal landscapes (technical restrictions) (GH: #1397)
      - Added Calendars plugin (GH: #1343)
      - Added configurable values for quick FOV tool (GH: #1391)
      - Added new zoom algorithm (GH: #1415, #529)
      - Added compass marks into core of planetarium
      - Added ability to hide cardinal and compass buttons from the GUI
      - Added missing time zone America/Godthab
      - Added few DSO textures (GH: #1402, #1441)
      - Added Galactic Center and Anticenter points
      - Added a config option to use multisampling for rendering "Planet"s (GH: #1388)
      - Added landers from the Chinese Lunar Exploration Program into list of locations
      - Added on-screen controls for OAG in Oculars plugin (GH: #935)
      - Added table view of exoplanets (GH: #1141)
      - Added show angular distance between the moon and host planet (GH: #1372)
      - Added classical cepheids filter for AstroCalc/WUT tool
      - Added Algol-type eclipsing systems filter for AstroCalc/WUT tool (GH: #1355)
      - Added ability to toggle to using decimal degrees for various navigational data through follow the option "Use decimal degrees" in the main GUI (GH: #1344) 
      - Added script with shortcut, which add ability to jump to random location for celestial navigation game and practice (GH: #1345, #1058)
      - Added support flip commands into Scripting Engine (GH: #1351)
      - Added new language: Central Atlas Tamazight
      - Added comet icon for ephemeris points plotting for AstroCalc/Ephemeris tool (GH: #1332)
      - Added script skybox.ssc into list of translatable scripts (GH: #1335)
      - Added config option to hide selection markers (default: viewing/flag_show_selection_marker = true) (GH: #1321)
      - Added export list of objects as Stellarium bookmarks into AstroCalc/WUT tool
      - Added support capital Greek chars in Search Tool (GH: #1282)
      - Added some discoverer’s original designation for double stars as their scientific designations (GH: #1282)
      - Added option to hide unlabelled ephemeris markers (GH: #1315)
      - Added ability to run the silent uninstall Stellarium in Windows
      - Added ability use decimals value for ephemeris steps in AstroCalc/Ephemeris tool (GH: #1289)
      - Added "No" default for deletion confirmation warning (GH: #1292)
      - Added ability to toggle show extra decimals in the navigational info (GH: #1303)
      - Added tool for build an AppImage package (GH: #1288)
      - Added ability for following an option ''Use decimal degrees" for longitude and latitude in Location dialog to define format of data (GH: #1416)
      - Fixed collision calendars panel with bottom button bar (GH: #1422)
      - Fixed zooming to FOV when duration is zero (GH: #1430)
      - Fixed designations for star HIP 62819 (GH: #1432)
      - Fixed crash when attempting to add a sensor (GH: #1407, #1403)
      - Fixed UMa figure in S&T skyculture (GH: #1414)
      - Fixed typos in Chinese skyculture (GH: #1413)
      - Fixed text for meteor showers plugin (GH: #1387)
      - Fixed the visual style of color chooser (GH: #1395)
      - Fixed GUI of AstroCalc/Positions tool
      - Fixed error in GUI of AstroCalc/WUT tool
      - Fixed errors in documents for scripting engine
      - Fixed typos and errors in various sky cultures
      - Fixed running scripting method core.quitStellarium(); (GH: #1363)
      - Fixed the location of Dunsink Observatory (GH: #1370)
      - Fixed rendering orbits with undefined period
      - Fixed orbital elements for comet Halley (1986) in the default ssystem_minor.ini file
      - Fixed typos in skycultures
      - Fixed odd cyclic behaviour of HiPS (GH: #1323)
      - Fixed odd survey interaction (GH: #1314)
      - Fixed crash when reference.fab file has wrong format
      - Fixed closing various dialogs (fix #1305, #1338)
      - Fixed sorting issue in AstroCalc/Ephemeris tool
      - Fixed search stars by designations (u Her and U Her are different stars!) (GH: #1282)
      - Fixed adding extra designations for stars, who already has Bayer and Flamsteed designations (GH: #1282)
      - Fixed sorting stars by their designations (partially) (GH: #1282)
      - Fixed selecting invisible stars (GH: #1331)
      - Fixed switch to native planet names when skyculture is changed in Location dialog (GH: #1203)
      - Fixed installing star names for Western (O.Hlad) skyculture (GH: #1170)
      - Fixed typecast: avoiding of jumping the markers of exoplanets and pulsars (GH: #1286)
      - Fixed handling custom shortcuts and few spell-check fixes
      - Fixed GUI issue in Observability plugin
      - Fixed inconsistency of NGC/IC list in AstroCalc/WUT tool (GH: #1310)
      - Fixed filling version info for Windows installer
      - Fixed installer for Windows
      - Fixed translatable string for Icelandic calendar
      - Fixed Puppis constellation lines in S&T skyculture (GH: #1438)
      - Fixed Mensa and Microscopium in S&T skyculture (GH: #1440)
      - Changed rendering planets: improve planets' halos size in relation to stars' (GH: #1361, #367)
      - Changed rendering of orbits in Satellites plugin: Hide invisible part of orbits when "hide invisible artificial sats" option is enabled (GH: #1349)
      - Changed GUI behavior: Enlarged maximum dialog size (GH: #1318)
      - Changed versioning scheme of Stellarium
      - Changed few DSO textures: reduce the size of some texture files (GH: #1442)
      - Updated Stellarium User Guide (GH: #1334)
      - Updated DSO catalog (v3.12)
      - Updated GUI of Calendars plugin
      - Updated GUI: refactored block "Additional buttons"
      - Updated description of Chinese skyculture (GH: #1410)
      - Updated Bengali descriptions for landscapes and skycultures (GH: #1380)
      - Updated nomenclature data
      - Updated few DSO outlines (GH: #1368)
      - Updated initial time steps for AstroCalc/Phenomena tool (GH: #372)
      - Updated Solar System Editor pluign: improve docs + added confirmation dialog (GH: #1304)
      - Updated DSO names
      - Updated upper limit for font size
      - Updated GUI of AstroCalc tools
      - Updated Exoplanets plugin: added extra info
      - Updated Satellites plugin: cosmetic improvement the handling the visibility of satellites by their groups
      - Removed Compass Marks plugin
      - Removed the XPM version of the app icon (GH: #1384)
      - Removed dead links from skycultures
      - Removed support of shortcuts from AstroCalc tools (GH: #1293)
    • By Anonymous Astronomer
      Hello everyone,
      I've read about Starnet++ lately and I wanna give it a try. Tried to get it from here but there are some issues. It seems like I can't find any viable kit.

      I would really appreciate if someone can provide a link to download.

      Thank you,
      Vlad 
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue. By using this site, you agree to our Terms of Use.