See this Comm Center message by Dick Berg, and the ones following. Currently the Catalog Maximum Magnitude in AcquireScheduler is fixed at 18. Same problem in AcquireImages for ACP.



The solution is to put a common function into AcquireSupport which returns the catalog maximum. It would determine if ATLAS is in use, then which mag bands are present (down to 20) and return the max mag for which catalog bands are present. No user setting needed, and simply adding another band will extend its coverage. 

 

  
SVN Comment
 
 

  
Author
  
rbdenny
 
 

  
Repository
  
svn+ssh://rbdenny@a2_svn_dc3/home/rbdenny/svn/astro/scheduler
 
 

  
SVN Revision
  
911
 
 

  
Affected files
  
/trunk/AcquireScheduler.vbs (Modified)

 
 

  
Check-in comment
  
Log CatMax since it is a setting now
GEM:1874

 

 

  
SVN Comment
 
 

  
Author
  
rbdenny
 
 

  
Repository
  
svn+ssh://rbdenny@a2_svn_dc3/home/rbdenny/svn/astro/scheduler
 
 

  
SVN Revision
  
910
 
 

  
Affected files
  
/trunk/AcquireScheduler.vbs (Modified)
/trunk/Help/RelNotes.htm (Modified)

 
 

  
Check-in comment
  
Get PinPoint solve parameters from ACP Prefs.PointingUpdates properties. This allows new ACP CatalogMaximumMagnitude to be used. 
GEM:1874

 

Decided to put a MaxMag setting in ACP since we also have giant cameras coming into use and need to give user control to avoid maxing out PinPoint. This is now exposed as an ACP API property Prefs.PointingUpdates.CatalogMaximumMagnitude. I also now get the SIgma and MinimumBrightness from the API. These are fixed at 3 and 0 respectively.