DanielVanNoord / open-phd-guiding

Automatically exported from code.google.com/p/open-phd-guiding
0 stars 0 forks source link

Enhancement request: show reference circle on target display #329

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
request to display units (graph, target, stats, etc.) as imaging camera pixels

currently we have options for guide camera pixels or arc-seconds; we could add 
the option for imaging camera pixels.

we would need to know either: imaging scale (arc-sec per pixel), or imaging 
camera pixel size and focal length

Original issue reported on code.google.com by andy.gal...@gmail.com on 29 Aug 2014 at 3:56

GoogleCodeExporter commented 9 years ago
more comments in this thread:
 https://groups.google.com/forum/?fromgroups=#!topic/open-phd-guiding/jJ96nEzUwVw

Original comment by andy.gal...@gmail.com on 30 Aug 2014 at 6:28

GoogleCodeExporter commented 9 years ago
Later discussion showed we can satisfy the original request without adding more 
bulk to the setup dialog.  Here's the summary: 

On Friday, August 29, 2014 8:05:11 PM UTC-7, Bruce Waddington wrote:
Ok, permit me to be a little contrarian now.  So if we add another pair of 
parameters, I wonder if we won't just add to the confusion for not much 
gain........  As a simpler alternative, what if we just added a capability in 
the "target" window to show a user-defined circle that would be retained as 
part of the profile.  So you could do the math one time in your head, as you do 
now, specify a circle that corresponds to your one-pixel-value, and you'd be 
done.  I suppose the same could be done on the tracking graph by just adding 
lines at user-defined ordinal "boundaries." 

Response from original requester:
... what you suggest would serve just as well, perhaps better, since the user 
could make that circle however large or small they wish which might allow the 
setup to conform to their feelings and theories as to what the acceptable 
guiding "area" should be.....

Original comment by bw_ms...@earthlink.net on 31 Aug 2014 at 12:44

GoogleCodeExporter commented 9 years ago
updated summary per comment above

Original comment by andy.gal...@gmail.com on 3 Oct 2014 at 5:09

GoogleCodeExporter commented 9 years ago
This issue was closed by revision r1152.

Original comment by andy.gal...@gmail.com on 3 Oct 2014 at 6:26