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 - GordonH

Pages: [1] 2
Bug Reports / Re: TVGDenoise Corrupts Image
« on: 2019 February 04 11:24:53 »
Thanks for the info on RAM useage. I took a look by opening the Windows Resource Monitor to track RAM useage while TVGDenoise was not running compared to running. (See the graph attached.) On my system TVGDenoise barely shows up on the graph. You can just see the uptick in usage about 4 segments from the left in the graph.  Increase in RAM was about 1 MB. (My system has 24 MB so I'm have some headroom.


Bug Reports / Re: TVGDenoise Corrupts Image
« on: 2019 February 02 07:40:32 »

Bug Reports / Re: TVGDenoise Corrupts Image
« on: 2019 February 01 14:50:47 »
I was mistaken earlier - the project size 6.08 GB.

I did go back and do some experimenting. I increased the convergence value from .004 to 1.0 with the same result. I then applied a inverted luminance mask on the image, again with the same result.

I then rolled back the processes to before the first TVGDenoise and then reapplied all the steps. Then applied the TVGDenoise (@.004 level) and all worked as expected. It appears that multiple applications of TVGDenoise is the problem.

If you still want me to upload the project I will. Let me know the best way.


Bug Reports / Re: TVGDenoise Corrupts Image
« on: 2019 February 01 07:47:25 »
I created the project. Its 29.6GB. The "Attach" option will not accept the project - I think because its a directory not a file. Is there another way of uploading the project?

I re-ran TBGDenoise again this morning. Windows did an update overnight and I wanted to make sure this wasn't an operating system bug. I re-ran on the preview and it converged after 142, 186, & 171 iterations. When run on the full image it never converged and went the full 1500 iterations set for. I'm not aware of that ever happening before. I had run TVGDenoise earlier in my processing with no problem, but, I did some more stretching and wasn't happy with the noise in the now brighter areas. The convergence value was still set to the default .004 level.

I will re-run at a higher limit to see what happens.

Thank you,

Bug Reports / TVGDenoise Corrupts Image
« on: 2019 January 31 12:08:38 »
TVGDenoise is corrupting my image. It worked fine in a preview, but, when I applied it to the image a part of the image turned black. I tried rebooting my PC and reloading from a project with the same result. I tried it in RGB/K mode and in CIE L*a*b* mode with the same results. See attachment

The image is a 64 bit if that matters. PixInsight is up todate Version

Gordon Hansen

Bug Reports / Re: PI Will Not Open (No Access Violation or Dell)
« on: 2017 August 31 14:15:11 »
I'm having a similar issue. Sometimes when I exit out of PI (using the "X") and then try to restart it later all I get is the spinning circle. I started monitoring my Windows 10 system using the Resource Monitor - Memory tab and the Task Manager. When exiting PI the PixInsight.exe process in the Resource Monitor will change from normal print to grayed out and ultimately disappear. It also disappears immediately from the Task Manager.
Sometimes the PixInsight.exe process disappears from the Task Manager but stays in normal print in the Resource Monitor and doesn't disappear with time. That's when PI will not restart. If I re-boot the computer PI will restart.

Today I did some searching on the web for processes that don't terminate properly. What I discovered is if I open an Admin level command prompt window you can type Tasklist and you will get a list of running processes similar to the Resource Monitor. I did that when PI would not restart. The PixInsight process was not listed. However, I entered:

Taskkill /PID xxxx /F        (where xxxx was the PID number listed next to the process on the Process Monitor)
The process reported success, the PixInsight.exe disappeared from the Resource Monitor, and then I could restart PI.

I'm over my head here. I don't know if this is a Windows bug or a PI issue.


New version out today put it back.



Thanks, I should have payed more attention.

That did the trick.


I tried the new LocalNormalization with the Output Files stored in the same directory as the previously registered images.  The process runs to conclusion with a ".xnml" file for each of the image files.
In ImageIntegration I set Normalization to Local normalization but get:

"Warning: Local normalization data not available - No normalization will be applied!

Note: The image files are RGB

What am I missing?

My screen resolution is 1920 pixels wide and the button is missing.


Release Information / Extract Luminance
« on: 2017 August 06 12:46:50 »
The Extract Lightness icon disappeared from the Image Toolbar in the latest release. Can that be restored?


New Scripts and Modules / Re: Annotation script
« on: 2017 July 03 12:01:49 »
Changing the FITS to "bottom-up" solved the problem. I had to go back to my original "RAW" images to make it work. It also fixed the plate solve. Interestingly, re-orienting the XISF files to match that of the bottom-up FITS still will not solve.

Thanks for your help.

New Scripts and Modules / Re: Annotation script
« on: 2017 July 01 11:01:26 »
I've used the script in the past with no problems, but, now I have an issue. When I run the script the annotated image is produced, but, all the text is mirrored around the horizontal axis. Some processing details: I attempted to plate solve with ImageSolver, but, it fails. I took the same image and plate solved with TheSkyX with no issue. I then re-opened in PixInsight. I've atgtached a jpeg of the annotated image and a screen shot shot showing the FITS header.

Registration was done after debater. The initial processing was done with the BatchPreprocessing. Additional integration attempts were done with the debayered-aligned images. (For clarification, the attached image was the extracted luminance channel.)


I imaged NC925 and while processing I noticed a "checker board pattern" in the background and persists into the higher signal area of the galaxy itself. The pattern runs at an angle to the row/columns of the sensor pixels. I've attached a grossly overstretched image to illustrate the conditions.

The images were taken with a Canon 6D DSLR using an AstroTech AT10RC scope. Acquisition software is TheSkyX Camera Add-in.  I've been using this combo for about the last 9 months and have not seen the pattern previously. I did go back and check some previous images.

I initially used 38 - 8 minute subs (I image from pretty badly light polluted skies and needs lots of subs!) I dithered these subs with an off-set of 10 pixels on the guide camera (translates to about 26 pixels on the image.) After seeing the pattern I inspected the individual subs, the master bias, dark, and flat and could not discern the pattern. I then stacked groups of 10 subs from the beginning and end of the run. The pattern appeared. I initially stacked using LinearFit, but, also tried WinsorizedSigma.

My next thought was some kind of relationship to the dithering pattern (TheSkyX seems to move the same number of pixels between each sub??) I re-imaged the target about 3 weeks later (I live in Michigan - you don't get many clear nights!) this time with the dither set to 5 pixels. Same result. I then stacked all the images together, tried the different rejection techniques and then started over with all the frames and used the Bayer drizzle routine in BatchPreprocessing. That's what was used for the attached image.

I also separated and inspected  the R - G - B channels from the integrated image. The pattern appear in all three channels, but, more noticeable in the red.

If the pattern were aligned with the sensor I would blame the camera. The fact that its on an angle leaves me puzzled.

Any ideas / help will be appreciated.


Pages: [1] 2