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

Pages: [1]
Bug Reports / Re: Error message from Blink in v1.8.8-3
« on: 2019 December 21 10:55:21 »
I am getting the same error, on a ryzen machine with Nvidia graphics.

I've had blink crash twice, and completely shut down the application.   And now Ive gotten a complete lockup of the application while doing image integration.  And had to do a hard kill on the application because it would not let me do anything.   

Same error message as 1Degree in pixinsight:
Exception code 0XC00000005
Faulting offset 0X000...001C3D1c3
Faulting process:  0XB74
Faulting  module:  Qt5WebengineCore.dll

Bug Reports / Swap file insufficient space error
« on: 2019 April 20 07:06:34 »
I've received errors associated with swap space that cause the program to not allow any further work.   This is the second time I've gotten the error.  After searching on the issue I've seen a couple of things that are probably going on.    1) that my C:/temp should be renamed to C:/ .   Although thought this might have been fixed long ago.  2)  This C drive has ~200G of space of NVMe drive available but likely only using 8Gb since I'm also using a bunch of folders in 8 GB of ram disk, giving me a total of only 16G.   It's the ramdisk that seems to be getting the error and I've read in some posts that it's the smallest swap space which defines the limit of all other spaces.   I have 32G of RAM and allocating 8G to the ramdisk.    Since I have super-fast NVMe, maybe it doesn't make sense to use the ramdisk and just stick with the C swap space.

That said, I'm still a bit surprised that the program faults rather than managing the space.     Maybe I'm doing something else wrong.    Some screen shots of the errors and my swap configuration.   This is a 64b windows 10 system.


General / Re: Inconsistent zoom buttons
« on: 2019 March 26 10:13:34 »
Hi Terri,

Here is a brief description of the three options:

- Zoom to fit. Apply the maximum possible zoom factor without making the image larger than the current maximization space. The maximization space is the rectangular region of the workspace at the left side of the maximization limit. The maximization limit is the vertical orange line that limits maximized windows.

- Zoom to optimal fit. Like zoom to fit, but instead of maximizing zoom factor, apply an 'optimal' zoom factor to allow multiple windows share the maximization space less unobtrusively.

- Fit view. Adjust the window to the current visible region of the image.

There is no inconsistency. Each option finds its practical use depending on image and monitor dimensions.

