Adding opponent APS in bot comparison?

Jump to navigation Jump to search

Can we assume that APS is relatively stable? Since we can click into the detail page to see the history APS even when that opponent is removed, can we simply put that value?

Opps this assumption breaks when comparing ancient bots ;( Then polluting the table must be a bad idea. However, why don't we use NaN or N/A instead of 0?

Xor (talk)‎01:05, 8 September 2017

NaN sounds most appropriate. I don't want to have to fetch each bot object that is not in the rumble anymore to look up its last APS.

Skilgannon (talk)‎07:30, 8 September 2017

Done. I also added a link on the BotDetails page to find the bot on the wiki.

Skilgannon (talk)‎17:19, 9 September 2017

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Users.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page.

Return to Thread:Talk:LiteRumble/Adding opponent APS in bot comparison?/reply (5).

You can do this with the &limit=0. limit works in both api and html mode, you could also do a sort with a limit=1 to just get a best/worst opponent, etc.

Skilgannon (talk)‎20:14, 9 September 2017

Thanks. It does the trick. Which brings the question: is API published anywhere? I get what I had by looking at the source, but clearly did not look careful enough.

I see that there are dark parts for exchanging with rumble clients too.

Beaming (talk)‎20:23, 9 September 2017

No published API, no. That said, with JSON I don't plan to remove any fields. It is possible field might be added though, which is why I wanted to use JSON to begin with.

Skilgannon (talk)‎20:50, 9 September 2017
 
 
 

WoW that's amazing! Thanks a lot!

Xor (talk)‎23:27, 9 September 2017
 
 
 
Retrieved from "http://robowiki.net/wiki/Thread:Talk:LiteRumble/Adding_opponent_APS_in_bot_comparison%3F/reply_(2)#Adding_opponent_APS_in_bot_comparison.3F__5682"