Jump to content

16 hours plus maybe another 8


Recommended Posts

1 hour ago, Clarkey said:

I won't run a BE. However careful you are, there is always the risk of losing detail running DBE or similar. If it ain't broke.......

The one thing I am yet to do is image a target that fills the sensor edge to edge, then I think I have to be more selective or not use it at all. I am however surrounded by LP from all sides so have to use it for pretty much everything.

Link to comment
Share on other sites

1 hour ago, Clarkey said:

Although very useful, there are quite a few occasions when I do not use any BE. If I cannot see any obvious gradient in the stacked image, I won't run a BE. However careful you are, there is always the risk of losing detail running DBE or similar. If it ain't broke.......

yeah i think rather than me using BE automatically, i should treat each image separately. Having said that, i tried it on a gradient free looking stack and it went badly :) very wishy washy looking maybe. so ill just check more closely and examine the extracted background before moving on.

Link to comment
Share on other sites

On 27/09/2024 at 08:50, TiffsAndAstro said:

It does? Only in fit header or?

If I work on a file in siril, save it and reload it any undo history disappears.

Where is this processing history window? :)

Been away for a few days, so here is my late reply!

I've just run a test, and this is the window that Siril gives when saving as a TIFF file:

image.png.fe875c0e9074b1fc47416b0a4b7e2fd3.png

Below, in italic, is the full copy+paste, and I can also see the same type of "History" data saved at the bottom from Fits files, and even PixInsights XISF file format on other files that I have just looked at. You can also add your own text to this if you like, before saving.

SIMPLE  =                    T / file does conform to FITS standard
BITPIX  =                  -32 / number of bits per data pixel
NAXIS   =                    3 / number of data axes
NAXIS1  =                 3538 / length of data axis 1
NAXIS2  =                 1990 / length of data axis 2
NAXIS3  =                    3 / length of data axis 3
EXTEND  =                    T / FITS dataset may contain extensions
COMMENT   FITS (Flexible Image Transport System) format is defined in 'Astronomy
COMMENT   and Astrophysics', volume 376, page 359; bibcode: 2001A&A...376..359H
MIPS-FHI=                    1 / Upper visualization cutoff
MIPS-FLO=                    0 / Lower visualization cutoff
BZERO   =                    0 / offset data range to that of unsigned short
BSCALE  =                    1 / default scaling factor
DATE    = '2024-09-30T23:08:14' / UTC date that FITS file was created
DATE-OBS= '2024-09-10T20:18:43.653000' / YYYY-MM-DDThh:mm:ss observation start, 
INSTRUME= 'ZWO ASI585MC'       / instrument name
OBSERVER= '        '           / observer name
TELESCOP= 'Starfield 102'      / telescope used to acquire this image
ROWORDER= 'BOTTOM-UP'          / Order of the rows in image array
XPIXSZ  =                  2.9 / X pixel size microns
YPIXSZ  =                  2.9 / Y pixel size microns
XBINNING=                    1 / Camera binning mode
YBINNING=                    1 / Camera binning mode
FOCALLEN=              574.424 / Camera focal length
CCD-TEMP=                   14 / CCD temp in C
EXPTIME =                  120 / Exposure time [s]
STACKCNT=                  413 / Stack frames
LIVETIME=                49560 / Exposure time after deadtime correction
EXPSTART=         2.46056e+006 / Exposure start time (standard Julian date)
EXPEND  =         2.46057e+006 / Exposure end time (standard Julian date)
IMAGETYP= 'LIGHT   '           / Type of image
OBJECT  = 'NGC 6946'           / Name of the object of interest
CVF     =             0.620981 / Conversion factor (e-/adu)
GAIN    =                  252 / Camera gain
OFFSET  =                   15 / Camera offset
CTYPE1  = 'RA---TAN'           / Coordinate type for the first axis
CTYPE2  = 'DEC--TAN'           / Coordinate type for the second axis
CUNIT1  = 'deg     '           / Unit of coordinates
CUNIT2  = 'deg     '           / Unit of coordinates
EQUINOX =                 2000 / Equatorial equinox
OBJCTRA = '20 33 32.093'       / Image center Right Ascension (hms)
OBJCTDEC= '+60 21 29.750'      / Image center Declination (dms)
RA      =              308.384 / Image center Right Ascension (deg)
DEC     =              60.3583 / Image center Declination (deg)
CRPIX1  =                 1769 / Axis1 reference pixel
CRPIX2  =                  995 / Axis2 reference pixel
CRVAL1  =              308.384 / Axis1 reference value (deg)
CRVAL2  =              60.3583 / Axis2 reference value (deg)
CDELT1  =         -0.000289257 / X pixel size (deg)
CDELT2  =          0.000289262 / Y pixel size (deg)
PC1_1   =            -0.231492 / Linear transformation matrix (1, 1)
PC1_2   =             0.972837 / Linear transformation matrix (1, 2)
PC2_1   =            -0.972825 / Linear transformation matrix (2, 1)
PC2_2   =             -0.23154 / Linear transformation matrix (2, 2)
PLTSOLVD=                    T / Siril internal solve
AIRMASS =              1.01239 / Airmass
HISTORY mean stacking with winsorized sigma clipping rejection (low=3.000 high=3
HISTORY .000), additive+scaling normalized input, normalized output, no image we
HISTORY ighting, equalized RGB
HISTORY TOP-DOWN mirror
HISTORY Crop (x=111, y=69, w=3538, h=1990)
HISTORY Background extraction (Correction: Subtraction)
HISTORY Photometric CC
HISTORY Asinh Transformation: (straaaetch=1000.0, bp=0.00000)
END

 

