ATSV (since version 10.0.8) supports two additional types of configurators, added at SEI's request. However, those additional configurators only work for choicepoints with floating point values. Since much of the value in GTSE comes from specifying component selections that modify the validity of other component selections, we require string values for these additional configurator types.
To get around this limitation, GTSE will cache the strings to floating point values right before the ATSV configuration file is generated, and then uncache the values when OSATE receives the request. It's a sort of hacky workaround and has the undesirable side effect of making the ATSV graphs harder to read, as some component names are replaced with floating point numbers. So, if ATSV supports string comparisons for these more advanced configurators in the future, methods and fields tagged with this interface should be removed.
ATSV (since version 10.0.8) supports two additional types of configurators, added at SEI's request. However, those additional configurators only work for choicepoints with floating point values. Since much of the value in GTSE comes from specifying component selections that modify the validity of other component selections, we require string values for these additional configurator types.
To get around this limitation, GTSE will cache the strings to floating point values right before the ATSV configuration file is generated, and then uncache the values when OSATE receives the request. It's a sort of hacky workaround and has the undesirable side effect of making the ATSV graphs harder to read, as some component names are replaced with floating point numbers. So, if ATSV supports string comparisons for these more advanced configurators in the future, methods and fields tagged with this interface should be removed.