Sections
Home
Hills
Infinite Hills
Tournaments
Software
Evolving
Optimizer
Community
Newsletter
Discussion
History
Sections
 
For Beginners
First Steps
FAQ
Guides
Lexicon
Benchmarks
For Beginners
> Home > Redcoders Frenzy > The Powers of Ten Round

Redcoders Frenzy - The ongoing corewar tournament

The Powers of Ten Round
Organiser: Chip Wendell


Rules

Time to free yourselves from the confines of tiny coresizes, and explore the open spaces of a truly huge core!
Core size =   1,000,000
Max cycles = 10,000,000
Read limit =  1,000,000
Write limit =    50,000
Max processes =      10
Max length =       1000
Min distance =   10,000
P-space size =  100,000
Number of rounds =  100
P-space is allowed, but PIN is not (no handshaking). The battles are fought Round Robin with no self fights. Two entries are allowed per author. Three points for a win, one point for a tie.

Please note the write limit. You'll need to use either CoreWin 2.2 or Joonas' R/W limit patch for pmars.

Hints

- There is no read limit, so scanners can see all of core. But they'll have to send out proxies to attack anything they find. Here's where p-space can come in handy: sharing information and instructions with your far-flung processes.

- With only 1/20th of the core reachable by any process, and only 10 processes, imp spirals are impossible, because the head can't wrap around to the tail. It also means that no set of static processes can bomb all of core. Mobility will be needed.

- There's plenty of room and plenty of time, so don't feel rushed. There's no danger of being hit by a qscan in the first 20 cycles! Perhaps this is the time to dust off some of the more complex strategies (cooperating processes, self-repair programs) that never seem to succeed on the standard hills.

FAQ

There have been a few questions about the RF23 round, so I've put together a brief FAQ.

Q: Why isn't my warrior working the same under CoreWin and pmars?
A: As I noted in a previous post, CoreWin has a bug in the way it reads settings from a .cfg file. Each time you start CoreWin, you need to type numbers into the write limit and p-space size boxes in order for those parameters to be set properly. If in doubt, run MOV 0,50001; it should behave as a normal imp.

Q: How do read/write limits work?
A: This is a long one, but here goes:
Every address in Redcode is either a read address or a write address. Basically, a write address is any address at which the core contents are (or could be) changed, and everything else is a read address. For instance, in a MOV $X,$Y instruction, X is a read address but Y is a write address. All compares, jumps, and SPL use read addresses, because nothing is changed in core. The address that's decremented by a DJN is a write address. Each of the indirect addressing modes involves two addresses, which may be classified differently: in a SUB >X,}Y instruction, both of the intermediate addresses (X and Y) are write addresses, because they're being incremented; the final addresses (X+[X.B] and Y+[Y.A]) are read and write addresses, respectively.
Under R/W limits, each write address is calculated modulo the write limit (WL), so that the address is "folded" into the range -WL/2+1 to +WL/2. Similarly, each read address is folded modulo the read limit. Under RF23 rules, the read limit is the same as the coresize, and since all addresses are calculated modulo the coresize anyway, the extra folding has no effect; any address in core can be "read". But the write limit is 50000, so every write address will be folded into the range -24999 to +25000, relative to the current instruction. This is true even for indirect addressing; MOV bomb,@ptr will bomb the same section of core no matter how far away ptr is.

Note that p-space addresses are not subject to R/W limits. STP #42,#90000 will store a value in p-space location 90000 under RF23 rules. (P-space addresses are folded modulo the p-space size, but that's a different story.)

Results

In a very close result, Roy van Rijn squeaks out a narrow victory over Christian Schmidt and German Labarga, on the strength of his clever non-PIN handshake. Nenad Tomasev finishes a very strong fourth.

#%W%L%TName AuthorScore%
146.19.744.2R1_Win Roy van Rijn182.5100.0
247.413.738.9Dementor Christian Schmidt181.099.2
347.918.134.0IR-Flashlight G.Labarga177.797.4
440.911.547.5e4 Nenad Tomasev170.393.3
543.518.538.0e1 Nenad Tomasev168.692.4
643.719.037.3UV-Scorch G.Labarga168.592.3
736.419.244.5R2_Loser Roy van Rijn153.584.1
832.538.628.9don't know if.. John Metcalf126.369.2
922.939.537.6Cloe XL John K. Lewis106.458.3
100.338.361.5Tie&Knot NTW Lukasz Adamowski62.334.1
115.967.027.1castle of mirrors John Metcalf44.824.5
124.378.617.1Dead Planet.. Lukasz Adamowski29.916.4


2002-2009 corewar.info. Logo C. Schmidt
The Rounds
Round 25
Round 24
Round 23
Round 22
Round 21
Round 20
Round 19
Round 18
Round 17
Round 16
Round 15
Round 14
Round 13
Round 12
Round 11
Round 10
Round 9
Round 8
Round 7
Round 6
Round 5
Round 4
Round 3
Round 2
Round 1
The Rounds