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

Pages: [1] 2
1
General / Rev 1.8.8.4 on WIndows 10 crash dumps
« on: 2020 January 26 10:30:09 »
For some reason, I get a crash dump with PixInsight 1.8.8.4 on Windows 10 every time I load the program.  Haven't done anything at all except load the program and I get a ~26MB dump.  Everything seems to work OK, just the incessant dumps for no obvious reason!  Can't find anything similar on Linux Mint 19.3.

The Win10 Event Viewer shows:
-------------------------------------------------------------------------------
Faulting application name: PixInsight.exe, version: 1.8.8.4, time stamp: 0x5e1db5eb
Faulting module name: Qt5WebEngineCore.dll, version: 5.13.2.0, time stamp: 0x5dc1834c
Exception code: 0xc0000005
Fault offset: 0x0000000001c3d1c3
Faulting process id: 0xd00
Faulting application start time: 0x01d5d47522694db8
Faulting application path: C:\Program Files\PixInsight\bin\PixInsight.exe
Faulting module path: C:\Program Files\PixInsight\bin\Qt5WebEngineCore.dll
Report Id: 908fff17-257e-4528-a6fa-ef1319ea588c
Faulting package full name:
Faulting package-relative application ID:
--------------------------------------------------------------------------------

Anybody know anything about this?  I suppose I could uninstall/re-install but until I know what the problem is, I'd rather see what others might have found.

John

2
General / Missing scripts
« on: 2020 January 09 10:43:53 »
I have the latest PI installed on a Linux platform and Windows 10.  Both show the Linear Defect detection and Pattern Subtraction scripts as having been downloaded and installed but they don't show up in any of the script categories. As I recall, I had a similar problem a long time ago but I can't remember how I fixed it.  The Batch Channel Extraction script was installed at the same time and it shows up!

HELP!

John

3
General / NB processing problem
« on: 2018 August 05 18:45:26 »
Just started doing NB recently and ran into a problem I haven't been able to work around.  M27: I have my RGB image (and an LRGB version that turned out decent) but I want to combine some OIII and Ha.  Tried using the NB script but the result completely washes out the interesting interior of the nebula while adding to the faint nebulosity outside the main body.  The OIII and Ha images are very bright and somewhat featureless compared to the RGB image.

I've investigated a couple of NBRGB combination techniques and none seem to work for me on M27, other large nebulae, no problem, but M27 is giving me fits!  Someone point me in the right direction.

Thanks

John

ES127mm-FCD100, 0.7xFF, QSI-683

4
(1) I'm having a hard time understanding what's happening here. 

