Script score impact. again
|Opened on:||Tuesday, August 31, 2010 - 13:15|
|Last modified:||Saturday, July 27, 2013 - 03:29|
still want to remind that the recipe score impact can give strange values, if a script has been terminated, and that it shows score changes even for scripts which don't do anything to the puzzle structure at all.
This is confusing for those people, who want to try a new recipe.
For impact, I suggest fetching recent best score value before script start (As recent best can be reseted via script) and compare this value with this at script end (including real script end or script termination).
Of course, this wouldn't give any negative values anymore, but the average calculation will drop the impact value to zero, if the scripts don't do anything good for the whole time.
A step further would be including script running length (undo point count, number of tool uses) as score weighting,
so short script run times won't change impact value much, long times will change it much.
You just have to store number of operations, too.
If a script has done 70 operations, and made 50 points score difference (recent best and end minus recent best at start),
Then it is run again with 20 operations making 100 points, the average value is:
thanks for reading,