| Comments |
| 8/3/2012 11:20:23 AM |
Bob Denny |
Declaring it ready for beta. |
| 6/29/2012 9:43:35 PM |
Bob Denny |
|
| 6/29/2012 5:05:54 AM |
Bob Denny |
|
| 6/28/2012 9:01:03 PM |
Bob Denny |
|
| 6/28/2012 8:58:32 PM |
Bob Denny |
|
| 6/28/2012 5:24:21 PM |
Bob Denny |
Need way to force per-filter autofocus even when FilterInfo is present... in case they want to use the variable star mags but not focus offsets. Will add a new property ACP.Util.Prefs.AutoFocus.ForcePerFilterFocus. |
| 6/28/2012 10:47:44 AM |
Bob Denny |
Wow!! There are major errors in the "visual" mags calculated from the catalogs for bright stars. The CatMax/Min use visual, so I was getting too faint stars "Mag" even when the CatMax/Min were properly ranged. This is a PinPoint problem. I ended up modifying AcquireSupport.FindBrightStar() to filter on Star.Magnitude (which drives off the ColorBand, defaulting to Red), then just set the PinPoint CatMax/Min range from 11 to 0 respectively.
At this point it also uses optional min/max mags in FilterInfo. Progress! |
| 6/26/2012 4:44:16 PM |
Bob Denny |
Adam Block has it the other way around... the focus stars can be too bright on the 32 inch.. Another point for adding a mag range to the FilterInfo file instead of the -NB hack. |
| 4/6/2012 4:26:40 PM |
Bob Denny |
I suggested: What would you think of asking people to name their narrowband filters in MaxIm xxx-NB or something? Like HAlpha-NB. Then I would just shift gears to stars with mag 3-6 and the larger search range needed. I could strip off the "-NB" for cosmetic purposes within ACP and keep a separate narrowband flag list. I'd strip them for the web forms too. |
| 4/6/2012 4:17:06 PM |
Bob Denny |
Brewington suggests a mag range be assigned to each filter as needed. |
| 1/17/2012 11:42:58 AM |
Bob Denny |
Rather than what I previously outlined, maybe make the AF algorithm smarter, and allow FindBrightStar to be called with mag range. There may be some info that can be read back from FMax to tell whether the star is too weak. Or maybe FMax can be told to use longer exposure, or automatically adapt. There are a lot of things that might work to automate this. Maybe the mag range could simply be expanded and let FMax adjust?
I'm going to take this old ticket and work on it. It could result in an improvement to the AF process in general. |
| 11/20/2010 5:15:49 PM |
Bob Denny |
Not this time. To do this right:
- FilterInfo.txt will need to change (added param)
- Documentation of FilterInfo changes
- AcquireSupport.FindBrightStar changes
- AcquireSupport.Autofocus changes (exposure interval guess)
- The FocusOffsets.vbs script changes, and ideally would ask the user for each filter in his list whether he considers it to be "narrowband". Otherwise the user will have to edit FilterInfo just for this feature, and that's error-prone and user unfriendly.
- An all-sky test for mag 5 stars within the 5 degree search are will need to be done. I did this for mag 6 and that's how I got the 5 degree number.
|
| 11/20/2010 7:01:09 AM |
Bob Denny |
Add optional "NB" flag to FilterIInfo, read into AcquireSupport, use in AutoFocus.
WARNING: Will need to greatly expand search area to get stars with mag < 6 |