You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just noticed that the applied flood weighting appears to be applied to Locations twice?
There appears to be an implementation in UpdateLocationScore() in scoring.py, which is used to calculate the base end point score used in getEndPointScore() in moving.py. However, after that base end point score is retrieved I see very similar code being applied to multiply that score with the same factors once more in getEndPointScore().
Could you perhaps double check this? I would recommend removing the implementation in getEndPointScore if it is a proper duplication....
(this might also explain why the DFlee test has been failing occasionally (see #107).
The text was updated successfully, but these errors were encountered:
Hi both,
I just noticed that the applied flood weighting appears to be applied to Locations twice?
There appears to be an implementation in
UpdateLocationScore()
inscoring.py
, which is used to calculate the base end point score used ingetEndPointScore()
inmoving.py
. However, after that base end point score is retrieved I see very similar code being applied to multiply that score with the same factors once more ingetEndPointScore()
.Could you perhaps double check this? I would recommend removing the implementation in
getEndPointScore
if it is a proper duplication....(this might also explain why the DFlee test has been failing occasionally (see #107).
The text was updated successfully, but these errors were encountered: