Jump to content
HWBOT Community Forums

richba5tard

Administrators
  • Posts

    6082
  • Joined

  • Last visited

  • Days Won

    37

Everything posted by richba5tard

  1. I disagree. If OGS (Bob?) does not deserve to be marked as the most noteworthy overclocker of 2018, his submissions are not worth the points. It's not the fault of the seasonal ranking. An all-time ranking just hides the flaws a bit more because it is more static. Please note I'm not saying we should abolish the all-time rankings. I'm just highly in favor of seasonal rankings too. The current algorithm on UAT does not yet take competition points into account.
  2. As usual, a testrun of the algorithm can be seen on http://uat.hwbot.org/ Currently it shows the member ranking based on top 20 total points of each user for year or all time. Teams are currently based on total of member points of current year, not all time.
  3. @Don_Dan @Leeghoofd i've edited the first post: use top 20 submissions instead of all, both for yearly as for alltime keep hw masters give points for official competitions "Calculate Top 20 Global Points (/WR Points) + Top 20 Hardware points + Top 10 Competition Points." I'd rather keep it more simple and say "top 20 submissions" count toward your league points (so wr+gl+hw), top 10 competition points. It avoids confusion about the different types of points you have, which is overwhelming for new overclockers.
  4. I don't see why you oppose so much to a seasonal ranking, next to an all-time one. The all-time one is way too static and not that interesting. A seasonal one is much more interesting, and resets each year. Your all time efforts would not be lost, they would be displayed in the all-time rankings. About hw masters, it makes sense to keep it if we do as Don_Dan suggested, to do a top 20 for normal league.
  5. While I don't like that your member points are not the sum of your submission points it is easy to explain you can get points for competitions too. I'll take it into account if we can keep it simple. Yes, that is my suggestion. The team and country points would be the sum of the member points of that team/country so would be based on the same logic. I can live with your top 20 suggestion, but only if we apply the same logic for the yearly rankings as the all time rankings. Much harder to code (without needing much computational power) than using just the sum though. No specific feelings towards enabling/disabling points for benchmarks. Like suggested, I want to keep the schedule and round/stage pages, but just read only view. The oc-esports pages are currently already optional, you can view the competitions on hwbot.org too. No specific feelings towards enabling/disabling points for 3D06.
  6. As I don't have sufficient time to maintain the complex algorithm of hwbot rev6/7 and the rankings are too complex to explain: here is my suggestion for rev8. It's dubbed "classic" as it is as easy to explain as rev1/2/3. Submission points (mostly as is): benchmark as-is global points if score is 50% of WR, not top 75% hardware as-is More focus on medals, a bit less on points. Member points rankings: Career Ranking: Sum top 30 globals + top 60 hardware submissions all time Season Ranking, split into leagues: Sum top 15 globals + top 30 hardware submissions + top 10 competition entries made in current year, split into leagues Team points rankings: as-is team power points. As TPP includes 1/10th of the total points made by submissions linked to the team, there is a small impact from the global points change. Country points rankings: Sum member points current year Hardware / global masters rankings As is. Competitions: Top 10 entries of current year (seasonal ranking) and top 10 all time (career ranking) count for member points, no more oc-esports/road to pro/challenger points. Achievements: TBD, good concept but takes too much computational power? oc-esports.io Rankings scrapped, only to be used for read only view of schedule and the competition/stage pages. Thoughts?
  7. GALAX has provided a tool for experts to tweak their Galax HOF OC Lab Edition 2080ti. Let us know if you want to use it!
  8. Hi IKKI, Galax has provided a tool to tweak the Galax HOF OC Lab Edition 2080ti extreme cooling. Drop us a note if you want it use it. :)
  9. Ok, I was clicking the hardware not the submissions. Investigating! - edit: cause found, pushing fix to test servers
  10. You mean this page, when you click a processor name for example? They all work for me...? Or do you mean another page?
  11. Allright guys, as I still have not figured out what flow messes up the rankings, and nobody seems to be able to reproduce it on the test environment, i've provided a "recalc" button on the rankings page where everyone can force a recalc of the currently shown ranking. Don't abuse. ?
  12. Hope we configured everything right leeghoofd! For those that want to help testing, team cup submissions are already open on the test server (uat.hwbot.org). Any issues reported today I can still fix, otherwise it will have to wait till Friday.
  13. I've added a sanity checker which checks for broken rankings every hour. The current definition of "broken" is getting 0 hwpoints for first spot which is not a solid approach but at least it fixed 14 rankings today. If someone can shed some insight on scenario's how to reproduce braking a rank, it would be greatly appreciated. You can use uat.hwbot.org for messing around. It contains the latest code but not the latest submissions, always a few weeks/months behind on production.
  14. Typo, it's hwbex.src = 'https://www.hwbot.org/js/exf2.js'; not wbex.src = 'https://www.hwbot.org/js/exf2.js'; The h got lost with copy pasting the code.
  15. Sorry, not sure why but it keeps using the non https version. You can't mix https with http, the browser will prevent that. Can you force https by changing above line to: wbex.src = 'https://hwbot.org/js/exf2.js';
  16. Please replace: hwbex.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://') + 'hwbot.org/js/exf2.js'; With: hwbex.src = ('https:' == document.location.protocol ? 'https://' : 'http://') + 'hwbot.org/js/exf2.js';
  17. You might! Please check if you have a reference to https://ssl somewhere in the hwbot code snippet.
×
×
  • Create New...