There was a problem with the translation of the website. It should be fixed now. Apologies for the inconvenience!
StarCraft 2 Progaming Statistics and Predictions
There was a problem with the translation of the website. It should be fixed now. Apologies for the inconvenience!
Due to security concerns, we have redeployed our entire setup on a fresh install with newer software. Because of this there may be undiscovered bugs. If you find any, please let us know by reporting an issue on github.
Thank you for your patience!
We have finally managed to translate Aligulac into Simplified Chinese, thanks to GitHub user StephenKingJJY for the translation. If you find any errors, please report them by either sending us an email or by creating a GitHub issue.
Once we got off our asses, it didn't turn out to be a big deal at all. Aligulac now runs on upgraded infrastructure, which should reduce downtime and lead to snappier response times, especially when we get all the kinks ironed out. (So far there haven't really been any.)
Thank you all for your patience!
We're terribly sorry about the recent downtime problems. We will move to another host as soon as we can.
You can now search a players game history for only games in the WCS system! On a players Match History page, select the criteria you want to sort by at the lowermost dropdown menu named "WCS Tiers". You can sort by both WCS Tier and the nativity of the event (1st/3rd party organizers). We know this feature has been wanted for a long time, and we are happy to have a front end interface to the WCS system we have had in place for some time now. We will be working on improving the accessability to the data and hopefully add it to the general search page soon™.
Aligulac in collaboration with Millenium proudly presents the French translation of Aligulac! This is thanks to the effortless work of Frédéric Leprévost, Nicolas Verger and @the_ppn over several months. It has been thoroughly tested and should be a quite high quality translation.
To get your dose of Français, head over here.
Millenium have also published an article.
From today, you can use Aligulac in Polish! This thanks to the thorough and professional work of Krzysztof Krasuski, representing netwars.pl.
This is particularly exciting for us because it's the first translation done 100% by someone who hasn't worked with Aligulac before, and it also represents a larger community than any of the previous translations (save English, of course).
Yes, it's true. We just added a Danish translation. Enable it here. Thanks to our tweeter and PR guy Morten!
We have supported translation for a while, but the actual work has been slow. We have now found ourselves forced to disable translations on the API documentation. It's long, technical, and difficult to translate. On the other hand it is probably of little interest to someone who doesn't already speak decent English, so I gather that this is not a huge loss.
From what I understand, the French translation is very close to being completed. We still would like someone to help us with Korean!
And for those of you who are giving up on our rating system, we are working on it. There's a reasonably promising modification in the pipeline which I hope will not be too long off.
We've just deployed our new comparison feature, make sure to check it out. Compare
Note that a full refresh of this site is needed (Ctrl+R, Ctrl+F5 or whatever your browser uses) as the CSS has been updated.
I'd like to apologize about the recent downtime issues we've been having. We've just made a fix in the configuration of our database server that we hope will fix the issue. Fingers crossed!
If you're a heavy user of the API you might want to check out the documentation again. We have added two meta-relations to event objects that will make it easier to search for matches and events across several levels of the event tree. (It's hard to explain, the documentation makes it more clear I hope).
We have also made the internal search function used by our own autocomplete feature available for everyone to use. This makes it easier to search for players, teams and events.
Since we have significant amounts of visitors from non-English speaking countries (in particular South Korea, Russia, France and Germany), we have spent the last month enabling translation for our site.
Since yours truly speaks Norwegian, that's the first language we enable, aside from English of course.
If you would like to see Aligulac in a language you speak well (perhaps one of the four already mentioned), please consider helping us translate the site. It's not a particularly massive task (about 1400 strings). Let me know please at evfonn(at)gmail(dot)com.
UPDATE: We have teams working on Russian, German, French, Dutch, Spanish, Danish, Swedish and Chinese. Korean is still very much desired.
Our resident frontend magician Hotspur (yes, that would be the Tottenham kind) has been working with our resident backend magician Prillan to cook up some autocompletion features for us. You can find them in the top right search, as well as on the inference and results search pages.
If it looks weird please make sure that you fully refresh the page, i.e try all of F5, Ctrl+F5 and Ctrl+R (or for the Mac folks, something like Cmd+Shift+R.)
We just changed the menu. If it looks weird please make sure that you fully refresh the page, i.e try all of F5, Ctrl+F5 and Ctrl+R.
Soon it will be one year since Aligulac was started, and although I didn't plan the timing, I'm still happy to introduce our perhaps most-requested feature so far: the API.
For details, please refer to this page. We now enter a period of beta testing. During this period, please understand that we may remove features without warning if we find that they can be abused. Once we release the full version, the URL will change and the feature set will remain as constant as we can possibly allow.
If we have previously designed API-like functionality for you, please migrate your application over to this interface as soon as possible. We will no longer guarantee the long-term survival of these other patchwork solutions.
The database will remain available for download, which is recommended over the API for experimental users with heavy query loads.
Please attribute our website if you make use of this anywhere. It would make us so happy. :-)
We are aware of the current server problems. It is caused by high memory usage during times of high load.
Hopefully we will be back at full capacity soon.
In the meantime, if it keeps failing, let us know @Sc2Aligulac.
Welcome to the «new» Aligulac! Yes, I know. It looks rather like the old one. I hope that the changes we do have was worth the wait.
Mostly, the exciting improvements are under the hood:
I have decided to remove the compare feature, since it was pretty dull and mostly superseded by the match prediction page. I can add the p-value there instead, if anyone's interested.
In the beginning, there will likely be some problems and bugs owing to the rewrite. Please feel free to report issues here.
On the 26th of September, we will take down the server pending an upgrade of various parts of our stack. This isn't expected to take very long, but me being as inexperienced as I am, don't expect to be able to access the site that day. :)
See you on… the other side!
Just a quick update for everyone who are wondering.
As many of you (at least those of you from TL) might know, I'm currently busy finishing my Ph.D. I was hoping to have most of the work done by the end of August, but that's not exactly the case. Still, I have found some time to being a long-awaited upgrade to the site, which is planned to involve:
I'm not particularly experienced as a project leader, and the code quality has suffered as a result. It's time to fix that.
At the moment, no major features are planned, but I'll get around to several minor ones as I notice them. When I graduate, I expect devlopment to continue as normal. Until then, this major rehaul will take some time.
A continued thanks to everyone for their interest in our work. It's been loads of fun working on it!
A note regarding donations and advertisement: Thanks (really, thanks!), but we don't need money. If the time comes when we do, I'll let everyone know. Until then, I am more interested in recruiting database maintainers and developers (-> evfonn(at)gmail(dot)com).
I've been promising a change in the rating algorithm for a while now, and finally it's here. The changes are numerous, but the most significant are:
I won't promise that this is the final version, however!
I'm sorry, but I'm still tinkering with the rating system off and on. In about one hour when the midnight (CET) update goes through, you will see some changes. The leaders will be about 100 points lower than before, for one. There will also be slightly more foreigners in the top 40. Hopefully most of you will not consider this a grave insult to your favourite Koreans.
The aim of this modification is to tweak the rates at which ratings adjust. Players who play rarely will now have their ratings adjust faster than before, and players who play more often will adjust somewhat slower. Overall, most of the players fall into the latter category, so I have also increased the uncertainty floor and the uncertainty decay rate to speed up adjustments over the whole player pool. You will see that uncertainties will be a bit higher than before.
There is yet another change that I am looking at making, but hopefully that won't have a big impact. More on that later when and if I get it to work.
The predictive power has not been affected, and is even slightly improved in some cases, such as very large skill gaps.
So, since last time I wrote a blog post, a lot has happened.
Most importantly, the rating system has been tweaked a bit following the discovery of a bug. Now it is much more conservative than before. The site will also provide continuous updates every six hours instead of every two weeks. The matches are still grouped in two week periods, but the preview of the next list is now kept up to date, so you can see the ratings change in "real time".
I have also opened for everyone to submit results to the site. Hopefully this will lower the bar for the general public. If you see anything missing there's literally nothing to it other than to submit it. Don't worry too much about the details, we can work that out ourselves when we review your submission.
The event catalogue has now grown quite large, and two thirds of the database has been catalogued. This is slow, hard work, and we need every man we can get. The result will be something quite unlike anything that exists.
Speaking of which, the Aligulac database is already unlike anything else. It's the most complete publically available pro/semipro SC2 database in the world. I only know of one other database which is bigger, namely the internal Blizzard one, which is hardly public and wouldn't be very useful even if it were (for these purposes, anyway).
Other than that, most other updates are in usability and minor features. The prediction system now supports four formats, and player/results search has been heavily improved.
Ferguson Mitchell of ESFIWorld was kind enough to publish an interview with me. It is not extremely current, but probably a good read anyway.
Since last time, some things have happend. First, we have a new rating list. Since there weren't so many games over the new year, it looks almost the same as the previous one. I have also changed the fonts a bit, and made the site fully zoomable (try it).
Several of the menu options should now have submenus, and a slightly red colour will indicate the currently selected pages.
We have a Hall of Fame page. On the rating list you can sort by any of the four ratings. (I will add filters in the future.) You can search the results database. (This feature has room for improvement, which will come eventually.)
Most excting for me is the event interface.
In the database there are more than 29,000 matches, the majority of which have no event information associated with them. This is a shortcoming that I hope to fix. New games are added with event information, but this is only textual, and may not be consistent over a whole event.
For this reason I have created the event system, where events are arranged in a hierarchical fashion (e.g. GSL -> Season -> Code S -> Ro32 -> Group A), and matches are linked onto this chain wherever appropriate.
The downside is of course that matches have to be assigned to events manually, and it's pretty daunting to search through 30,000 matches to find the ones you need. Currently, about 6.4% of the matches are assigned to an event object, and 20% have any kind of event information at all.
Hopefully these figures can be pushed close to 100% some time in the future.
The biggest newest addition is the teams page, where I have ranked most of the premier teams in two ways. Both are percentage type scores, in a massive hypothetical round-robin involving all teams on the list.
The all-kill score is generated assuming a best-of-9 format, that is, the first team to eliminate five players on the opposing team wins (this is used in the GSTL, for example). The teams are assumed to always field their five best players (by rating) in increasing order. (This is not very accurate, but what can you do?) I have also allowed teams with fewer than five players to get an all-kill score. (Which will be very poor, of course. For SK to win an all-kill match, MC would have to win all the games himself, for example.)
For Proleague score, I am using a best-of-7 format (as seen in Proleague). The teams are assumed to field their best six players in a random order (again, not very realistic), and their best player in an eventual ace match. Teams with fewer than six ranked players won't get a proleague score.
The scores on the teams page represent the expected match score of the team in such a big round-robin. Thus Startale's 96.48% shows that they can expect to win that many of their 40 matches against the other teams.
The all-kill format rewards teams with one or two exceptionally strong players, and the Proleague format rewards teams with more well-rounded lineups.
Some useability improvements have also been made. On the results page there is now a date picker widget, and for each player, there is now a big match history page, with all his or her matches in the database. In addition, I have reworked the records page to only show one record for each player, and to count them only after period 12 (corresponding to the release of the game), to avoid artefacts from the early lists such as DIMAGAs massive lead on list 1.
Happy new year!
Today I have made some changes to the prediction system. Mostly you will not notice anything different, except that you now enter player names in a different way. This is to facilitate more formats (groups, team matches, brackets...) that will be added in the future.
I know the entry of players can be slightly awkward, especially with players like the two Korean Zergs Shine and the Protosses HerO and herO (who cannot be distinguished in a case-insensitive format). Hopefully I can make this easier in the future. For the vast majority of cases I have found it's effortless.
So in response to the volatility debate I have made some changes to the parameters. The ratings should now be somewhat more stable for players who compete frequently, and a bit less stable for new and infrequent players.
All ratings from the beginning have been recomputed, so you might see some changes from before.
As always, shoutout to Conti, Grovbolle, KristofferAG and PhoenixVoid for the help, and TLO for being awesome!
So, today I have made our results ticker public. I didn't want to do it before now, because most of my results were scraped from other websites. Now, however, we are mostly populating the database ourselves, so I feel more confident allowing access to this information.
On the results page you can go back or forward by a single day or a full month. You can also enter the date directly into the URL if you want:
I'll add a form to go directly to any given date when I get around to it.
The matches are shown grouped by event. This event information is missing from matches that were entered prior to the launch of this site, so expect a bit of a mess up to mid-December 2012. All results are there, they're just a bit hard to make sense of sometimes.
You can now use the ratings to predict the outcome of matches. Just click "predict" in the menu or go here.
The system is pretty basic at the moment, but I'm planning on doing a lot of things with this. It just might take some time.... :(
If you now open a player page you will see, immediately below the graph, a list of games that have been added and which are scheduled for inclusion in the next period.
In the table for historical data, you will also see a "details" link. If you click it, you can see some information about the rating calculation for that player for that period. It shows which games were included, the average rating of the opposition, and the expected score for the player given the opposition. You should see that the rating adjustments correlate with how much the player over- or underperformed. Note that the correlation isn't necessarily exact, since there are a few other factors that come into play (see the FAQ for more details on those.)
I also want to thank Conti, Grovbolle and KristofferAG for aiding me with populating the database with results.
The newest period is published. The top three are now Sniper, Parting and Leenock. Big climbers include Stephano, Scarlett, Huk and Polt. This list includes games from the IPL weekend, GSL code A, the Hyper X playoffs, Iron Sqiud as well as the beginning of SPL and IPTL, among others.
In other news, there is now a possibility for you to submit results to the database. I'm keeping my head above the waterline currently, but every bit would be helpful. Currently the results submitted aren't publicly viewable, but that might be something I change in the future. If you're interested in helping, e-mail me for an account!
After a week or two of work, the site is now public.
Please note that this is still somewhat of a work in progress, and I have several ideas that I would like to implement. Nevertheless, I hope you enjoy what is already here!