|
From: James R. V. Z. <jr...@co...> - 2007-07-27 02:17:44
|
Ethan Merritt wrote:
> But that's not an issue of failing to store input data; it's an
> issue of whether you apply axis scaling upon input or wait until
> later.
Currently the data are scaled and replaced. That means if the user
reverts to linear scaling, the data has to be unscaled. Any
nonpositive data points will have been lost. It also means we need an
"unscale" function. The probability scaling in my patch uses the same
kind of implementation.
I would like to implement general scaling by a user-defined function,
and would rather not force the user to supply its inverse too. We
could do that with "just in time scaling" - i.e. store the data as
read in from the file, and apply scaling immediately before
calculating screen positions. If we agree that's the way to go, then
it makes sense to make that change before applying [a version of] my
axis scaling patch.
- Jim Van Zandt
|