SIRIL Short vs long exposures , computer power and auto stack option? Siril Team Siril · Astroplantfish · ... · 28 · 626 · 2

ThierryBoufflet 0.00
...
· 
With 1.83 of sampling rate, you don't have worry a lot about seeing, except if it's really miserable. From 120s for bright objects and 300s for faint ones, you have a range of choices.
Like
ReadyForTheJetty 1.81
...
· 
Bortle 9 Dim Light Chaser:
Hi, 

I'm trying to keep computer costs down for processing dso images. 

I'm planning to use Siril, as I've read it is relatively undemanding on computer specs compared to some other software, when stacking. But, is it best to have a small number of long exposures or large number of short exposures, when it comes to demand on computer resources? 

Since I'm planning to get an AZEQ6 mount, I am able to go for a shorter number of long exposures, e.g. 5 minutes per exposure. 

My other question is, does Siril have an option to auto stack the best exposures or does the user need to manually choose which exposures to stack? 

Thanks for your help

Mark

Hello Mark,

I used to stack 800 images with 1.3 sec sub-exposure, once.  Siril simply fill out my entire spared space (400 GB) in one minute.  I recommend to use long exposure and less No. of images for stacking in general.

Clear skies,

Bortle 9 DimLightChaser

If you ever attempt that again, just turn on the RICE compression and you probably won’t run out if disk space.
Like
Astroplantfish 0.00
...
· 
Gary JONES:
Mark Worthington:
*Thanks Gary, for your really helpful reply! All these details are brilliant. Picking out a couple in particular, for external storage, would you recommend going for any cheap large ssd, so focus more on size than write speed, if all the hard work will be on the internal ssd? Now, whether the ssd in the refurbished T430 is up to the job in terms of writing speed, is another matter... it certainly isn't an M.2 or nvme type. And your comments on exposure times and use of AP, very useful. I guess I could have both to start with.

Hi Mark,
Many thanks for the compliment

In terms of your computer gear, I'd recommend the following :-

1. Assuming you use your AAP in local mode, buy a large SSD with reasonably fast write speed.
The RAM inside the AAP spools images to the disk while the next image is being exposed, so write speed is not the main consideration.
But if you copy your files to another drive for processing, you want something with a very fast read speed.
Of course, if you get one, you usually get the other.
Also have TWO SSDs in case one becomes faulty, particularly if you image in the field.

2. Try performing a read/write speed test on your internal RAM, then match the R/W speed of your SD card to that, plus a 50% margin.
No point paying for extra speed on the SSD if your PC can't make the most of it.

3. The AAP has a 256 GB internal SSD which is pretty fast (RW = 121/95 MB/sec).
That's more than enough to store all your images for a night (256 GB will store about 2,500 APS-C RGB images), so you don't really need an SD card.
But it does make things easier if you want to copy images to your PC without using a network.
Of course, you can copy images direct from the AAP to your PC via WiFi, which can take a very long time - or ethernet, which is much faster.
But it's still a good idea to have an SD card handy just in case you run out of memory ...
It happened to me once on my AAP after I forgot to erase the images from the previous night's imaging.

4. For storing all your image files, it is *really* risky to use an SD card or USB stick.
I highly recommend against this.
USB sticks have a finite failure rate, so if the drive fails, you could lose everything.

Much better to invest in an inexpensive SSD RAID drive for storing all your RAW and processed images.
RAID gives you redundancy, so one SSD can fail completely and you won't lose any data.

Considering the cost of your mount, and the cost of all your other gear, IMHO it's definitely worth investing in a good RAID - just part of the overall package.

Just one other thing to follow on my my earlier comment ...
In terms of the ideal exposure time - that depends on many factors - the best thing is to experiment, but around the 3-4 minute mark is a good place to start - an AZEQ6 is certainly up to the task. It totally depends on your equipment, the target and atmospheric conditions.

