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.


Topics - Salvatore Giambruno

Pages: [1]
1
Bug Reports / Shared Image Reference
« on: 2017 November 23 16:41:39 »
This happened when I tried to close a separate image that I created as a CLONE OF A PREVIEW on a main image.  I use this technique to speed up previewing my MMT settings because using a preview that is still attached to the main image to preview MMT settings seems to want to process the entire main image (in cache) and seems slower than creating a separate preview image.  The problem with using this workaround now seems to be that Mask preview enabling/disabling (on the separate-image preview) is not working consistently when previewing MMT changes, and when I go to close the clone of the preview, I get this error message.

Restarting the application does not solve the problem.

2
I'm not sure if this technique has been covered by anyone before or if I am a the first, but a brief search of this forum and Google turn up nothing as far as I can tell, so I thought I'd share it here in any case.

Briefly, you create a good star mask from your final image (or any of its derivations) using the StarMask process (or by whatever method you prefer), invert the resulting star mask (stars to black), then use that star mask as a map in the DefectMap process to and apply it to the image. 

This technique works VERY well and results in very little degradation to image detail.  The larger stars usually require additional touch-up because as a large "defect" they are replaced with a wide average of the background which is apparent even after the application of the star removal process.

The key to using this technique effectively is to create an accurate star mask to begin with.  If one mask doesn't remove all the stars, simply create another star mask at the scale required to get all the stars you need at a particular scale.






3
I was asked by the program to report this, so here it is:

Internal error: MainView::~MainView(): Unexpected shared image reference:
Image112_clone
This denotes corruption of internal data structures. To stay on the safe side, save your data, exit the application, and start again. Please report this problem to our development team.

4
Bug Reports / Dynamic PSF Window Causing Errors and Disappearing
« on: 2017 October 16 23:24:35 »
Dynamic PSF caused an error to appear (I think access violation) when I tried to close the interface.  I just ignored it.  When I tried to open another dynamic interface, I got an error saying itcouldn't be opened becuase PSF was already open but the window was nowhere to be found.  I tried closing the project (after saving), but that process merely aborted.  I closed all the image windows hoping it would disconnect the ghost dynamic PSF interface but then I got this pop-up:

"Internal error: MainView::~MainView(): Unexpected shared image reference:
Image821_clone
This denotes corruption of internal data structures. To stay on the safe side, save your data, exit the application, and start again. Please report this problem to our development team."


After this, tried to exit PI and got this pop-up:

"At address 00007FF6C4CAC8DB with exception code C0000005 :
Access violation: invalid memory read operation at address 0000000000000008"


Tried opening another project and got this in the console:

Loading project:
F:/Astronomy/PI/PROJECTS/SH_2_162 Bubble Nebula.xosm
* Project integrity verified, SHA1 checksum = 25b84683ba5a5e0d7fda8504d3fc185de832dfaa
*** PCL Win32 System Exception: At address 00007FF6C4CAC8D7 with exception code C0000005 :
Access violation: invalid memory read operation at address 0000000000000028

<* abort *>



Sal

5
Bug Reports / Pixinsight Not Responding after Wake From Sleep
« on: 2017 September 19 10:10:52 »
Pixinsight Version 01.08.05.1353 (x64) fails to resume (becomes unresponsive and must be force-closed) after computer resumes from sleep. 

The computer system is a relatively new Dell setup: AMD Ryzen 1700x with 12G DDR and Nvidia GTX 1070 running on Windows 10 Home 64-bit.  Other than this, the program appears to run flawlessly.  I also run PI on an Intel system and normally don't put it to sleep but tested PI sleep recovery on that machine and it appears to work just fine.

The only thing I suspect at this point is an external USB mechanical disk drive on the AMD system because it has hesitated in the past and I am using it as my data drive with PI.

While PI is unresponsive, Task Manager shows its process is consuming 7-7.5% (variable) of CPU resources and 408.4MB (unchanging) of Memory resources.  The PI process shows no disk or network activity.

6
Image Processing Challenges / Is this a processing problem?
« on: 2017 July 11 10:19:34 »
I'm experiencing the following checker patterns (from dithering exposures it appears) after processing Ha images the way I normally process my LRGB images (which have no problem).  Has anyone seen anything like this before?  Any help appreciated. See photo attached.

Pages: [1]