Fix decay baseline so new memories start Active instead of Fading
Changed zero-access usage_factor from 0.5 to 1.0 in calculate_decay_score(). Previously, a freshly stored solution (importance=0.7, weight=1.2) scored 0.42 (Fading); now scores 0.84 (Active) as intended. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
807c6978e5
commit
08b74ec6d6
@ -361,7 +361,7 @@ def calculate_decay_score(
|
||||
decay_score = importance * e^(-lambda * days) * log2(access_count + 1) * type_weight
|
||||
"""
|
||||
time_factor = math.exp(-DECAY_LAMBDA * days_since_access)
|
||||
usage_factor = math.log2(access_count + 1) if access_count > 0 else 0.5
|
||||
usage_factor = math.log2(access_count + 1) if access_count > 0 else 1.0
|
||||
return importance * time_factor * usage_factor * type_weight
|
||||
|
||||
|
||||
|
||||
Loading…
Reference in New Issue
Block a user