After switching readout mode to integer it won't go back to real?

[Nocturnal]

Hi,

I switched readout mode to 0-64k and then back to real 0-1. Readout values change to the integer values fine but then remain at 0 after switching to real.

[georg.viehoever]

I also have this problem.
Georg

[Nocturnal]

It seems Juan has gone undercover somewhere in wine country.

[Niall Saunders]

Hi Sander,

I am not seeing this - and I am also using Vista64.

Maybe I am not fully understanding your scenario (same with you, Georg)

When I click the little blue triangle on the bottom bar of the PI window, I have the following options:-


The setup I am currently using, for each of these options, is as follows:-


Readout Data

Readout Mode

Probe Size

Preview Size

Preview Zoom

And, this is what I use if I want to see ADU data in terms of a 16-bit Unsigned Integer range (0, 65535)


And I use this for my PixInsight 'internal' (0.0, 1.0) range


I can change happily, back and forth, between these two configurations without any 'bug' being evident, either on the display line at the foot of the PI main window, or on the 'readout probe' panel when actually inspecting an image, as shown in the two examples below:-
  Real Mode
  Integer Mode

Have I missed the point of your bug reports?

[Nocturnal]

You're getting close. Now change back to range 0-1 and see if you're getting fractional numbers or just 0 with the occasional 1 if the data is maxed out.

[Niall Saunders]

Hi Sander,

Yes - that WAS what I noticed, but I simply took that to represent a REAL display with 'zero' decimal places - in the same way as I have interpreted each of the other 'real' options to represent options of between 1 and 15 decimal places.

I agree, this is perhaps not that intuitive - at first - but, isn't that the way of PI 

What I cannot remember is how 'it used to be' and 'when it changed'. I have a feeleing that this changed well before v1.6.x - but I may be wrong

So, 'bug' or 'feature'

[Nocturnal]

Hmm, I'll have to play with this a bit more. I couldn't get it to do the right thing anymore but that's probably because I don't understand the options. Of course there's no help for them so I suppose we should just figure it out ourselves.

[Niall Saunders]

I couldn't get it to do the right thing anymore

You couldn't get it to do the right thing or you couldn't get it to do the wrong thing any more?

As I said, I now interpret the 'Real' options to allow me to choose the number of decimal places for displaying my ADU values - all in the range [0.0, 1.0] of course. And the choices are from 1e⁰ through to 1e^-15, or no decimal places through to 15 decimal places - which does actually make sense (apart from the rather un-necessary first entry).

Perhaps it would be better actually just stating "number of decimal places" in the options list - it would avoid confusion

[Juan Conejero]

Hi Niall,

Perhaps it would be better actually just stating "number of decimal places" in the options list

Actually, it is more related to the precision of the decimal representation (not to be confused with accuracy; the accuracy is always the same in this case).

Following your suggestion, I'll change this menu to:

0 decimal places
1
2
...
15

[Juan Conejero]

It seems Juan has gone undercover somewhere in wine country.

Yeah, I always do that while I'm writing a documentation compiler 

[Nocturnal]

Thanks Juan, that will make the radout options clearer. I think what happened was I changed one option and I had to change two to get back to where I started.