For the second form of the syntax we assume that an adjustment has already taken place. We will assume that the collection to be adjusted is the base B, and that the currently fitted collections can be arranged as the collection D. Hence, we assume the scenario that would result if we issued the command
It is also possible to use this second form of the syntax for the SCAN: command when a collection has been prepared for adjustment using either of the following two ways:
in which case there is no current fit, and for the purposes of this section we will assume that D is empty. However, in such scenarios it would be more natural to use the first form of the syntax described above.
The action of the SCAN: command is now to evaluate limited aspects of the partial adjustment of the base B by the base F, having already adjusted by the base D. That is, the potential of the further adjustment by is assessed. The following information is available after such a command has been issued.
This then can be accessed via the [B/D] operator scac as scac analagously to the [B/D] operator ac . For adjusted variances, we could also use the scav operator in that scav is equivalent to, and shorthand for, scac
This then can be accessed via the [B/D] operator scae as scae analagously to the [B/D] operator aex .
As an example, consider the fragment of code given in Figure 9.4. Here, we scan for the effect of adjusting B by D and then some other base F. Assume that the base B contains elements X, Y, and Z. To begin, we switch off the scac control, so that we don't copy the adjusted covariances to a belief store for this and subsequent SCAN: commands. This is followed by the SCAN: command itself, and then various lines of output which show how we access the results of the command.
Figure 9.4: Scanning partial adjustments
Similar information to this (albeit in terms of resolutions) can be obtained by using the arcin operator following an adjustment.