next up previous contents
Next: Additional Capabilities Up: Control parameters Previous: Control parameters   Contents

Implementation issues

The implementation has been made in such a way that the name changes do not break backwards compatibility.

The scheme is the following. A Fortran derived type handles all UV_MAP associated parameters, and SIC variables are pointing directly towards one instance of this derived type, handling all default values. Command UV_MAP converts the default values to actual values. Command UV_STAT SETUP does the same. Both use the same routines.

A second set of instances of the same Fortran derived type is used as target for the old SIC variables, so that the code can check whether the user has been modifying these ones instead of the new ones, and a warning is issued in such cases. Both instances are made identical after each UV_MAP command.

The only exception is WEIGHT_MODE, which has no meaning in the new implementation, where MAP_ROBUST encompasses all possibilities.

The define.map script as been changed to provide an implementation which is independent of the MAPPING version.



Gildas manager 2023-06-01