Previously:
SpProg
SpMSB
SpObs Filter J
SpSurvey n tiles (4n fields AKA pointings AKA "Survey Targets")
SpObs Filter H
SpSurvey n tiles (4n fields AKA pointings AKA "Survey Targets")
SpObs Filter K
SpSurvey n tiles (4n fields AKA pointings AKA "Survey Targets")
Now:
SpProg
SpMSB
SpSurvey n tiles (4n fields AKA pointings AKA "Survey Targets")
SpObs Filter J
SpObs Filter H
SpObs Filter K
The previous version can still be used by adding the line
Either
Or
Load the Science Program XML file into a text editor and search/replace the old filter names. The filter names that have changed are
Filter Names Old New blank Blank J98 J H98 H K98 K H2_1-0_S1 1-0S1 Br gamma BGamma
Filters Y and Z are unchanged.
(You can use GAIA's Data-Servers Catalog searches to see which catalog uses which fields. The fields appear in the header line of the catalog query result table in GAIA.)
Once the SDT had decided which magnitude field to use it tried to retrieve this field for each object in the query result returned from the catalog. The problem with this approach was that some catalogs (e.g. USNO B1.0 Catalog at CDS) provide several magnitude fields but not all of them are set to a value for all the objects in the catalog. (Again you can check this in GAIA.) That is why the SDT has to look at more than one magnitude field until it finds one which contains a value. This means that the SDT might end up comparing different kinds of magnitudes (the B1 magnitude of one object with the R1 magnitude of another object, say) when selecting guide stars. This does not seem to be ideal. On the other hand it only seems to be an issue with some catalogs such as USNO B1.0 Catalog at CDS. Normally each magnitude field defined in the result table is actually set for each object. So the magnitude fields are now selected on an object by object basis in the following order of preferrence:
As mentioned above this gets rid of the follwing bug: When using USNO B1.0 Catalog at CDS (maybe other catalogs as well) lines would sometimes be drawn accross the autoguider CCD display. This problem was probably caused by the failure to retrieve a magnitude from the catalog for some objects. The calculation of the radius of the circle representing such objects on the autoguider CCD display was then based on a zero magnitude which let to circles with an infinite radius. The problem should now be fixed.