[00:00] Join: pjwaffle joined #corewars [00:00] hi [00:01] I need help with redrace [00:01] it has a big scary segmentation fault :( [00:01] I compiled it under Ubuntu Linux with GCC 4.3.2 [00:02] I even tried to link it with libgc [00:27] MSG: Read error: Operation timed out [00:41] Join: Altair joined #corewars [00:42] hi [01:08] MSG: [01:33] MSG: Quit: humhum [02:14] Join: X-Scale2 joined #corewars [02:17] MSG: Ping timeout: 240 seconds [06:03] Join: CwarsV1 joined #corewars [07:51] MSG: Remote host closed the connection [09:32] Nick Change: X-Scale2 changed nick to X-Scale [09:32] Nick Change: X-Scale changed nick to NorthStar [10:18] Join: fiveop joined #corewars [12:57] Join: Altair joined #corewars [12:57] hi [13:04] is it possible to initialize a "mov 0, 2667" and "djn.f 0,{nnn" 3 times with a certian distance that way, that the stream starts afterwards the imp? [13:14] Join: myndzi joined #corewars [13:16] MSG: Ping timeout: 240 seconds [14:00] explain again, what are you trying to achieve? [14:26] ^_^ [14:27] okay. i want a mov 0, X and a djn.f 0,{300 for example to initialize that way in the core, that 3 of these make up an spiral if the reach themselves: djn.f -1<- jumps to the spiral [14:29] hard to explain, but the idea is very simply [14:29] 2x3 instruction in the core, same distance [14:30] but I dont get the spiral working [14:31] so, you want a spiral that has a djn-train? or three djn's which will turn into a spiral when meeting a 1,1? [14:31] or a djn which will fill a dead process? [14:33] okay: first copy the mov 0,2667 and djn.f 0,{2500 in the core which distance 2667. then start 3 processes, each an the djn.f [14:34] the decrement and decrement and when they reach temselves, the jump to the spiral. but somehow im too stupid to achieve a working spiral -.- [14:35] well, its a synchronozation-problem then [14:35] the processes should be running 123-123-123-123 but instead you have them as 321-321 or something like [14:36] so it is possible, but the sync is somehow crapp? [14:36] yes it is [14:36] okay, thx. I will try it out. [14:37] Im sure I will bother you at least 1 more time with this. :D [14:37] thx. try it out this evening [14:37] cu [14:37] MSG: [19:43] Join: Metcalf joined #corewars [19:44] Hi :-) [20:24] Join: pjwaffle1 joined #corewars [20:24] hi [20:33] Hi pjwaffle1 [20:33] Are you new here? [20:40] oh sorry [20:40] yes [20:40] I am [20:40] how do borg's work? [20:43] borgs? As in corewar programs written in redcode? [20:52] yes [20:52] but they supposedly assimilate code [20:52] I am guessing it uses pspace right? [20:53] Is this anything to do with MicroGP? [20:57] yes [20:57] besides that how do you use microgp for corewars anyway? [21:00] no luck with google [21:00] I even checked google groups [21:00] on rec.games.corewars [21:03] To be honest, I haven't tried to use MicroGP [21:04] I've experimented with Yace. It's possible to start evolving with Yace within a few minutes of download [22:01] Join: CwarsV1 joined #corewars [22:01] hi [22:02] h [22:04] hi Mizcu! :-) [22:05] MSG: Ping timeout: 240 seconds [22:07] Mizcu, can you tell me an idea how to stop imps with multi threaded (spl) code? [22:11] by having large, average part of the code(s) to run something to squash imps [22:11] i dont mean to intentionally put impgates everywhere, but simple aggressive offensive can work [22:12] (until you get to really bad paper/imps, which pretty much need a specialized warrior to be reliably defeated) [22:25] simple aggressive offensive? [22:27] well, let your warrior do what it does best, and dont take the imp-problem too seriously until you get into "medium" problems [22:30] i see [22:32] is it a good idea to replicate code to, lets say 200 addresses after current location after every 200 cycles? So imps can hopefully never catch my warrior? [22:32] Hi CwarsV1 [22:32] Hi [22:34] CwarsV1: "replicate" = copy, which would mean that the original code is still active, and might be overwritten by the imp [22:36] CwarsV1: moving the warrior around in middle of a match is not very common, at start of match yes, and papers do not much else, but still, copying around takes instructions, making the warrior usually too heavy to fight properly [22:37] yes. the warrior lives every 200 addr. at another place. [22:37] you have to remember that when imp overwrites something, it becomes an imp too [22:37] Hmm. ok. Then lets say: Every 500 cycles. [22:38] so if you have 4 copies, and one gets overwritten by imp, you have only 3/4 'active speed' [22:38] ok [22:38] sorry. [22:38] thats ok, theres lot to learn [22:39] i just forgot of using spl and fighting against imps. so my idea: [22:39] only one process, ... [22:39] and even though a warrior makes copies, a warrior still runs at same speeds; warrior with 10 copies has each copy run at 1/10 speed [22:39] ... bombing the memory ... [22:40] and seldomly changes location. [22:43] it is simple and genial, isn't it? [22:44] sure [23:02] ok. so i code it and send it to the hill. [23:29] MSG: Quit: Leaving. [23:36] Join: myndzi\ joined #corewars [23:37] MSG: Ping timeout: 240 seconds