Please subscribe to the official Codeforces channel in Telegram via the link: https://t.me/codeforces_official. ×

PedroBortolli's blog

By PedroBortolli, history, 5 months ago, In English,

Hello Codeforces community!

Me and my friend nakamura developed CFStats: a website that allows stats comparison between 2 Codeforces handles.

The comparison includes:

  • Rating graph comparison over the time (just like in Codeforces, but for 2 users)
  • All attempted (but unsolved) problems by each handle
  • Problems solved by tag by each handle
  • Unique problems solved by each handle
  • Problems that both handles solved
  • Contests that each user participated
  • Contests in which both handles participated (and their respective positions)

And we will be more than glad to introduce more features! We are open for your suggestions :)

Also, CFStats lets you create a profile. There, you can save:

  • Codeforces friends (so you can easily compare yourself to them with one click)
  • Problems to solve later
  • Contests to solve later

The advantage of saving such things is that every time your profile is updated a message will appear next to a solved problem/contest telling you it has been solved so you can delete it.

The code is available on GitHub!

We hope that CF Statistics will be useful for someone! If you have any bug report we will appreaciate it!

 
 
 
 
  • Vote: I like it  
  • +160
  • Vote: I do not like it  

»
5 months ago, # |
  Vote: I like it +31 Vote: I do not like it

Nice website.

One drawback: It counts Div2E and Div1C (and so on) versions of the same problem as different. Maybe something can be done about that?

Thanks for the site :)

  • »
    »
    5 months ago, # ^ |
      Vote: I like it +12 Vote: I do not like it

    Thanks for the feedback! We will take a look at it.

  • »
    »
    5 months ago, # ^ |
      Vote: I like it 0 Vote: I do not like it

    There is nothing API users can do about that because Div1C isn't always the same as Div2E and so on. I'd suggest to add some "unique ID" to the task on the CF side for that.

»
5 months ago, # |
  Vote: I like it +5 Vote: I do not like it
»
5 months ago, # |
  Vote: I like it +22 Vote: I do not like it

Love that curl | sudo -E bash - in instructions for setting up the repository.

»
5 months ago, # |
  Vote: I like it +19 Vote: I do not like it

I really like this website! I have two ideas that could added in the upcoming versions:

1) Statistics about contribution (number of topics, number of comments, most upvoted topic, most upvoted comment, most downvoted...)

2) Problems solved by hardness(A, B, C,...G) by each handle

  • »
    »
    5 months ago, # ^ |
      Vote: I like it +4 Vote: I do not like it

    Thanks for the suggestions! I will add them to the pending features.

»
5 months ago, # |
Rev. 2   Vote: I like it +22 Vote: I do not like it

A pretty good website, good job.

but I find some bug,

For problem solve or not you are using last submission status, but the last submission may be wrong although some previous submission status accepted.

so there is a bug in the unsolved(attempted) list.

image...

  • »
    »
    5 months ago, # ^ |
      Vote: I like it +4 Vote: I do not like it

    Thanks for the feedback! This has already been fixed (update your handle's info to see it).

    • »
      »
      »
      5 months ago, # ^ |
        Vote: I like it +11 Vote: I do not like it

      Yes , that is fixed now.

      Two more suggestions,

      If contest list also be in decreasing order like solved problems.

      If you count how many times first user and second user won in contest both user participated list and How many tie as well.

»
4 months ago, # |
Rev. 2   Vote: I like it +8 Vote: I do not like it

A bug (?) found:

The minimum rating change of a handle is chosen to be displayed as the maximum rating decrease, which may not be accurate if the handle does not experience any rating loss. Maybe the same happens in maximum rating increase.

»
4 months ago, # |
  Vote: I like it +8 Vote: I do not like it

Suggesting things to add:

  • Minimum / maximum rating difference
  • Ratio of wins / losses in common participations
  • Number of hacking attempts between the two
  • The list of common / unique solved problems could optionally include only those from common contests
  • The pie graphs should use the same colors for the same tags (otherwise they do not act as comparison tool)