I would advise at least placing the domain specific algorithms in a
separate artifact and keep the base API in a main artifact. Also a
smaller API will be easier to release quickly.
Emmanuel Bourg
Le 28/03/2012 23:04, Simone Tripodi a écrit :
Salut Manu,
The ELO ranking algorithm - like all
Salut Manu,
The ELO ranking algorithm - like all algorithms in [graph] - is
implemented in a generic way that it can be used to rate chess players
as well as chicks on facemash, it is not related to any specific
domain.
The main purpose is rating generic entities that faced in one or more matches.
It's really nice to see that [graph] is mature enough to support the
implementation of the ELO system, however I wonder if it should be
shipped along with [graph]. IMHO Commons Graph should focus on providing
the building blocks for working with graphs instead of implementing
domain specific al
Hi all guys,
we have an ELO implementation now which I would really like some of us
could review and provide feedbacks/contributions/...
The concept is that *directed* Graphs represents tournaments where the
generic players (Vertices) take part, Edges are WIN/DRAW enums,
players are ranked in a u
