Tweening "y" and connecting movement to score

Question

Still trying to get a bar/column to move up and down based on a positive or negative total score value. Uisng "scaleY" doesn't scale proportionately for these values. The "absolute "0" point in this scaling is the mean value for the score. I thought that if a score result was > mean, then the score could be successfully adjusted by score - mean, while if score < mean, then the adjustment would be mean - score. This seemed to work for some of my testing values, but not all cases.
So, instead of scaleY, maybe moving the bar/column up or down depending on its relationship to the mean (used to establish the 0 point).
So, I would need to move the bar based on score. As an example, if the mean is 1.95 and the range is - 0.15 to + 4.05, the bar/column (registration set to center) is 75 w and 250 h and placed stage horizontal center (384 for a 768 height screen), what would a tween script look like? Needs to factor in the score to stop the movement.
var tween1:Tween = new Tween(bar1_mc, "y", None.easeOut, 384, 634, 30, true); //starting point, then needs adjustment based on score value
The scaleY with a paramF provided by kglad seemed a better and far easier solution, but these score values don't seem to fit that model. Even with the scale set as -mean, -1, +mean, +1. I tried Math.abs to avoid problems with multiplying negative numbers by negative numbers to get "accidental" positives that threw off the tween direction needed. But no joy. Sometimes the bar travelled in the correct direction based on the score. Sometimes it did not and was unrepresentative of what is was needed to symbolize ( a big up movement for a score that should have produced a small downward movement, etc.)
So maybe, tweening by using "y" instead of "scaleY"?

Answer 1

So, this works if my test score (hard-coded for testing) is +2.18.
If I change my test score and hard-code +1.18 instead, the bar does not show at all (the trace shows a small negative result for the calculation which can not display because the range is set above it). 1.18 is below 1.95, so a correct display would show the bar going slightly down for a 1.18 score.
If I change the range to paramF (-0.15,0,4.05,250) since the correct range actually is -0.15 to 4.05, then 2.18 goes up more, but 1.18 now goes up when it should go down.
The trace is showing the correct hard-coded scores that I am using.
So, back to the design. I don't think that a scaleY tween can accomplish this display with these scores. Maybe a "y" instead? Move the 250 px (height) bar up from a stage center point, if > 1.95 and another bar from a stage center point down, if < 1.95?
Very challenging score display.  (Beginning to think that no moving parts display, just the score numbers in a text box, may be all that can be done?)