|
|
ccdciel histogram scale.png (10,084 bytes) |
|
|
Yes, the histogram values are for the internal display image where datamin-datamax is stretched to 0-65535. This look useless at first, but this greatly simplify the image display when the fits file is not 16bit integer, for example a file saved by Pixinsight as floating point ranging from 0 to 1. But I agree this two box must show the real value, as this is done at the other place a pixel value is show. This is the FimageMin+value/FimageC you can see at various place in the source code. The only difficulty is to use a floating point input box when the fits file not use integer values. |
|
|
For ASTAP, to read Pixel Insight/ APP floating point the range is changed from 0..1 to 0..65535 during loading. But my program should be more universal. Anyhow it would nice if it could work correctly for native CCDciel files. My first idea would be to correct the Tupdown values with a datamax/65535 factor. It is not so important but it would be helpful if you cursor measured pixel values match with the histogram range. P.s an other improvement could be if you could measure the histogram with the mouse using the Tonmousemove event. I did it for ASTAP. |
|
|
Hello Han, I do the change to show real values for integer and floating point files, also show the value in the status bar when moving the limit with the mouse. https://github.com/pchev/ccdciel/commit/3f31b6061aa8b7de0e4481f0f9b11a133235e652 And this change to prevent to set min > max, even if this is already handled in the fits routines. https://github.com/pchev/ccdciel/commit/39344fd258233e60d31d5bf10ccc75afbbe4ec65 I also add your photometry functions. see https://www.ap-i.net/mantis/view.php?id=2181#c5993 |
|
|
The change is now include in new version 0.9.61. |
- Anonymous