You can then access this information later on in Windows Explorer as below, by right-clicking the file, choosing properties and going to the Details Tab. Then you can copy+paste it to notepad (or word, etc) to see it all.

The "Details Tab" in Windows Explorer appears only on TIFF files for some reason, I've no idea why that might be. But you can actually open up a Fits file in Siril, then save as a TIFF, and the box (above) appears again with the history :) 

image.png.9cccc55ed320b910ab9d91cb6e28fc44.png

I used to save these histories into Notepad, and add my own notes to it, if for instance I edited 70% in Siril and then took it to GIMP, so I'd know exactly how I processed it.

  • Thanks 1
Link to comment
Share on other sites

9 hours ago, WolfieGlos said:

Been away for a few days, so here is my late reply!

I've just run a test, and this is the window that Siril gives when saving as a TIFF file:

image.png.fe875c0e9074b1fc47416b0a4b7e2fd3.png

Below, in italic, is the full copy+paste, and I can also see the same type of "History" data saved at the bottom from Fits files, and even PixInsights XISF file format on other files that I have just looked at. You can also add your own text to this if you like, before saving.

SIMPLE  =                    T / file does conform to FITS standard
BITPIX  =                  -32 / number of bits per data pixel
NAXIS   =                    3 / number of data axes
NAXIS1  =                 3538 / length of data axis 1
NAXIS2  =                 1990 / length of data axis 2
NAXIS3  =                    3 / length of data axis 3
EXTEND  =                    T / FITS dataset may contain extensions
COMMENT   FITS (Flexible Image Transport System) format is defined in 'Astronomy
COMMENT   and Astrophysics', volume 376, page 359; bibcode: 2001A&A...376..359H
MIPS-FHI=                    1 / Upper visualization cutoff
MIPS-FLO=                    0 / Lower visualization cutoff
BZERO   =                    0 / offset data range to that of unsigned short
BSCALE  =                    1 / default scaling factor
DATE    = '2024-09-30T23:08:14' / UTC date that FITS file was created
DATE-OBS= '2024-09-10T20:18:43.653000' / YYYY-MM-DDThh:mm:ss observation start, 
INSTRUME= 'ZWO ASI585MC'       / instrument name
OBSERVER= '        '           / observer name
TELESCOP= 'Starfield 102'      / telescope used to acquire this image
ROWORDER= 'BOTTOM-UP'          / Order of the rows in image array
XPIXSZ  =                  2.9 / X pixel size microns
YPIXSZ  =                  2.9 / Y pixel size microns
XBINNING=                    1 / Camera binning mode
YBINNING=                    1 / Camera binning mode
FOCALLEN=              574.424 / Camera focal length
CCD-TEMP=                   14 / CCD temp in C
EXPTIME =                  120 / Exposure time [s]
STACKCNT=                  413 / Stack frames
LIVETIME=                49560 / Exposure time after deadtime correction
EXPSTART=         2.46056e+006 / Exposure start time (standard Julian date)
EXPEND  =         2.46057e+006 / Exposure end time (standard Julian date)
IMAGETYP= 'LIGHT   '           / Type of image
OBJECT  = 'NGC 6946'           / Name of the object of interest
CVF     =             0.620981 / Conversion factor (e-/adu)
GAIN    =                  252 / Camera gain
OFFSET  =                   15 / Camera offset
CTYPE1  = 'RA---TAN'           / Coordinate type for the first axis
CTYPE2  = 'DEC--TAN'           / Coordinate type for the second axis
CUNIT1  = 'deg     '           / Unit of coordinates
CUNIT2  = 'deg     '           / Unit of coordinates
EQUINOX =                 2000 / Equatorial equinox
OBJCTRA = '20 33 32.093'       / Image center Right Ascension (hms)
OBJCTDEC= '+60 21 29.750'      / Image center Declination (dms)
RA      =              308.384 / Image center Right Ascension (deg)
DEC     =              60.3583 / Image center Declination (deg)
CRPIX1  =                 1769 / Axis1 reference pixel
CRPIX2  =                  995 / Axis2 reference pixel
CRVAL1  =              308.384 / Axis1 reference value (deg)
CRVAL2  =              60.3583 / Axis2 reference value (deg)
CDELT1  =         -0.000289257 / X pixel size (deg)
CDELT2  =          0.000289262 / Y pixel size (deg)
PC1_1   =            -0.231492 / Linear transformation matrix (1, 1)
PC1_2   =             0.972837 / Linear transformation matrix (1, 2)
PC2_1   =            -0.972825 / Linear transformation matrix (2, 1)
PC2_2   =             -0.23154 / Linear transformation matrix (2, 2)
PLTSOLVD=                    T / Siril internal solve
AIRMASS =              1.01239 / Airmass
HISTORY mean stacking with winsorized sigma clipping rejection (low=3.000 high=3
HISTORY .000), additive+scaling normalized input, normalized output, no image we
HISTORY ighting, equalized RGB
HISTORY TOP-DOWN mirror
HISTORY Crop (x=111, y=69, w=3538, h=1990)
HISTORY Background extraction (Correction: Subtraction)
HISTORY Photometric CC
HISTORY Asinh Transformation: (straaaetch=1000.0, bp=0.00000)
END

 

