37 replies to this topic

[rj144]

What is your thought about GIMP processing (just after Siril stacking)?

What is GIMP vs. Siril processing, is Gimp loose more pixels vs Siril?

Is that Levels and Curves "ancient technique", like @jml70 said, only in Photoshop, or Gimp too?

Can I process in Gimp?
Gimp processing seems to me easier than Siril processing. And in Gimp I got more red color on M27, which I need.

I recommend learning Siril.  It will do a much better job than using a photo program like GIMP.

[Smurf]

Whatever workflow produces the outcome you want is 100% valid.

 

BQ

Wow. Great.

 

I noticed some that change Ex.speed during shooting season and that stuck together, if I understand good.

 

Can we change ISO or Ex.seconds during shooting season and that all stuck together?

 

Tonight might be clear sky, after long, long time

[BQ Octantis]

I do not understand your question.

 

Yes, you can take longer exposures and stack them with shorter exposures—if that's what you mean—but you need to do weighted stacking. You can also do proportional summing with pixel math if you know the ratios.

 

We already covered that there is no benefit to changing ISOs.

 

BQ

[Smurf]

I do not understand your question.

 

BQ

 

Because someone in one group shared a message like:

Approximately 10h of 10 and 20-second exposures of the Iris Nebula.
Stacked and processed in Pixinsight. Drizzle x3. 

So I wonder can we do that, but I see that is harder than I thought because of math, so I will skip this.

[Smurf]

Guys. Is normal that stacking of 2h data need 150GB free space? I left 140gb of space, did not work, but only 150 working

I have only 250gb disc. But right now I upgrade my PC and mean to buy 1T SSD.

Also, do you delete all stacked files after stacking finish snd only save result.* files?

[rj144]

Guys. Is normal that stacking of 2h data need 150GB free space? I left 140gb of space, did not work, but only 150 working

I have only 250gb disc. But right now I upgrade my PC and mean to buy 1T SSD.

Also, do you delete all stacked files after stacking finish snd only save result.* files?

We need to know what software you're using.

[Smurf]

We need to know what software you're using.

 

I stacking in Siril.

[Smurf]

Guys. Is normal that stacking of 2h data need 150GB free space? I left 140gb of space, did not work, but only 150 working

I have only 250gb disc. But right now I upgrade my PC and mean to buy 1T SSD. Is 1T enough space?

Also, do you delete all stacked files after stacking finish snd only save result.* files?

I stacking with Siril.

Edited by Smurf, 29 June 2024 - 05:30 PM.

[BQ Octantis]

Guys. Is normal that stacking of 2h data need 150GB free space? I left 140gb of space, did not work, but only 150 working

I have only 250gb disc. But right now I upgrade my PC and mean to buy 1T SSD. Is 1T enough space?

Also, do you delete all stacked files after stacking finish snd only save result.* files?

I stacking with Siril.

The size of 2 hours depends on the sub duration, pixel dimensions, and bit depth. I use a 500 GB external USB on my processing server, and I find it to be sufficient for a few hours (4+) of 14-bit 18MP raws out of my DSLR (which Siril immediately converts to 16-bit FITS files after calibration). Siril creates a metric crap-ton of intermediate files (it was worse when the registration step had yet another set of files), but I've never come to even 50% of the drive capacity. There is no reason to keep the intermediate files—just the final FITS file if you plan to try different techniques or software and want to skip calibration. But I keep my raws in permanent storage with online backup.

 

BQ

[BQ Octantis]

I recommend you head over to the planetary forum for advice on planetary.

 

https://www.cloudyni...netary-imaging/

 

Post your questions there and they'll get you sorted.

 

BQ

[Smurf]

.

.

 

Registration 

 

Hi, these days I tried combinations of Siril registrations.

 

Note that the test was on ALT-AZ mount, and test material time like 1–2 hours.

When I pre-processing lights automatic with script, I figured out that I finished in many cases with too low number registered pictures — only 10-60% registered (but more like 10-20%).

Then I tried MANUAL stacking → "Automatic Image Registration". I got 50% or more registered images. That is a big difference.

"Global Star Alignment" on 10 stars 8% registered, on 6 stars 81%, 5 stars 83%, 4 stars 83%.

 

"1-2-3 Stars Registration"

-checked Follow Star Movement 0.20%
-non-checked Follow Star Movement 3.63%.

I thought that checked "Follow Star" gives me more registered pictures on Alt/AZ, because of sky rotation, but not.

How much do you usually have registered pictures?

I assume that is better to have more registered pictures, but would I just bring bad picture in stacking with that?

Edited by Smurf, 28 July 2024 - 07:29 AM.

[BQ Octantis]

I always get 100%. But I use an equatorial mount.

 

BQ

[Smurf]

Here I am! I am now „more in“ than before. I rebuild my PC including SSD. Also I switched from the Samsung Galaxy S7 to S20, which you already know!

Ok, after seasons of auto-stacking Lights in Siril with scripts, now I am learning manual stacking lights, but my stacking not work! I got always this two warnings:
MAD is null. Statistics cannot be computed.
Normalization failed. Check image 156 first.
Stacking failed, please check the log to fix your issue.

My Stacking settings are:
Method: Average stacking with rejection.
Normalisation: Additive with scaling.
Rejection: Winsorized Sigma Clipping.
Weighting: Number of Stars.
Image Rejection: selected
Output normalisation: yes
RGB equalization: yes

Errors I got in any seasons. Registration goes normal (like 157 of 335, normally for me).

Did I try repair what logs suggest me? Yes.
In every stacking show me about 10 numbers image warnings.. I remove (uncheck) that 10 pictures, stack againg, and after that it shows me new warnings with other numbers of pictures. That process I can repeat unit ALL pictures are deleted, there is no end! (tested at 50 pictures, all I deleted). So, it seems that Siril not accepts any of pictures with current setting: „Normalisation: Additive with scaling“ (or any other normalisation).

WEIRD THING:
How is possible that SCRIPT (OSC without DBF)

successfully finish stacking process with included „Average“ and „ Additive with scaling" (in text log)???? I confused, why not work manual? Is that means that must work in manual stacking too?

 

METHOD WHICH WORK:
Otherwise, I found a method which works: disable Normalisation, like:
Method: Average stacking with rejection.
Normalisation: None

Is it normalisation important and how much? Does it ruin a picture if is disabled?

Also working Sum stacking and Pixel (min and max) stacking, which have normalisation disabled by default, but it seems to give me the worst results in the image.

I remind you that I have ALT/AZ mount, where I have field rotation. My target not all time in season
„in center“, I check it every 15-30 minutes and sometimes must recenter position. Maybe because of that normalisation failed.

I saw in log some .log "memory" word, is it problem in memory PC?

 

With pictures I am sending my main stacking log (which not work) and script stack log (which work) to compare.

Attached Thumbnails

• 
• 

Attached Files

•  logs.zip   127.2KB   1 downloads

Edited by Smurf, 08 January 2025 - 02:28 PM.