User Palette in Settings

AutoIntegrate
1

Hello Jarmo.

This is probably a basic and well understood process, but it baffles me.

I’ve been looking at various user settings for use on my images for narrowband mapping.
I’ve now got access to a 14 inch telescope with a 44mm x 33mm IMX 461 CMOS sensor.
I’m enjoying the built in ones and what I’m able to achieve but want to experiment more.
I see some written for example SHO

R = (Oiii^~Oiii)Sii + ~(Oiii^~Oiii)Ha
G = ((OiiiHa)^~(OiiiHa))Ha + ~((OiiiHa)^~(Oiii*Ha))*Oiii
B = Oiii

also like these

R=(OIII^~OIII)SII + ~(OIII^~OIII)Ha)
G=((OIIIHa)^~(OIIIHa))Ha + ~((OIIIHa)^~(OIIIHa))OIII
B=OIII

R= (O^~O)S+~(O^~O)H
G= ((OH)^~(OH))H+~((OH)^~(O*H))*O
B= O

They don’t always work.
Is there a specific way to write them

CS
Peter

2

Hi Peter,

Those formulas are passed directly to PixelMath but before that single letters LRGBSHO are replaced with filter image names. So the format must be compatible with PixelMath.

If you look for example Dynamic SHO palette in Color palette dropdown the R channel looks like this:

(O^~O)*S + ~(O^~O)*H

So for multiplication you need to add * etc.

The code for replacing channel names with image names is a bit tricky so it is also possible that there is a bug. In that case it would be great if you can pass the bad formula to me.

Note that in my understanding those dynamic palettes work best with stretched (non-linear) data. So you may want to check that option (narrowband mapping using non-linear data).

Jarmo

3

Hi Jarmo.

Thank you for the clarification. It was the way to write them that was confusing. I know that *7H plus *3O must always =1 and not more. I don’t think it is a bug, more my not understanding how they work. I can experiment and see what comes out at the end.

Peter