My favorites | Sign in
Logo
                
New issue | Search
for
| Advanced search | Search tips
Issue 11: Bias random selection to newly added tracks
1 person starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  ewxrjk
Closed:  May 2008
Type-Enhancement
Priority-Medium


Sign in to add a comment
 
Reported by ewxrjk, Mar 05, 2008
Newly added tracks should (optionally) have a greater weight (in the sense
described in  issue 10 ) than others.  How much they are upweighted and how
long for should be configuration options.
Comment 1 by ewxrjk, Apr 26, 2008
revno: 633
committer: Richard Kettlewell <rjk@greenend.org.uk>
branch nick: disorder.dev
timestamp: Sat 2008-04-26 14:51:46 +0100
message:
  Log the time at which newly noticed tracks are added to the database.
  This will allow disorder-choose to add a bias in favor of those tracks
  (cf defect 11).

Status: Started
Comment 2 by ewxrjk, May 17, 2008
disorder.dev's disorder-choose implements biasing, though not yet in favor of
recently added tracks.  MdW was talking about changing it to be lighter on
/dev/urandom, though  it's quick enough to go if further changes don't appear.
Comment 3 by ewxrjk, May 18, 2008
revno: 658
committer: Richard Kettlewell <rjk@greenend.org.uk>
branch nick: disorder.dev
timestamp: Sun 2008-05-18 23:44:36 +0100
message:
  Bias up recently added tracks.  See new_bias and new_bias_age in
  disorder_config(5) for details.  Fixes defect #11.

Status: Fixed
Sign in to add a comment

Hosted by Google Code