By 'atmospheric conditions' of course I'm referring to seeing. Seeing is composed of a number of elements - fast turbulence, slow turbulence and short-term density changes.

One way to reduce the effects of fast turbulence is to use really short exposures - in the order of milliseconds. Anything longer than that makes little difference in terms of fast turbulence.

To reduce the effects of slow turbulence you can use short exposures - in the order of seconds. Anything longer than that makes little difference in terms of slow turbulence.

To reduce the effects of short-term density changes you can use limit exposures to less than a few tens of seconds. Anything longer than that makes little difference in terms of short-term density changes.

See as example of seeing in the short movie I posted on Astrobin here.
You can see the fast and slow effects, both of which will affect any exposure of more than a second or so.

So, although better seeing and shorter exposures will always give you sharper images, any exposure exceeding a few seconds will still suffer from the effects of seeing. But shorter exposures will also suffer from more noise.

As I said before, the best thing to do is experiment. Try imaging a single target on the same night using different exposures - 1/2/3/4/5 minutes, and make sure to record the seeing. Measure the noise and star size in each set of RAW images and in the stacked result - that will be your best guide.

Cheers,

Gary

*Thanks again Gary, for this useful info. My initial plan was to use the memory on the AA plus for dso AP, but in the case of planetary, to directly connect the imaging camera (zwo 224mc) to the laptop. I did consider changing from AA plus to AA mini, and using SD cards in the dslr for dso. Not sure on this route though.
Like
Gary.JONES 5.77
...
· 
Hi Mark,
OK - so you plan to use your AAP for DSO, and your laptop for planetary imaging.

I never used my AAP for planetary, but it does support planetary imaging, so would expect it to be reasonably capable, providing you choose the right settings.

What is your reason for using your laptop rather than the AAP ?
What app do you plan to use on your laptop to capture images ?
Will your laptop be able to provide the bandwidth required ?
How will you drive your mount to do a polar alignment and track your planet ?

The issue of course is image capture speed, which needs to be much higher for planetary than for DSO.
Your camera is 1,304 x 976 px = 1.3 Mpx, so the file size for a single frame at full resolution and bit depth will be about 1.3M x 3 x 12 bits / 8 = 5.7 MB.
At that resolution, the maximum frame rate is 64 fps, so the video bandwidth will be = 5.7 x 64 = 365 MB/sec.

The write speed of the eMMC RAM in the AAP is 95 MB/s, so, if my arithmetic is correct, it doesn't seem possible for the AAP to capture images from your camera at full resolution and frame rate.

So, you have 4 options :-
1. Use a lower frame rate;
2. Use a lower resolution - bandwidth is proportional to resolution - but that might sacrifice image quality, depending on your target and focal length;
3. Use a combination of 1 and 2;
4. Use a capture device with a faster frame rate - which would be limited by the USB 3 port @ 5Gb/s - which would easily handle 367 MB/sec = 2.9 GB/s.

IMHO, trying to capture images at that bandwidth on a PC could lead to lots of frustration, and is still limited by the PC's SSD write speed. I tried using ASIAir on a desktop device, but was unable to get it to work reliably - and you still need something to manage your mount and do your polar alignment etc.

The AAP is designed to provide a simple solution for most imaging applications, which is its core strength. Its set up for DSO and planetary imaging, and provides great support for ZWO cameras and most mounts.

My advice would be to stick with the AAP for planetary, but choose a frame rate that fits within the AAP's 95 MB/s speed limit. Something like 95/5.7 = 16 fps would be the maximum possible - lets say 8 fps to allow for processing overhead - that should be well within the capability of the AAP, and is easily fast enough for most planetary work.

I suggest you run a few experiments - set up your AP and camera inside, and see how it performs capturing full resolution images at various frame rates. I'm not 100% certain, but would expect the AAP to tell you if it drops frames. Then select a frame rate that provides a reliable image stream, and use that for some real imaging.

I hope that helps

Gary
Like
 
Register or login to create to post a reply.