Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - pfile

Pages: [1] 2 3 ... 299
1
General / Re: Understanding SNR Weight graph in Pixinsight
« on: 2019 December 11 17:54:31 »
if you were measuring eccentricity then that would say something about how good your guiding/tracking is. but this is an SNR (signal-to-noise ratio) weight plot.

still, since more than likely you'll have several worm periods in any given frame, i don't think the eccentricity measurement would say anything about your PE when measured from frame to frame. the periodic error would probably just manifest as RA elongation (eccentricity in the RA direction).

anyway: this is what mike schuster said about the SNRWeight measurement in the original SFS script documentation

Quote
The signal to noise ratio weight estimate for the subframe. SNRWeight equals MeanDeviation2 / Noise2. SNRWeight is unnormalized approximation to the current NoiseEvaluation weight used by the ImageIntegration process. In a subframe integration, the ratio between a subframe's SNRWeight and the reference subframe's SNRWeight approximately equals the NoiseEvaluation weight of the subframe.

The significance of the unnormalized SNRWeight and the normalized NoiseEvaluation weight is that a weighted subframe integration using these weights is an approximate maximum likelyhood estimator for pixel values that correspond to background limited targets, without requiring additional information such as exposure times or sensor parameters. See the ImageIntegration documentation for more information.

Note that SNRWeight and NoiseEvaluation weight are relative and not absolute measures of signal to noise ratio. Their formulation assumes that the subframes represent observations of the same target and that the subframes have similar background gradients

does the Median parameter correlate with this graph? maybe the steady decline indicates worse and worse gradients in the images. not sure.

rob

2
hmm, what is the source of these images? it seems like the flattening is bad and there was RBI preflash in the lights but not in the darks. however that's just a guess as the striping is not consistent.

what kind of camera is this and what kind of shutter does it have? what is the duration of the flats?

rob

3
New Scripts and Modules / Re: StarNet - new module for star removal
« on: 2019 December 11 12:36:06 »
hi walter, i think after that happens, if you go into the system preferences and click on "security & privacy" there will be a button in the lower half of the window mentioning the dylib and a button that says "install anyway" or something like that.

i don't have 10.15 on any of my machines so i can't test, but i think others reported being able to override this and get it installed on 10.15

rob

edit: i should say that after clicking that you probably need to re-try installing the module from within pixinsight. i think clicking the button only marks the .dylib file as being safe, it doesn't actually install it.

4
General / Re: Problem stacking
« on: 2019 December 11 11:28:24 »
since it's a DSLR my best guess is that with Dark Optimization turned on, there are too many residual hot pixels left in the calibrated frames. StarAlignment (which gets called from the BPP script) is presented with a huge number of these hot pixels which it has interpreted as stars, and as a result registered all of the files with no offset at all. so the c_d_r files are identical to the c_d files. it then stacks the c_d_r files but since they aren't actually aligned on the real stars, you get what you ended up with.

you need to increase the noise scales and the hot pixel suppression in StarAlignment but i'm not sure you can do that from within BPP. you might have to run StarAlignment manually.

rob

5
New Scripts and Modules / Re: StarNet - new module for star removal
« on: 2019 December 11 11:24:38 »
just type

cd "C:/Program Files/PixInsight/bin"

into the pixinsight console and it will work.

rob

6
General / Re: Problem stacking
« on: 2019 December 11 10:41:23 »
that looks like what happens when you stack unregistered frames... are you using BPP or WBPP or doing it manually?

rob

7
do you mean does the keyword's name change from WBPPWGHT to something else?

i don't know but i wouldn't expect it to. i havent yet used WBPP for any project, plus i don't use a DSLR anymore...

rob

8
if you upload them to dropbox or google drive or whatever and share them, you can post the link here and someone can look.

rob

9
General / Re: Can't get a mosaic with GradientMergeMosaic
« on: 2019 December 10 13:41:19 »
looks good, looking forward to the RGB.

only thing i would say is that on the left the color is a little different so i wonder if there is a gradient in that half that didn't get removed?

rob

10
looks pretty good -

what was the total exposure time for the O3? it wouldnt be uncommon for me to need 10-20h of OIII with a f/5 telescope.

rob

11
New Scripts and Modules / Re: StarNet - new module for star removal
« on: 2019 December 10 13:34:02 »
looks like an extra argument here:

rgb_starnet++.exe rgb_test 5.tiff  .tif  rgbtest5_s.tif 64

should be

rgb_starnet++.exe rgb_test_5.tiff rgbtest5_s.tif 64

note that you can't have spaces in filenames in a command line without escaping them somehow, so you should rename the input file to not have spaces for ease...

rob

12
General / Re: Process Icons
« on: 2019 December 10 08:59:19 »
try changing directories to your home directory or a folder inside your home directory before saving. you should get a standard mac dialog box popping up when you try to save your icons, and from there you can switch folders.

the application folder is write protected, which is normal as it's a part of a strategy to prevent viruses and malware... and even if it weren't it's not a good place to save user data.

rob

13
General / Re: LRGB Combination...doing something wrong?
« on: 2019 December 09 20:03:54 »
just make sure that you obtain new darks/bias if you end up changing gain. as long as you already have matching darks or bias for the flats you've taken you'll be OK as long as you still use those darks/bias when calibrating the flats.

rob

14
General / Re: Can't get a mosaic with GradientMergeMosaic
« on: 2019 December 09 11:19:28 »
GMM requires the input images to be the same size as the final image. so i think the trouble is the step where you have cropped the images.

in your case one image should be black on the left and contain the nebula on the right, and the other should be black on the right and contain the nebula on the right. both images should have the same dimensions.

you shouldn't have to do any cropping; whenever you are making a mosaic you either need a reference frame that spans the entire mosaic, or you need to use MosaicByCoordinates which will generate input files in the fashion that GMM expects.

rob

15
General / Re: LRGB Combination...doing something wrong?
« on: 2019 December 08 22:26:30 »
the pixel levels in your L image are exceedingly low... i had to use a 24-bit LUT to see anything. that's not normal... i don't know what went wrong to cause that as i've never seen that problem before.

i didn't look at the RGB masters.

one thing about the LRGB combination tool is that it should be used on stretched images. were you doing that?

the way to do this is to create an RGB image from the RGB masters, do-pre stretch processing (like DBE, linear noise reduction or color calibration), stretch the image (HT, curves) and then do any post-stretch processing you might want to do (non-linear noise reduction, additional saturation boost, etc.) then you process your L image in a similar fashion and stretch it to a similar brightness as the RGB image. finally you specify just the L image in the LRGB process and apply it to the RGB image, thus replacing the L component of the RGB image with your L image.

in short, maybe you need to read those intervening 100 pages :)

rob

Pages: [1] 2 3 ... 299