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

Pages: [1]
1
Bug Reports / Re: pix 1.8.7 Control Page Down not working?
« on: 2019 October 02 18:22:49 »
Yay! Thanks for getting to it so quickly Juan! Really looking forward to trying out the other new functionality in PI 1.8.7: a lot of interesting stuff in the release notes.

Thanks -- Joel.

2
Bug Reports / Re: pix 1.8.7 Control Page Down not working?
« on: 2019 October 01 20:56:24 »
It is not just you. :-(   Not functioning on Windows 10.

3
Bug Reports / Re: Missing PI Icon
« on: 2017 September 29 20:58:48 »
Have observed this as well: Windows 10, 64-bit. Interestingly, the correct icon is used when PixInsight is first opened. Not sure at what point it changes. This is also new behavior with 1.8.5 (which, of course, continues to deliver awesome processing ... :-).

4
Bug Reports / Window titles
« on: 2017 September 25 21:13:56 »
This is a minor issue but also the kind of thing that drives me batty.  :-)

PixInsight 1.8.5 (on Windows 10 64-bit if it's relevant) displays a not-very-sensical window title. See attached. The main window title lists the names of calibrated lights and tentative integrations ... none of which are open in the application any longer.

What I'd strongly prefer (and which I believe previous versions of PixInsight did normally) was for the main window title to include only the name of the currently selected image(s) ... certainly not of arbitrary images that were once selected but which are now not even open.

Again, not a big deal, but it does make it just a little harder to keep track of what is selected and active, and what isn't.

Thanks -- Joel.

5
General / Re: Dealing with NaNs in fits files
« on: 2017 February 28 18:23:31 »
Hi - Did you work out a solution for this? I've started working on some WFC3 data (for NGC 3368) and have been looking for a better solution than clone-stamping to address the seam between the sensors. It is so regular that it seems like some PixelMath magic could address it ... but haven't quite worked out what that is.

Thanks for any insights -- Joel.

Pages: [1]