
Hi David. PHD2 doesn’t worry about what the star field looks like in the image display and it’s not really useful to try to compare screen-shots. PHD2 works on the raw, un-stretched frames obtained from the guide camera. If you really want to see what PHD2 is working with, you should capture a typical frame (File/Save) and then examine that data in a suitable imaging app – one that can compute areal statistics, stretching according to your wishes, etc. Obviously, the data obtained with different apps using the same camera must also be using the same camera driver with the same settings, especially things like 8-bit vs 16-bit and gain. You should also disable dark-frame or bad-pix map corrections to make comparisons. But in such experiments, you should always be comparing raw data frames.
Bruce
--
You received this message because you are subscribed to the Google Groups
"Open PHD Guiding" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to open-phd-guidi...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/2479a910-b819-4fe0-85ab-e6e649600894n%40googlegroups.com.
You should be able to solve the first problem by doing auto-select, that’s what we recommend. It doesn’t matter what you see on the screen, the selection is based on the stellar properties that are important for guiding. And you must do that if you decide to start using multi-star guiding.
Good luck,
To view this discussion on the web visit https://groups.google.com/d/msgid/open-phd-guiding/418b8ae4-78b4-4364-b586-1ec60d7eb343n%40googlegroups.com.