You can then access this information later on in Windows Explorer as below, by right-clicking the file, choosing properties and going to the Details Tab. Then you can copy+paste it to notepad (or word, etc) to see it all.

The "Details Tab" in Windows Explorer appears only on TIFF files for some reason, I've no idea why that might be. But you can actually open up a Fits file in Siril, then save as a TIFF, and the box (above) appears again with the history :) 

image.png.9cccc55ed320b910ab9d91cb6e28fc44.png

I used to save these histories into Notepad, and add my own notes to it, if for instance I edited 70% in Siril and then took it to GIMP, so I'd know exactly how I processed it.

Amazing never realised. Ty so much for pointing this out

  • Like 1
Link to comment
Share on other sites

On 28/09/2024 at 13:48, Elp said:

It's most definitely the NR. I used to do similar with semi aggressive and ended up with similar. I've just upped the brightness on my display and it's clear, you don't see it so much with a lower brightness display.

Ok im not 100% certain yet, but, i don't think its graxpert's NR, but it might be siril's remove green noise, which i possible use too often in my workflow.

testing latest version of siril now see if it still occurs :(

Link to comment
Share on other sites

35 minutes ago, TiffsAndAstro said:

it might be siril's remove green noise

You don't really need to use this, if you use PCC your RGB peaks will align removing the excessive green (or you can do it manually afterward in an image editing program). I tend to do the latter as PCC at least after the initial operation looks to do weird things to the colour (likely it doesn't delete anything that can't be brought back via editing).

  • Like 1
Link to comment
Share on other sites

22 minutes ago, Elp said:

You don't really need to use this, if you use PCC your RGB peaks will align removing the excessive green (or you can do it manually afterward in an image editing program). I tend to do the latter as PCC at least after the initial operation looks to do weird things to the colour (likely it doesn't delete anything that can't be brought back via editing).

I tried again after updating to latest release and, so far, can't see any posterisation.

Can't see graxpert in siril yet, maybe it's only in beta.

Don't like my colours on latest version I've done, but that's a minor issue.

I'll post image if/when I think it's better than previous versions :(

Link to comment
Share on other sites

Ok, after many, many tests, exports, 16/32bit and seeing if my regular use of Windows 'sleep' was the cause, im 75% certain its having to high a NR setting in graxpert. 0.5 seems ok. 0.85 or higher seems not.

now to see if it appears after a sn++ etc. 

Link to comment
Share on other sites

Rich at Deep Space Astro uses 0.2 NR. Depends on SNR of course, but 0.8 likely too high.

NoiseXterminator is the bomb, BTW. Unfortunately not integrated in Siril, necessitates an export and NR in Affinity

  • Like 1
Link to comment
Share on other sites

2 hours ago, 900SL said:

Rich at Deep Space Astro uses 0.2 NR. Depends on SNR of course, but 0.8 likely too high.

NoiseXterminator is the bomb, BTW. Unfortunately not integrated in Siril, necessitates an export and NR in Affinity

Even 0.5 seems too little for my Cygnus wall effort, but I haven't experimented with it much

Link to comment
Share on other sites

Try to extract RGB channels, use R as Ha and a*G + b*B as OIII, where a and b are constants which you chose, like 0.4*G+0.6*B, and play with them. 

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

Posted (edited)
16 minutes ago, Vroobel said:

Try to extract RGB channels, use R as Ha and a*G + b*B as OIII, where a and b are constants which you chose, like 0.4*G+0.6*B, and play with them. 

Was sort of my plan as I *was* struggling with too much NR.

If you look at my earlier blue/yellow period I did roughly what you suggest. Seems just too much NR was my problem.

Hopefully will have some time to kill this evening so will try doing this with Ha/Oiii and with r g and b channels.

Spent most of day in hospital/a&e (not for me and not too serious :( ) otherwise I would have done it by now. 

I see blueish sky right now :)

Also for red channel 1.5*Ha - Oiii is possibly a weird but useful expression. 

I Really appreciate your advice as always

Ps - My stars are still NB and rather po* :(

Edited by TiffsAndAstro
Link to comment
Share on other sites

On 01/10/2024 at 00:22, WolfieGlos said:

Been away for a few days, so here is my late reply!

I've just run a test, and this is the window that Siril gives when saving as a TIFF file:

image.png.fe875c0e9074b1fc47416b0a4b7e2fd3.png

Below, in italic, is the full copy+paste, and I can also see the same type of "History" data saved at the bottom from Fits files, and even PixInsights XISF file format on other files that I have just looked at. You can also add your own text to this if you like, before saving.

SIMPLE  =                    T / file does conform to FITS standard
BITPIX  =                  -32 / number of bits per data pixel
NAXIS   =                    3 / number of data axes
NAXIS1  =                 3538 / length of data axis 1
NAXIS2  =                 1990 / length of data axis 2
NAXIS3  =                    3 / length of data axis 3
EXTEND  =                    T / FITS dataset may contain extensions
COMMENT   FITS (Flexible Image Transport System) format is defined in 'Astronomy
COMMENT   and Astrophysics', volume 376, page 359; bibcode: 2001A&A...376..359H
MIPS-FHI=                    1 / Upper visualization cutoff
MIPS-FLO=                    0 / Lower visualization cutoff
BZERO   =                    0 / offset data range to that of unsigned short
BSCALE  =                    1 / default scaling factor
DATE    = '2024-09-30T23:08:14' / UTC date that FITS file was created
DATE-OBS= '2024-09-10T20:18:43.653000' / YYYY-MM-DDThh:mm:ss observation start, 
INSTRUME= 'ZWO ASI585MC'       / instrument name
OBSERVER= '        '           / observer name
TELESCOP= 'Starfield 102'      / telescope used to acquire this image
ROWORDER= 'BOTTOM-UP'          / Order of the rows in image array
XPIXSZ  =                  2.9 / X pixel size microns
YPIXSZ  =                  2.9 / Y pixel size microns
XBINNING=                    1 / Camera binning mode
YBINNING=                    1 / Camera binning mode
FOCALLEN=              574.424 / Camera focal length
CCD-TEMP=                   14 / CCD temp in C
EXPTIME =                  120 / Exposure time [s]
STACKCNT=                  413 / Stack frames
LIVETIME=                49560 / Exposure time after deadtime correction
EXPSTART=         2.46056e+006 / Exposure start time (standard Julian date)
EXPEND  =         2.46057e+006 / Exposure end time (standard Julian date)
IMAGETYP= 'LIGHT   '           / Type of image
OBJECT  = 'NGC 6946'           / Name of the object of interest
CVF     =             0.620981 / Conversion factor (e-/adu)
GAIN    =                  252 / Camera gain
OFFSET  =                   15 / Camera offset
CTYPE1  = 'RA---TAN'           / Coordinate type for the first axis
CTYPE2  = 'DEC--TAN'           / Coordinate type for the second axis
CUNIT1  = 'deg     '           / Unit of coordinates
CUNIT2  = 'deg     '           / Unit of coordinates
EQUINOX =                 2000 / Equatorial equinox
OBJCTRA = '20 33 32.093'       / Image center Right Ascension (hms)
OBJCTDEC= '+60 21 29.750'      / Image center Declination (dms)
RA      =              308.384 / Image center Right Ascension (deg)
DEC     =              60.3583 / Image center Declination (deg)
CRPIX1  =                 1769 / Axis1 reference pixel
CRPIX2  =                  995 / Axis2 reference pixel
CRVAL1  =              308.384 / Axis1 reference value (deg)
CRVAL2  =              60.3583 / Axis2 reference value (deg)
CDELT1  =         -0.000289257 / X pixel size (deg)
CDELT2  =          0.000289262 / Y pixel size (deg)
PC1_1   =            -0.231492 / Linear transformation matrix (1, 1)
PC1_2   =             0.972837 / Linear transformation matrix (1, 2)
PC2_1   =            -0.972825 / Linear transformation matrix (2, 1)
PC2_2   =             -0.23154 / Linear transformation matrix (2, 2)
PLTSOLVD=                    T / Siril internal solve
AIRMASS =              1.01239 / Airmass
HISTORY mean stacking with winsorized sigma clipping rejection (low=3.000 high=3
HISTORY .000), additive+scaling normalized input, normalized output, no image we
HISTORY ighting, equalized RGB
HISTORY TOP-DOWN mirror
HISTORY Crop (x=111, y=69, w=3538, h=1990)
HISTORY Background extraction (Correction: Subtraction)
HISTORY Photometric CC
HISTORY Asinh Transformation: (straaaetch=1000.0, bp=0.00000)
END

 

You can then access this information later on in Windows Explorer as below, by right-clicking the file, choosing properties and going to the Details Tab. Then you can copy+paste it to notepad (or word, etc) to see it all.

The "Details Tab" in Windows Explorer appears only on TIFF files for some reason, I've no idea why that might be. But you can actually open up a Fits file in Siril, then save as a TIFF, and the box (above) appears again with the history :) 

image.png.9cccc55ed320b910ab9d91cb6e28fc44.png

I used to save these histories into Notepad, and add my own notes to it, if for instance I edited 70% in Siril and then took it to GIMP, so I'd know exactly how I processed it.

Also I just realised, .fit might be a txt file so I could keep them in vss and do diffs, maybe even merges on this stuff.

Maybe :)

Link to comment
Share on other sites

used a paired down selection of subs, 15.4 hours extracted Ha/Oiii and mixed them back up via pixel math. Turned out very similar to last image i posted :( Ran it through cosmic cleaner sharpness and denoise. Too sharp?

image.thumb.jpeg.863639c5eb295ed15da22eea8aec7533.jpeg

  • Like 1
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
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • 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.