Talk:Main Page

From Robowiki
Jump to navigation Jump to search

Contents

Thread titleRepliesLast modified
New Rumble Categories813:16, 16 January 2023
is wiki css broken?721:58, 3 March 2019
First page
First page
Previous page
Previous page
Last page
Last page

New Rumble Categories

I don't think code size is a good limiter for different rumble types, because it forces people to do all sorts of tricks which results in very difficult to understand code. In addition, code size is so small compared to memory now that it hardly seems relevant in most cases. What if new rumble types were added where time per tick is the limiting factor: QuickRumble, with half the time, FastRumble 1/4, HyperRumble 1/8, SlowRumble 2x, etc. (Names are arbitrary) This would mean bots in faster rumbles would have to make more time tradeoff decisions, (less precise prediction? more approximate GFs?), and perhaps bots in slower rumbles could find a use for non-KNN classification schemes that required more time. What do you think?

Straw (talk)23:47, 17 March 2014

Tick time size sound like a fantastic idea, I think robocode has some built in constants which potentially can be tweaked for time based rumbles.

But, I would still keep size based categories. I personally amazed how much can be squeezed into small code. It is indeed unreadable, but they set a bar and send a strong hint to me when those little gizmos level my megabot.

Beaming (talk)00:52, 18 March 2014

I'm not advocating the destruction of the codesize limited rumbles, just the addition of time limited ones.

Straw (talk)02:11, 18 March 2014
 

The problem is categorizing them. Right now they are automatically sorted into the categories, since codesize is a compile time constant. However time limiting is a run time value. You would have to run a number of battles to place a robot. Even then you need to decide if something that is under the certain limit 99.9% of the time but over 0.1% of the time should be in which category, and so forth.

Chase10:13, 18 March 2014

Well, we can make a time tick fixed competitions. Every one participate but bots which designed with time constrains in mind will sort to the top by themselves.

I think it is analogous to current size based system: nano bots participate in mega bots competitions and have good chances, but it is not true in reverse. Though here we can participant selection in advance.

So all we need is good tick measure, which is not that easy with current CPU which tend to throttle and boost their performance.

Beaming (talk)13:42, 18 March 2014
 

In my model, you could submit any bot to any category, but it would skip turns if it took too long for that category. So time limits implemented the same way they are now, but with different categories.

Straw (talk)04:04, 19 March 2014
 

The problem I have with this idea, is that the Robocode engine's control over CPU time is far too approximate for that task.

The nature of such a league is to encourage people to push the limit of the alotted CPU time, however one can expect the calibration of CPU time to be off by wide margins between different computers, or even different runs on the same computer.

If one wants to have a league where the CPU time is a primary design constraint for bots, we need an engine with more precise management of this, such as by using Java bytecode instrumentation to assign fixed costs to different Java bytecode instructions... but that... that gets very complicated to implement.

Rednaxela (talk)18:49, 20 March 2014

I agree that would be the best way, and also very expensive to implement. If the VM itself tracked it, that would be another story, but as far as I know, it doesn't.

Chase17:14, 23 March 2014

what would happen if the VM itself tracked it

Tmservo (talk)17:38, 23 March 2014
 
 
 

is wiki css broken?

When I look at discussion threads, I do not see anymore separate post highlighting? The whole discussion with action links now looks like one a single continuous stream.

Does anyone else experience it?

Beaming (talk)18:13, 2 March 2019

I experienced the same bug two weeks ago. But it seems fixed for me now, even though I didn't do anything.

Perhaps it's an intermittent issue?

MultiplyByZer0 (talk)19:07, 2 March 2019
 

The issue seems to be with the js resources which fails to load

Xor (talk)02:41, 3 March 2019

I have a theory about the root cause of the problem, but I need more data to confirm.

Can someone experiencing this issue please open the browser console (F12 -> Console tab), and post the contents of it? Also, which browser are you using?

If I my idea is right, you should see Uncaught ReferenceError: jQuery is not defined.

MultiplyByZer0 (talk)06:55, 3 March 2019

Same here. That's why I suspect the cause is js resources. However this issue seems to happen some time, and disappear some time. Maybe browser caches that once it successfully loads.

Xor (talk)07:15, 3 March 2019
 

I see something else in Firefox:

SyntaxError: illegal character load.php:1:190

When I go to

view-source:http://robowiki.net/w/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=monobook&version=20140108T004349Z

After character 190 it is a bunch of strange characters. I guess something was corrupted on the database?

Skilgannon (talk)15:35, 3 March 2019

Yeah, it looks like jQuery is missing a byte somewhere.

Enamel 32 (talk)21:57, 3 March 2019
 

It seems there are two separate problems then.

Everyone who sees Uncaught SyntaxError: Invalid or unexpected token is:

  • Using Monobook (the default skin), either by choice or by not being logged in.
  • Experiencing this problem continuously.
  • The root cause is that this script, which should contain jQuery and MediaWiki frontend code, has parts of it overwritten with 155648 0x00 bytes.
  • Because that script does not parse, the loading process is broken.
  • This probably requires a server-side fix.
  • People seeing this: Skilgannon

Meanwhile, everyone who sees Uncaught ReferenceError: jQuery is not defined is:

  • Using the Vector skin.
  • Using Chrome.
  • Experiencing this problem intermittently.
  • For the Vector skin, this script, which contains jQuery and MediaWiki frontend code, it perfectly fine.
  • However, that script is loaded by this script through document.write() of a <script> tag.
  • Chrome is known to block the use of document.write() to load scripts on slow Internet connections.
  • Thus, since the script that contains and exposes jQuery is not loaded, other code that depends on it errors with Uncaught ReferenceError: jQuery is not defined.
  • Possible fix: Go to chrome://flags, set "Block scripts loaded via document.write" to "Disabled", and restart your browser.
  • People experiencing this: Xor and past me
MultiplyByZer0 (talk)21:58, 3 March 2019
 
 
 
First page
First page
Previous page
Previous page
Last page
Last page