Thanks Juan,
I had given up getting a response and have been away for a week or so.  I did get some feedback from Adam Block via e-mail which helped, as well as some experimentation on my own.   I found that operating in full screen desktop mode (normally I wasn't using it) with my taskbar minimized gave me the operation I expected based on your description.  Unless I run full screen (on either the macbook or PC) the window sizes aren't really consistent with what I thought they should do.  But in full screen they actually operate as expected.  And then only afterwards I found your documentation on minimum system requirements published in February of this year, which stated some of the same suggestions for small screens (like my laptops and even though my laptop says 2880xnnn it's really only 1440).  In any case, I found a way make the operation consistent and good for me.   Thank you for responding.      As a long term photoshop user, I find many things to like about pixisight, but the learning curve is very steep.   I've been using Adam Blocks video tutorials which are very instructive and helpful.

I am looking at various system requirements to spec out a new desktop system (my current is not as fast as my laptops and only used as an archive storage server).


General / Re: Inconsistent zoom buttons
« on: 2019 March 16 06:15:37 »
Just make it easy on yourself:

Ctrl + T        Zoom to optimal fit

Ctrl + 0        Zoom to fit
Not a very helpful response....   

Does someone else see inconsistent operation?   I have tried these functions on both a PC and Macbook laptop, and I get inconsistent operation of fit view on both of these computers... and I'll say zoom to fit is a bit more useful on my macbook (gives a view a good bit larger and differentiated window size from zoom to optimal fit) but the fit view operation still works inconsistently (sometimes it works, sometimes it does nothing).   Is there a reason that I'm missing?

General / Inconsistent zoom buttons
« on: 2019 March 15 08:51:58 »
Maybe I'm doing something wrong, or don't have something setup correctly.  But I'm finding it a bit maddening to have the zoom buttons operate differently at different times.
What is zoom to fit, zoom to optimal fit, and fit view supposed to do?    I get inconsistent operation. 

My experience:
Zoom to optimal fit - gives  me most consistent operation, kind of a smallish window, not really useful for any detail but maybe good for fitting a whole bunch of windows on my screen.
Zoom to fit - I get inconsistent operation.  Sometimes I get a full window sized view of an image, and other times I get something that only is slightly larger than the zoom to optimal fit.   Why?
Fit view - Probably the most inconsistent operation, sometimes I get nothing (it doesn't do a thing) and other times it makes the image very large to where I have scroll bars on the image.   

It would be really useful to have a zoom button that maximizes the image to the available real estate (no scroll bars).    Am I doing something wrong or have a setting wrong?


Bug Reports / Re: Image integration showing old results
« on: 2019 January 03 14:35:43 »
Thank you for any understanding.

So you know a little about our business.   :)  I have to admit in recent history, I've been more management than execution and design of circuits and/or more often chips.    So Design Compiler is the tool of choice for most of our customers, although our own shop has used Magma extensively.
Last i had to actually touch tools, was when I was managing development of place and route software..   


Bug Reports / Re: Image integration showing old results
« on: 2019 January 03 11:00:27 »
Guys, I've gotten off on the wrong foot obviously, or two wrong feet.  My apologies to all.     I've obviously become a bit frustrated and wanted to share that frustration a bit but not take it out on any particular person, and maybe i've inadvertently done that, and it wasn't my intention.   Again, my apologies.   I appreciate the community support greatly, even though in my heart of hearts I feel if someone/company sells a product, they should be supporting it.  But maybe that would mean a license is $500 instead of $100.   

The issue I brought up, the best that I can tell, was real and it was solved as I wrote.     

I am not a newbie at image processing, or computers (I have been designing, and then managing the design of semiconductors for almost 40 years) nor am I an expert in image processing and was an early adopter of digital (canon d30).  I've been able to do things I'm pleased with in nebulosity and photoshop, using imperfect and limited data from a terrible environment for astrophotography (northeastern united states).    But I am a new comer to pixinsight.  Although I have invested time in both free and paid for tutorials I don't feel I am making progress consistent with my time investments.   Hiccups like the one I mentioned are short term irritations, but the general usage of some items has been a tough experience (for me, anything to do with background neutralization).   I've never spent so much time fiddling with measurements points to get results that are for the most part no better than what I started with.  In any case, I will post some problems that I can't solve and see what I can learn from the experts.   

So sorry to those I may have offended due to my frustration coming through.

Bug Reports / Re: Image integration showing old results
« on: 2019 January 02 13:35:21 »
You are very condescending and not very aligned on how to accomplish customer service, if indeed you are someone from the company.   There were no gradients in my new data, and I'm not a newbie  in digital imaging.    As I said,  running the program with new data, created the same old result. I did this several times.  What I had to do to fix it, with the same old data, is not recreate or change my data, but to stop using my saved iconized process, and restart the process from scratch (just opening a new process window).    And without any more issues, it created the correct result and did it several times in a row with all my different color files.   I have no idea what's going on and honestly only want things to work.    I've experienced this kind of behavior in at least one other program as well, but don't recall the one and I'm not likely to take my limited free time to put in constant bug reports.. this stuff should be tested better.

I'm not sure what to provide you other than ALL Of the data that went into the program, which is Gigabytes.. just showing the result, which I did save, would be meaningless.     

Cathartic ,maybe.. but I spent hours and hours on this stuff is disappointing given I had high expectations.     Especially with the people saying this is a real professional program for professionals.. I guess I expected more.    My take is you've created a monster that may be too unwieldy to manage.     I have a high tolerence, but it's getting to it's limit.

Bug Reports / Image integration showing old results
« on: 2019 January 01 20:27:38 »
Multiple issues/bugs.

My first issue is with the integration process on a new set of data based on fixed flats to remove an un-fixable gradient (un-fixable in pixinsight DBE) in any reasonable amount of time or effort.    So after reprocessing all of my data, and running integration, I find the same integration result file based on old data..  It took the normal amount of time, so implied to me that it was running correctly.  I thought I must have picked up the wrong (old) files or something.  I checked all the files I used and even ran it twice.. same bad result file comes out with bad gradient, with input files of all correct gradients (or rather no gradient).   So how to heck do you fix this?    This is crazy if some internal files, or file pointers, stick around for days inside of your project file (I save no data files in my project file, only iconized processes) and show up as results to new input data.    I still have no idea how this is fixed?  I keep on getting the same result based on data from a few days ago, even though inputting different data!! 
Issue two, while pre-processing and using subframe selector, I couldn't get the graph to show... it was just a blank panel.  Nothing I did would fix it except logging out, and then not using my prior iconized process set up at all.  So I  had to start from scratch.     After getting it to work correctly I also noticed scoring on 2 items I would have thought only effected by stars, which didn't change in my subframes, have changed pretty significantly.    Would a gradient change in flats calibrating my lights effect eccentricity and Fwhm?   So multiple issues here (graph in subframe selector blank and changing results).

After playing with pixinsight, or struggling I should say, for a month or so while taking advantage of excellent tutorials (A. Block and Light Vortex), I'm beginning to feel like this is someone's partially finished science project and not a software package ready for primetime.    Documentation seems sparse and a bit cryptic (as is the interface in most cases).   I'm an engineer who likes astronomy and to take photos.  Software is a necessary evil, not something I want to be immersed in, nor do I want to be an expert in the science behind pixel processing.   Many I know feel the same.    I have been a long time user of photoshop and other software packages that I've used for my images but thought I'd give this a try since I'm going into mono imaging.    I don't know how long I'll stick it out with your software.    It's possibly too much of a chore to use.

General / Re: Crashing
« on: 2018 November 30 11:15:18 »
Thanks Rob, I'll give memtest a try.  This is a laptop, so no over clocking or accelerating in any form.


you can run memtest86 to find out if you have a bad memory, and prime95 to see if the CPU for some reason is making mistakes (this is usually only likely when you have overclocked the CPU or perhaps if your cooling is suspect.)


General / Re: asi1600mm Bright Star Reflections
« on: 2018 November 30 11:14:00 »
Hi Lightpath,
I know this is old and there are no responses, but I've been seeing what appear to be the same kind of spikes on my ASI1600 images.   While they're fainter (maybe less exposure and fainter stars) they are there.   On my images, it almost looks like spider spikes, while I'm using a refractor!   I can see that yours are much more extensive and beyond spider-spikes.   Really odd.   So it's either the camera or some odd artifact of having an OAG in the field. Are you using an OAG?  Do you have any further insight from other sources?


Hey all, I'm curious if anyone has any idea how to process out these reflections from Alnitak...  I'm using an ASI1600mm pro cool and an 80mm refractor with a 300s exposure.

Maybe a synthetic flat?

Thanks very much for any thoughts about how to correct this, I have a fair bit of data with this problem.

General / Re: Crashing
« on: 2018 November 29 13:40:04 »
Thank you Adam,
You know I wondered about this but not entirely clear on how to debug.  I've put 16G into this machine recently, a windows machine (which I'm not entirely fond of), but it's also my capture machine so I thought I might be able to keep all astro-work on one machine.  I guess I could process on my MacBook and just move the files around.  The MacBook, for the most part, will run forever without a reboot it seems.

Since no one else is seeing this, which I noticed when I looked around, the system is suspect.   It's just funny that it happens mostly while idle and not when I'm using it or running a process.   


Hi Terri,

I can't offer any suggestions on the software side. It would be pretty unusual for a software to cause that kind of crash. I defer to others.
If you cannot find a software reason for what is going on...
You description does strike a chord with me. I recently struggled with some computer issues like this, and it turns it the issue was bad memory. PI and image
processing programs use quite of bit it... so you might not see issues until that part of RAM is active. Bad memory is so insidious.
Anyway, this might not be the issue- but certainly is an issue to consider in the panoply of possible problems.

General / Crashing
« on: 2018 November 29 05:52:19 »
I'm not sure if this is the right place or not, my first post, so please move if not.

I am experiencing instability and crashing of the latest version of the software.    I've had it lock up on me a couple of times recently, to where nothing other than cntl-alt-delete will bring my system back, and several times now (doesn't seem a fluke) it's caused a system restart either automatically or forced by me.   I'm not seeing this anywhere else right now.

On the crashing I was running DBE and could not get it to recognize keystrokes.. system was chirping at keystrokes.   I tried to see if any dialog was open but I couldn't do anything, couldn't move or minimize anything.    I couldn't get other programs to the front, basically the system was locked up.   

And now several times over the last 10 days, it's locked up while coming back from hibernation or I find a reset system (I come to a system which is clean and nothing running and loosing some work on a project).    I went into event viewer but really don't see what might be causing the issue.   For the most part I only have a browser open along with PixInsight.

Debug help?


Pages: [1]