RGB data sets, all 3 uncalibrated images roughly the same minimum sky background levels (R about half B or G, B and G about the same).  After calibration, about the same ratios, nothing looks odd.  I integrate using LocalNormalization (AdditiveWithScaling has the same effect) and my integrated Green image is now 10% of the R and B (i.e., G background is .004 while R and B are closer to .030.  Stats shows about the same standard deviation in all integrated images but the average G is again 10% of the B and R images. 

If I disable normalization, the integrated G image is now similar to the B and R.  I've read the description of the processes but why I'm seeing such a huge scaling eludes me.  FWIW, my dataset was only some test images (15x60s of M81/82), not nearly enough and transparency wasn't all that good either but I'm at a loss to understand the results I'm getting.  Any help appreciated!

2nd question: I thought I had a handle on flats until I went from a long focus RC to a short focus refractor and a new camera.  Looks like my previous technique needs some adjustment but my question is this:  I've always abided by the conventional wisdom 1/3-1/2 the sensor's linear range but I'm wondering should a flat be in some way matched to the average image level, or average background, etc?  Something like that rather than some arbitrary level?  I've made flats using a flat panel at 3 different exposure levels for each filter and when I use the results to calibrate an existing dataset, I can get very different results.  I'd appreciate some advice...

5
General / LFHH script
« on: 2017 November 15 07:24:13 »
Probably me but I can't find the LFHH script.  Where is it supposed to appear?

John

6
General / Combining NB with RGB in a galaxy
« on: 2017 October 16 05:53:38 »
Been using the NBRGB tool and it works great for nebula imagery so I thought I'd try it combining NB in a galaxy image.  The galaxy NB shows the core and HII regions so when I do the combine, the galaxy comes out green...I tried masking just the HII regions but the mask doesn't seem to work.  Also tried the old extract-channels/pixel math/combine channels, etc, method and again the mask doesn't affect anything.

So two questions: how do you apply a mask to an image and save just the masked results? I can't seem to find a method to do that.

Second, I would appreciate someone pointing me to a technique to combine galactic HI regions to an RGB image.

Tnx


John

7
General / Batch preprocessing using master frames
« on: 2016 September 04 10:26:52 »
I thought I'd give the batch preproc script another whirl just to see how it compares with my manual process.  For some reason, it rejects all my master calibration files (including the superbias) and will only work if I use the original raw calibration data.  I created these master cal frames using the process described in the tutorials and they work properly with the Calibration Tool.

However, if I use the master calibration images created BY the script and run it again using these images as master calibration images, it will run to completion. 

Replacing the scripted-created master flat with my own and it again fails. 

** Warning: No flat frames have been selected to calibrate light frames (filter="Luminance", binning=2, exposure=30.00s, length=6)


What's it looking for that the manually created master flat don't have?

John

8
General / Confused after viewing online videos
« on: 2016 March 03 12:09:12 »
I thought I had a fair understanding of the use of some of the many options in PixInsight - until I viewed some online videos. 

Here's my question:  is there a concise guide as to when to use a function in linear or or non-linear image space?  I've been using most of the functions in linear space except the more obvious, e.g., HDR and Curves. 

I recently ran across a video demonstrating Deconvolution after the image had been run through Histogram processing - his results looked decent but I had thought Deconvolution is applied prior to Histogram processing.

9
General / Lost readout window on latest Linux
« on: 2015 September 17 11:15:53 »
Not sure exactly what I did but I seem to have lost my readout window (running on Linux Mint, Pixinisght V 01.08.04.1170 Ripley).  It was there until a few minutes ago, now all i see is the readout on the bottom of the screen.  Any ideas?

10
General / after the defect map...
« on: 2014 July 02 15:12:04 »
This has probably been asked a hundred times but I still can't quite understand what's happening. 

First, I can calibrate an image set in the usual way and everything is fine.  If I first use the defect map tool to remove hot pixels and THEN calibrate I get the warning message indicating an incompatibility between the image and the dark frame but the results appear to be identical at least as far as the stats go. 

If I uncheck Calibrate the Master Dark, no error message and the calibrated image is different from before (my master dark is 10min while most of my imaging is done at 3min or less due to light pollution).

The only thing I can see different in the Defect Mapped image versus the raw image is the format of EXPTIME and EXPOSURE header entries (one is scientific notation, the other is a decimal number, 60.)

Thoughts, any one?

11
Bug Reports / PixInsight benchmark
« on: 2014 May 13 12:41:00 »
I had no trouble running the benchmark on my Windows machine but when I try it on my Linux box, I get:

Error: File I/O Error: Unable to open file: No such file or directory: /tmp/pixinsight_benchmark_v1.fit

If I copy the file from the Windows machine to /tmp, everything works fine.  Any ideas?  /tmp has the appropriate permissions.




John

12
General / Linux X11 message
« on: 2014 May 07 09:06:29 »
After I installed the latest release of PixInsight, I noticed that I couldn't get any of the processes to come up unless I turned off X11 compositing.   Running Mint Mate 16.

Now of course I get the warning:

** No running X11 compositing manager has been detected. Some core GUI functionality will be reduced or unavailable.

I've been fighting this issue with Mint for a while now and discovered that if I use the Cinnamon desktop, I don't have the problem (I normally use MATE which I like much better).  Any Mint gurus out there?  Anyone know why Cinnamon would work fine with compositing enabled while MATE doesn't?  BTW, no xorg.conf file exists in any of my installations.

I'm stumped, especially when some of the processes come up fine while others do not.  I get similar results (but not exactly the same!) on my Linux machine as well as on VirtualBox on a Windows 7 machine.  I'm guessing it has something to do with the video card (integrated on the Linux machine), not exactly sure how VirtualBox treats the ATI card in my Windows machine.



John

13
General / screen size issue
« on: 2014 January 08 09:27:52 »
Ran into something I can't quite explain. 

I swapped monitors on my Linux Mint 15 system and now I can't resize the PixInsight window.  The original monitor was 1920x1080 and everything "seemed" to work fine (full-screen and windowed) until I swapped in a monitor with 1600x900 resolution.  Now full-screen is narrower and taller than screen space and when I try to adjust it in windowed mode, I can't reduce window height - but I CAN change window width.  I also notice that going back and forth between windowed and full-screen acts oddly - the full-screen window does not return to full screen - it stays whatever size I left it.  I can grab the left, right and bottom edges of the window but not the top. 

Anybody have any insight in what's happening?  Every other program I use acts normally.


14
Bug Reports / possible linux bug
« on: 2013 August 01 19:15:02 »
I'm fairly new to Linux but I think there might be a bug in PI for linux.  I'm using Linux Mint 15-Mate and in general PixInsight works perfectly if I have X11 compositing disabled (and I get the warning message in the command window).  If I enable compositing, no warning message, but I can't bring up any of the tools.  Am I doing something wrong or is this normal?

15
Bug Reports / Defect map usage
« on: 2013 March 31 14:21:37 »
I've tried using the same procedure to defect correct using the defect map and image container as I did with 1.7.   Latest version 1.8 processes one image, then stops responding and crashes.   Here's what I do:

open an image container, add the files I want to correct, iconize it.
open the defect map image file and the defect correction tool, select the defect image
drag the defect correction triangle over the iconized image container.

I do recall some of the correction options not working right in 1.7 (also crashed) but at least one of the options always worked.  Anybody know what's going on?

Pages: [1] 2