Talk:RumbleStats

Glicko-2 scaling

Oops, I forgot that the RoboRumble Query API is not yet scaling the Glicko-2 rating as it does for the web interface, so right now this isn't going to post the right Glicko-2. You'll either have to go back and edit that in manually, or wait until Darkcanuck gets that fixed. --Voidious 02:43, 19 August 2009 (UTC)

(edit conflict) Cool! I'll send you another API key for this app -- that way I can track it's usage separately from your twitter app. I'm assuming it uses the same query strategy?

I thought I fixed the glicko-2 scaling when you brought it up? --Darkcanuck 02:46, 19 August 2009 (UTC)

Hmmm, fixed the 'rankings' query but not the 'participants' -- should be fixed now! --Darkcanuck 02:54, 19 August 2009 (UTC)

Awesome, thanks! I'm not sure what you mean by "query strategy"? Some of it's very similar and I was able to adapt some of the twitter app code, but this is PHP while that is Perl, so there are some differences. Oh, if you mean about watching until it hits 2000 battles, no ... this is just taking a snapshot from the server right now. So you'd have to use this after it's stable. --Voidious 02:57, 19 August 2009 (UTC)

I meant how you're querying the data. Assuming that you're doing a rankings query, then maybe a participant query if the bot isn't active? --Darkcanuck 03:02, 19 August 2009 (UTC)

Ah... Right now, I'm actually doing both each time, but I can tighten that up a bit. =) --Voidious 03:05, 19 August 2009 (UTC)