SCFusion - WoL, HotS & LotV Build Order Optimizer - Page 20

LegacyObserver

United States32 Posts

November 21 2010 02:20 GMT

#381

Suggestion: I think your waypoints would be more user friendly if they were aligned with typical early game timings instead of a basic 300 second interval. It's a very simple change that I perceive would be much more useful overall.

Waypoint 1: 6 pool timing (~3:20)
Waypoint 2: Standard non-cheese rush timings (~5:20)
Waypoint 3: Standard push timings (~6:30)
Waypoint 4: Midgame push (~9:00)
Target: Good time period to do most builds (~15:00)

Knightlax

United States150 Posts

November 21 2010 02:39 GMT

#382

Hey C12 (you like what I did there?),

Would it be possible to designate Nexi as Nexus (1) and Nexus (2), etc.? I can't tell what Nexus I'm supposed to be chrono boosting.

Specifically, I've been running your program to get the fastest mothership possible, and I can't tell if the program is building probes out of the nexus that is also building a mothership (obviously not possible in game, and from what I can tell, it is not building probes out of the mothership nexus, but I want to be sure) and I also can't tell if it has me chrono boosting both nexi or just one then the other, or a combination of the two. Also, I can't tell if the energy rate is increasing twice as fast since I have 2 nexi built and can chrono from both.

+ Show Spoiler +

If you notice, in bold, I build a probe at 4:52. I then start the Mothership at 5:46. Clearly the probe is already finished by then, even without chronoboost, so the upcoming Mothership (@5:46) will be the only thing building. It has me Chrono a nexus at 5:46 and then again at 5:57 (~11 sec difference), but I don't have anything building except the mothership and it doesn't ask me to build a probe in the 2nd nexus until 6:22. But chronoboost lasts 20 seconds, not 10, which is the difference between the 2 chrono's in the list. Since I'm not also building out of the 2nd nexus, I guess I'm chronoboosting an empty nexus?

Also, if you look at the 2nd part in bold, I have 28 E, I spend 25 on chrono (3 energy left), then 10 seconds later I have 34 E to chronoboost again. I don't see how I can get 24 more energy in 10 sec. As far as I can tell, Energy gain per sec is about .53-.54 E/sec. Even with 2 nexi, I shouldn't get 24 energy in 10 sec. Did I miss something here?

If I just haven't read the lines properly and I'm being dumb, let me know!

Also, the parameters for running this were Target = 600 sec, 1 Mothership. That's it. Everything else was left as default, even the waypoints.

EDIT

It came up with a faster Mothership in the middle of this reply, with no expansion, so I wanted to post it in case anyone was interested.

+ Show Spoiler +

0:02.00: 50M 0G 0E 6/ 10S - Build Probe
0:19.00: 73M 0G 10E 7/ 10S - Build Probe
0:36.00: 106M 0G 19E 8/ 10S - Build Probe
0:46.44: 113M 0G 25E 9/ 10S - Chrono Nexus
0:46.44: 113M 0G 0E 9/ 10S - Build Assimilator
0:50.81: 60M 0G 2E 9/ 10S - Build Probe
1:05.11: 100M 0G 10E 10/ 10S - Build Pylon
1:16.44: 73M 0G 17E 10/ 10S - Move Probe To Gas
1:30.11: 160M 10G 25E 10/ 18S - Build Gateway
1:37.30: 50M 15G 29E 10/ 18S - Build Probe
1:37.30: 0M 15G 29E 11/ 18S - Chrono Nexus
1:37.30: 0M 15G 4E 11/ 18S - Move Probe To Gas
1:37.30: 0M 15G 4E 11/ 18S - Move Probe To Gas
1:48.63: 54M 36G 10E 11/ 18S - Build Probe
2:01.30: 74M 60G 17E 12/ 18S - Build Probe
2:09.58: 75M 76G 22E 13/ 18S - Build Assimilator
2:35.11: 170M 124G 36E 13/ 18S - Build Cybernetics Core
2:39.80: 50M 133G 39E 13/ 18S - Build Probe
2:39.80: 0M 133G 39E 14/ 18S - Chrono Nexus
2:39.80: 0M 133G 14E 14/ 18S - Move Probe To Gas
2:39.80: 0M 133G 14E 14/ 18S - Move Probe To Gas
2:39.80: 0M 133G 14E 14/ 18S - Move Probe To Gas
2:51.13: 53M 174G 20E 14/ 18S - Build Probe
3:03.80: 72M 219G 27E 15/ 18S - Build Probe
3:25.11: 158M 296G 39E 16/ 18S - Build Stargate
3:31.75: 50M 170G 43E 16/ 18S - Build Probe
3:48.75: 118M 230G 53E 17/ 18S - Build Probe
3:48.75: 68M 230G 53E 18/ 18S - Move Probe To Gas
4:25.11: 338M 369G 73E 18/ 18S - Build Fleet Beacon
4:33.86: 100M 202G 78E 18/ 18S - Build Pylon
5:26.01: 401M 400G 100E 18/ 26S - Build Mothership
5:26.01: 1M 0G 100E 26/ 26S - Chrono Nexus
5:26.01: 1M 0G 75E 26/ 26S - Move Probe To Minerals
5:46.01: 173M 72G 86E 26/ 26S - Chrono Nexus
6:06.01: 345M 143G 73E 26/ 26S - Chrono Nexus
6:26.01: 517M 215G 59E 26/ 26S - Chrono Nexus
6:46.01: 689M 287G 45E 26/ 26S - Chrono Nexus
7:06.01: 861M 358G 31E 26/ 26S - Chrono Nexus

Ncinerate

172 Posts

November 21 2010 16:09 GMT

#383

Looking forward to the zerg version (and of course, T), you're getting this program -so- dialed in. Love it OP!

Fine work, all around.

Antedelerium

United States224 Posts

November 21 2010 19:56 GMT

#384

EDIT: Yeah I forgot a point of reference. This concerns the GPGPU optimization for this program and seeing how much it may or may not help.

Yeah we have no idea how much faster it will be, but if we can handle the breeding/mutation aspects in a way that actually take advantage of unique cores and explore more options, either a) we should have a fast speedup for the same result or b) we'll just get better results in the same amount of time. Shadghost and I will probably work on it with my classmate and we'll let you know what happens with the progress of this. Should be a pretty straightforward modification.

omgCRAZY

Canada551 Posts

November 21 2010 20:47 GMT

#385

One suggestion. Being able to have target times for each entry or atleast categories. I know that I want charge and 2 sentries but I have no way of making sure I get the 2 sentries out by a certain point while still getting charge out as fast as possible.

Barook

Germany143 Posts

November 21 2010 21:54 GMT

#386

On November 22 2010 05:47 omgCRAZY wrote:
One suggestion. Being able to have target times for each entry or atleast categories. I know that I want charge and 2 sentries but I have no way of making sure I get the 2 sentries out by a certain point while still getting charge out as fast as possible.

Use waypoints. Tell it that you want 2 sentries first and Charge in the next waypoint. It should automatically generate a build that gets you 2 Sentries within your given time frame while trying to get Charge asap.

CarbonTwelve

Australia525 Posts

November 21 2010 22:15 GMT

#387

On November 22 2010 04:56 Antedelerium wrote:
EDIT: Yeah I forgot a point of reference. This concerns the GPGPU optimization for this program and seeing how much it may or may not help.

Yeah we have no idea how much faster it will be, but if we can handle the breeding/mutation aspects in a way that actually take advantage of unique cores and explore more options, either a) we should have a fast speedup for the same result or b) we'll just get better results in the same amount of time. Shadghost and I will probably work on it with my classmate and we'll let you know what happens with the progress of this. Should be a pretty straightforward modification.

What you'd want to do is have extra villages that run on the GPU. Each village runs in its own thread, and there's no need for any locks other than when immigration happens (which is once per village per 100 evolutions).

You might be able to rework the evolution/breeding logic to make it multi-threaded for a single village, but it'd be pretty complicated and in the end I don't think it'd be worth it.

AcTiVillain

Australia81 Posts

November 21 2010 23:50 GMT

#388

Lominar wrote his program in Java, and you've written yours in C++. Java has automatic memory management, but your quite clever aren't you?

Dealing with pointers and memory space, I can imagine the headaches your going through.

CarbonTwelve

Australia525 Posts

November 22 2010 00:41 GMT

#389

On November 22 2010 08:50 AcTiVillain wrote:
Lominar wrote his program in Java, and you've written yours in C++. Java has automatic memory management, but your quite clever aren't you?

Automatic memeory management is rather slow. Requires reference counting, garbage collection, locks, and other things that slow it all down. Makes it even worse than just standard dynamic memory allocation.

Dealing with pointers and memory space, I can imagine the headaches your going through.

Heh, I went through that at the start when trying to get my memory pools to be thread safe (well, technically they're still not thread safe, just that it uses thread local storage to have separate pools per thread, and then a threadpool so it doesn't continually create new memory pools). All good now so I don't have to worry about it anymore.

In general that stuff isn't a problem though. If you're used to C/C++ then memory management is easy to deal with and you'll very rarely write a memory leak.

Antedelerium

United States224 Posts

November 22 2010 01:11 GMT

#390

On November 22 2010 07:15 CarbonTwelve wrote:

Show nested quote +

Interesting note. I was thinking about spawning duplicate villages and having each duplicate vary slightly in how they mutate and then comparing them afterwards (think mini-mapreduce style for each village for a certain amount of time), but starting on having extra villages on the GPU sounds like the more reasonable starting place for us.

blackbrrd

Norway477 Posts

November 22 2010 01:34 GMT

#391

Nice program to see what target-times I should set for myself in-game. Since I am a bronze noob atm, I can do a 4-gate push at around 7:30. Setting up a build that needs 1zealot+1stalker and then a 4-gate push with 3zealots and 5 stalkers should be available at 5:24... I have a bit of a margin you could say. (And this is with constant probe-production!) :D

AcTiVillain

Australia81 Posts

November 22 2010 06:58 GMT

#392

I see. So you are taking lominar's java implemetation and taking it a step further by improving memory management by writing in c++

I also wonder how do you distribute the villages at the start? do you just have 1 of them run a 12 gate build, another run a 13 gate build or another do a 11gate build etc etc?

CarbonTwelve

Australia525 Posts

November 22 2010 07:55 GMT

#393

On November 22 2010 15:58 AcTiVillain wrote:
I see. So you are taking lominar's java implemetation and taking it a step further by improving memory management by writing in c++

Yep, not a lot of innovation on my part - Lomilar needs the credit there. I just knew I could write a fairly fast version in C++ due to experience in writing such solvers for other tasks before - I've written depth searching algorithms (modified A* algorithm) for games like Psycopath (flash game), Sokoban, path finding, and a few other things.

I also wonder how do you distribute the villages at the start? do you just have 1 of them run a 12 gate build, another run a 13 gate build or another do a 11gate build etc etc?

All villages run independently and run with the same targets (the ones you set). However due to randomisation they can end up making different choices and lead to different results. Then, 'immigration' happens which causes the best chromosome (build order) from each village to be copied into the city so they can breed with eachother. Once a village has been stagnant (no improvement) for a certain number of evolutions (the stagnation limit - seen as the stagnation for the Overall row in the list control) the village is culled and restarted.

kklawm

Australia1 Post

November 22 2010 14:13 GMT

#394

I made an account so I could thank you -- this is incredible! I was sad when I thought the only program was for Zerg, I was happily wrong. Very happy with this, it is really letting me try out some fun ideas I've had for builds (I like protoss) like a 2 pheonix 1 VR build I've been wanting badly to do (5:35 19P eco-build or 5:48 1 Stalker 13 Probe Build)--btw the post below this one is epic.

Ncinerate

172 Posts

November 22 2010 14:18 GMT

#395

All this talk of C and C++ memory management reminds me of a funny coding moment of my own from back in the early 90's.

I was a "wizard" on a MUD (for the young'ins, think world of warcraft, only completely text based and massively multiplayer in the day and age of dialup internet - the wizards were basically the creators, programmers who built the mud). The mud was mostly based on C and thus coding new areas, items, etc etc etc was fairly straightforward. I decided one day that it would be fun to create a new area (a dangerous cave) with a rather weak old spore carrying mycon creature inside. When the player killed it to retrieve whatever item I had it carrying, it released it's spores into the cave, propagating new mycon creatures, which automatically released spores every so often into other rooms in the cave, surrounding you and making escape a tense and difficult situation.

Or at least that was the plan. I carefully built everything to kill the mycons inside at regular intervals to avoid overpopulation, and the whole thing was safely disconnected from the mud at large while I built it (it was connected to my "wizard" castle in the sky).

Unfortunately, I made that connection to my "wizard" castle a 2-way street. While I was sleeping that night one of the mycon managed to reach the exit of the cave and "propagated" out of the cave. Without the built-in population controls (only present in the cave) it spread spores quickly and exponentially throughout my wizard castle, and hilariously, right to an exit to the main square in the main city of the game (something that I had built in a completely separate area I was designing that the mycon had propagated into). Over the course of the next hour, the mycon flooded into the world, slaughtering -everyone- who wasn't hunkered down in the safe no-attack room under the main square (we called it the bunker). Finally, the crushing memory load of exponentially growing mycons crashed the whole mud.

It was our very own Cataclysm. And my favorite "memory leak" ever.

Conti

Germany2516 Posts

November 22 2010 14:45 GMT

#396

(Edit: Eh, just found out that you can only build one Mothership at a time. You learn something new every day! Still curious what the heck the program is trying to do in this case, though.)

I just found a rather curious bug. Or at least I think it's one. Anyone ever tried to get it to build 2 Motherships? If I tell it to build one it almost immediately gets an acceptable time (< 8 min.) and improves from there. If I tell it to build two.. it builds Probes until it's almost maxed out and then builds one Mothership right before the Target Time. And all the time there's only one Probe on gas. I'm on a laptop right now, so I only got 6 million games so far, but there's no sign of improvement whatsoever.

Target: 2 Motherships
Target Time: 1500 Seconds

Results after 6 Million games:
+ Show Spoiler +

0:02.00: 50M 0G 0E 6/ 10S - Build Probe
0:19.00: 73M 0G 10E 7/ 10S - Build Probe
0:36.00: 106M 0G 19E 8/ 10S - Build Probe
0:44.10: 100M 0G 24E 9/ 10S - Build Pylon
0:54.19: 50M 0G 29E 9/ 10S - Build Probe
1:11.19: 107M 0G 39E 10/ 18S - Build Probe
1:28.19: 177M 0G 48E 11/ 18S - Build Probe
1:45.19: 258M 0G 58E 12/ 18S - Build Probe
2:07.39: 400M 0G 71E 13/ 18S - Build Nexus
2:13.20: 50M 0G 74E 13/ 18S - Build Probe
2:13.20: 0M 0G 74E 14/ 18S - Chrono Nexus
2:24.54: 97M 0G 55E 14/ 18S - Build Probe
2:37.20: 163M 0G 62E 15/ 18S - Build Probe
2:54.20: 291M 0G 72E 16/ 18S - Build Probe
3:08.49: 400M 0G 80E 17/ 18S - Build Nexus
3:17.69: 100M 0G 85E 17/ 18S - Build Pylon
3:22.43: 50M 0G 88E 17/ 18S - Build Probe
3:42.69: 227M 0G 99E 18/ 26S - Build Probe
3:42.69: 177M 0G 99E 19/ 26S - Chrono Nexus
3:42.69: 177M 0G 74E 19/ 26S - Build Assimilator
3:47.39: 157M 0G 77E 19/ 36S - Chrono Nexus
3:47.39: 157M 0G 52E 19/ 36S - Build Probe
3:54.03: 192M 0G 56E 20/ 36S - Build Probe
3:58.72: 203M 0G 58E 21/ 36S - Build Probe
4:02.69: 208M 0G 60E 22/ 36S - Chrono Nexus
4:05.36: 246M 0G 37E 22/ 36S - Build Probe
4:11.39: 285M 0G 40E 23/ 36S - Build Probe
4:16.69: 316M 0G 43E 24/ 36S - Build Probe
4:28.39: 457M 0G 50E 25/ 36S - Build Probe
4:28.39: 407M 0G 50E 26/ 36S - Move Probe To Gas
4:28.39: 407M 0G 50E 26/ 36S - Chrono Nexus
4:28.39: 407M 0G 25E 26/ 36S - Build Nexus
4:28.67: 11M 0G 25E 26/ 36S - Chrono Nexus
4:31.21: 50M 2G 1E 26/ 36S - Build Probe
4:39.72: 139M 8G 6E 27/ 36S - Build Probe
4:42.54: 136M 10G 8E 28/ 36S - Build Probe
4:48.49: 191M 14G 11E 29/ 46S - Build Probe
4:48.49: 141M 14G 11E 30/ 46S - Chrono Nexus
4:52.39: 210M 17G 13E 30/ 46S - Build Probe
4:56.48: 233M 20G 16E 31/ 46S - Build Probe
4:59.82: 246M 22G 18E 32/ 46S - Build Probe
5:09.39: 391M 29G 23E 33/ 46S - Build Probe
5:13.11: 419M 31G 25E 34/ 46S - Chrono Nexus
5:13.11: 419M 31G 0E 34/ 46S - Build Nexus
5:14.60: 50M 32G 1E 34/ 46S - Build Probe
5:16.90: 50M 34G 2E 35/ 46S - Build Probe
5:21.96: 112M 38G 5E 36/ 46S - Build Probe
5:31.60: 280M 44G 10E 37/ 46S - Build Probe
5:33.39: 271M 45G 11E 38/ 46S - Build Probe
5:33.90: 233M 46G 12E 39/ 46S - Build Probe
5:42.69: 400M 52G 17E 40/ 46S - Build Nexus
5:48.60: 148M 56G 20E 40/ 46S - Build Probe
5:50.39: 143M 57G 21E 41/ 46S - Build Probe
5:50.90: 106M 58G 21E 42/ 46S - Build Probe
6:03.69: 400M 67G 28E 43/ 46S - Build Nexus
6:05.60: 51M 68G 30E 43/ 46S - Build Probe
6:05.60: 1M 68G 30E 44/ 46S - Chrono Nexus
6:07.47: 50M 69G 31E 44/ 46S - Build Probe
6:09.33: 50M 71G 32E 45/ 56S - Build Probe
6:09.33: 0M 71G 32E 46/ 56S - Chrono Nexus
6:11.10: 50M 72G 33E 46/ 56S - Build Probe
6:16.94: 169M 76G 36E 47/ 56S - Build Probe
6:20.66: 229M 79G 38E 48/ 56S - Build Probe
6:24.47: 294M 81G 40E 49/ 56S - Build Probe
6:24.47: 244M 81G 40E 50/ 56S - Chrono Nexus
6:24.47: 244M 81G 15E 50/ 56S - Chrono Nexus
6:27.54: 339M 83G 17E 50/ 56S - Build Probe
6:28.27: 312M 84G 17E 51/ 56S - Build Probe
6:32.55: 400M 87G 20E 52/ 56S - Build Nexus
6:34.09: 50M 88G 21E 52/ 56S - Build Probe
6:35.80: 57M 89G 22E 53/ 56S - Build Probe
6:39.60: 136M 92G 24E 54/ 56S - Build Probe
6:44.54: 258M 95G 26E 55/ 56S - Build Probe
6:49.97: 400M 99G 29E 56/ 56S - Build Nexus
6:49.97: 0M 99G 29E 56/ 56S - Chrono Nexus
6:53.11: 112M 101G 31E 56/ 66S - Build Probe
6:53.11: 62M 101G 31E 57/ 66S - Build Probe
6:54.16: 50M 102G 32E 58/ 66S - Build Probe
6:55.54: 50M 103G 33E 59/ 66S - Build Probe
6:57.68: 79M 105G 34E 60/ 66S - Build Probe
7:09.01: 460M 112G 40E 61/ 66S - Build Probe
7:10.11: 452M 113G 41E 62/ 66S - Build Probe
7:10.11: 402M 113G 41E 63/ 66S - Build Probe
7:11.16: 393M 114G 41E 64/ 66S - Build Probe
7:12.54: 397M 115G 42E 65/ 66S - Build Probe
7:13.82: 400M 116G 43E 66/ 66S - Build Nexus
7:22.69: 370M 122G 48E 66/ 76S - Build Probe
7:22.69: 320M 122G 48E 67/ 76S - Chrono Nexus
7:25.54: 439M 124G 24E 67/ 76S - Build Probe
7:25.54: 389M 124G 24E 68/ 76S - Chrono Nexus
7:27.11: 455M 125G 25E 68/ 76S - Build Probe
7:27.11: 405M 125G 25E 69/ 76S - Build Probe
7:27.11: 355M 125G 25E 70/ 76S - Chrono Nexus
7:28.18: 400M 126G 26E 70/ 76S - Build Nexus
7:28.18: 0M 126G 26E 70/ 76S - Chrono Nexus
7:29.37: 50M 127G 27E 70/ 76S - Build Probe
7:30.51: 50M 127G 27E 71/ 76S - Build Probe
7:34.02: 157M 130G 29E 72/ 76S - Build Probe
7:36.87: 235M 132G 31E 73/ 76S - Build Probe
7:38.44: 257M 133G 32E 74/ 76S - Build Probe
7:38.44: 207M 133G 32E 75/ 76S - Build Pylon
7:38.80: 123M 133G 32E 75/ 76S - Build Probe
7:43.69: 300M 137G 35E 76/ 86S - Build Probe
7:43.69: 250M 137G 35E 77/ 86S - Chrono Nexus
7:46.37: 377M 139G 11E 77/ 86S - Build Probe
7:46.37: 327M 139G 11E 78/ 86S - Chrono Nexus
7:46.37: 327M 139G 11E 78/ 86S - Chrono Nexus
7:46.69: 342M 139G 11E 78/ 86S - Build Probe
7:47.51: 332M 139G 12E 79/ 86S - Build Probe
7:49.16: 361M 141G 13E 80/ 86S - Build Probe
7:50.13: 360M 141G 13E 81/ 86S - Build Probe
7:50.58: 332M 142G 14E 82/ 86S - Build Probe
7:55.02: 514M 145G 16E 83/ 86S - Build Probe
7:57.70: 605M 147G 18E 84/ 86S - Build Probe
8:01.47: 760M 149G 20E 85/ 86S - Build Probe
8:01.47: 710M 149G 20E 86/ 86S - Build Nexus
8:01.47: 310M 149G 20E 86/ 86S - Chrono Nexus
8:03.69: 431M 151G 21E 86/ 94S - Build Probe
8:04.51: 426M 151G 21E 87/ 94S - Build Probe
8:06.16: 467M 152G 22E 88/ 94S - Build Probe
8:06.16: 417M 152G 22E 89/ 94S - Build Gateway
8:06.36: 278M 153G 22E 89/ 94S - Build Probe
8:06.47: 234M 153G 23E 90/ 94S - Build Probe
8:10.37: 406M 155G 25E 91/ 94S - Build Probe
8:12.55: 482M 157G 26E 92/104S - Build Probe
8:12.55: 432M 157G 26E 93/104S - Chrono Nexus
8:16.02: 635M 159G 3E 93/104S - Build Probe
8:16.02: 585M 159G 3E 94/104S - Build Nexus
8:17.69: 282M 161G 4E 94/104S - Build Probe
8:20.69: 409M 163G 6E 95/104S - Build Probe
8:21.51: 409M 163G 6E 96/104S - Build Probe
8:23.16: 458M 164G 7E 97/104S - Build Probe
8:23.47: 426M 165G 7E 98/104S - Build Probe
8:23.86: 400M 165G 7E 99/104S - Build Nexus
8:25.09: 74M 166G 8E 99/104S - Build Probe
8:27.37: 166M 167G 9E 100/104S - Build Probe
8:27.37: 116M 167G 9E 101/104S - Build Pylon
8:29.02: 119M 168G 10E 101/104S - Build Probe
8:29.97: 128M 169G 11E 102/114S - Build Probe
8:33.02: 271M 171G 12E 103/114S - Build Probe
8:33.02: 221M 171G 12E 104/114S - Chrono Nexus
8:33.02: 221M 171G 12E 104/114S - Chrono Nexus
8:37.69: 521M 175G 15E 104/114S - Build Probe
8:38.51: 525M 175G 16E 105/114S - Build Probe
8:40.16: 584M 176G 16E 106/114S - Build Probe
8:40.47: 554M 176G 17E 107/114S - Build Probe
8:42.09: 612M 178G 18E 108/114S - Build Probe
8:42.32: 578M 178G 18E 109/114S - Build Probe
8:44.26: 661M 179G 19E 110/114S - Build Probe
8:44.35: 617M 179G 19E 111/114S - Build Probe
8:44.35: 567M 179G 19E 112/114S - Build Nexus
8:44.37: 168M 179G 19E 112/114S - Build Probe
8:53.82: 794M 186G 24E 113/132S - Build Probe
8:53.97: 755M 186G 24E 114/132S - Build Probe
8:53.97: 705M 186G 24E 115/132S - Chrono Nexus
8:54.69: 757M 186G 25E 115/132S - Build Probe
8:55.51: 767M 187G 25E 116/132S - Build Probe
8:57.02: 827M 188G 26E 117/132S - Build Probe
8:57.16: 788M 188G 26E 118/132S - Build Probe
8:57.47: 760M 188G 26E 119/132S - Build Probe
8:57.47: 710M 188G 26E 120/132S - Build Nexus
8:57.47: 310M 188G 26E 120/132S - Chrono Nexus
8:58.50: 387M 189G 2E 120/132S - Chrono Nexus
8:59.09: 430M 189G 2E 120/132S - Build Probe
9:01.26: 546M 191G 3E 121/132S - Build Probe
9:01.26: 496M 191G 3E 122/132S - Build Assimilator
9:01.26: 421M 191G 3E 122/132S - Build Assimilator
9:01.26: 346M 191G 3E 122/132S - Build Assimilator
9:01.26: 271M 191G 3E 122/132S - Build Assimilator
9:01.37: 204M 191G 3E 122/132S - Build Probe
9:01.37: 154M 191G 3E 123/132S - Build Assimilator
9:01.37: 79M 191G 3E 123/132S - Build Assimilator
9:02.35: 75M 192G 4E 123/132S - Build Assimilator
9:03.39: 75M 193G 5E 123/132S - Build Assimilator
9:05.30: 138M 194G 6E 123/132S - Build Probe
9:06.17: 155M 194G 6E 124/132S - Chrono Nexus
9:06.17: 155M 194G 6E 124/132S - Build Pylon
9:08.18: 211M 196G 7E 124/142S - Build Probe
9:08.80: 209M 196G 8E 125/142S - Build Probe
9:08.94: 171M 196G 8E 126/142S - Build Probe
9:10.82: 267M 198G 9E 127/142S - Build Probe
9:11.69: 286M 198G 9E 128/142S - Build Probe
9:11.69: 236M 198G 9E 129/142S - Build Cybernetics Core
9:12.51: 151M 199G 10E 129/142S - Build Probe
9:15.16: 314M 201G 11E 130/142S - Chrono Nexus
9:15.16: 314M 201G 11E 130/142S - Build Probe
9:15.16: 264M 201G 11E 131/142S - Build Probe
9:16.09: 290M 201G 12E 132/142S - Build Probe
9:16.63: 285M 202G 12E 133/142S - Build Probe
9:18.26: 373M 203G 13E 134/142S - Build Probe
9:18.26: 323M 203G 13E 135/142S - Build Assimilator
9:21.16: 494M 205G 15E 135/142S - Build Probe
9:21.47: 470M 205G 15E 136/142S - Build Probe
9:24.73: 706M 207G 17E 137/142S - Build Probe
9:25.18: 696M 208G 17E 138/142S - Build Probe
9:27.82: 881M 210G 18E 139/142S - Build Probe
9:28.69: 910M 210G 19E 140/142S - Build Probe
9:28.86: 876M 210G 19E 141/142S - Build Probe
9:32.16: 1129M 213G 21E 142/150S - Build Probe
9:32.16: 1079M 213G 21E 143/150S - Build Probe
9:33.09: 1115M 213G 21E 144/150S - Build Probe
9:35.26: 1270M 215G 22E 145/150S - Build Probe
9:36.51: 1339M 216G 23E 146/150S - Build Probe
9:38.16: 1447M 217G 24E 147/150S - Build Probe
9:38.47: 1426M 217G 24E 148/150S - Build Probe
9:41.47: 1667M 219G 26E 149/160S - Build Probe
9:42.18: 1687M 220G 26E 150/160S - Build Probe
9:44.82: 1896M 221G 28E 151/160S - Build Probe
9:44.82: 1846M 221G 28E 152/160S - Build Assimilator
9:45.69: 1856M 222G 28E 152/160S - Build Probe
9:45.86: 1823M 222G 28E 153/160S - Build Probe
9:49.16: 2100M 225G 30E 154/160S - Build Probe
9:49.16: 2050M 225G 30E 155/160S - Build Probe
9:49.16: 2000M 225G 30E 156/160S - Build Assimilator
9:49.16: 1925M 225G 30E 156/160S - Build Assimilator
9:49.16: 1850M 225G 30E 156/160S - Build Assimilator
9:50.09: 1866M 225G 31E 156/160S - Build Probe
9:52.26: 2033M 227G 32E 157/160S - Build Probe
9:52.26: 1983M 227G 32E 158/160S - Build Assimilator
9:53.51: 2034M 228G 33E 158/160S - Build Probe
9:53.51: 1984M 228G 33E 159/160S - Build Assimilator
9:55.16: 2078M 229G 34E 159/160S - Build Probe
9:55.16: 2028M 229G 34E 160/160S - Build Assimilator
9:56.02: 2040M 229G 34E 160/170S - Build Probe
9:56.02: 1990M 229G 34E 161/170S - Build Assimilator
9:56.02: 1915M 229G 34E 161/170S - Build Assimilator
9:56.02: 1840M 229G 34E 161/170S - Build Assimilator
9:56.02: 1765M 229G 34E 161/170S - Build Assimilator
9:56.02: 1690M 229G 34E 161/170S - Build Probe
9:58.47: 1887M 231G 36E 162/170S - Build Probe
9:59.18: 1909M 232G 36E 163/170S - Build Probe
10:01.82: 2137M 233G 37E 164/170S - Build Probe
10:02.69: 2181M 234G 38E 165/170S - Build Probe
10:02.86: 2150M 234G 38E 166/170S - Build Probe
10:02.86: 2100M 234G 38E 167/170S - Build Pylon
10:03.86: 2105M 235G 39E 167/180S - Build Probe
10:06.16: 2304M 236G 40E 168/180S - Build Probe
10:06.16: 2254M 236G 40E 169/180S - Build Probe
10:06.16: 2204M 236G 40E 170/180S - Build Assimilator
10:06.16: 2129M 236G 40E 170/180S - Build Assimilator
10:06.16: 2054M 236G 40E 170/180S - Build Assimilator
10:06.16: 1979M 236G 40E 170/180S - Build Assimilator
10:06.16: 1904M 236G 40E 170/180S - Build Assimilator
10:07.09: 1926M 237G 40E 170/180S - Build Probe
10:09.26: 2105M 239G 42E 171/180S - Build Probe
10:10.51: 2190M 239G 42E 172/180S - Build Probe
10:12.16: 2324M 241G 43E 173/180S - Build Probe
10:13.02: 2369M 241G 44E 174/180S - Build Probe
10:13.02: 2319M 241G 44E 175/180S - Build Probe
10:15.47: 2547M 243G 45E 176/180S - Build Probe
10:15.47: 2497M 243G 45E 177/180S - Chrono Nexus
10:15.47: 2497M 243G 20E 177/180S - Chrono Nexus
10:16.18: 2580M 243G 20E 177/180S - Build Probe
10:18.82: 2835M 245G 22E 178/180S - Build Probe
10:19.69: 2886M 246G 22E 179/180S - Build Probe
10:24.35: 3388M 249G 25E 180/190S - Build Probe
10:24.35: 3338M 249G 25E 181/190S - Build Probe
10:24.35: 3288M 249G 25E 182/190S - Build Probe
10:24.35: 3238M 249G 25E 183/190S - Build Probe
10:24.35: 3188M 249G 25E 184/190S - Build Pylon
10:24.35: 3088M 249G 25E 184/190S - Build Probe
10:24.35: 3038M 249G 25E 185/190S - Build Assimilator
10:24.35: 2963M 249G 25E 185/190S - Build Assimilator
10:24.35: 2888M 249G 25E 185/190S - Build Probe
10:24.35: 2838M 249G 25E 186/190S - Build Stargate
10:25.17: 2783M 100G 26E 186/190S - Build Probe
10:26.26: 2862M 101G 26E 187/190S - Build Probe
10:26.80: 2876M 101G 26E 188/190S - Build Probe
10:27.51: 2910M 101G 27E 189/190S - Build Probe
10:29.16: 3059M 103G 28E 190/198S - Build Probe
10:30.02: 3114M 103G 28E 191/198S - Build Probe
12:48.39: 21851M 200G 100E 192/200S - Build Fleet Beacon
22:19.82: 99744M 400G 100E 192/200S - Build Mothership
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas
22:19.82: 99344M 0G 100E 200/200S - Move Probe To Gas

Waypoint 1 failed:
24:59.82: 116080M 4435G 100E 200/200S
Income: 6276M 1663G
Buildings: 16 Nexus 28 Assimilator 7 Pylon 1 Gateway 1 Cybernetics Core 1 Stargate 1 Fleet Beacon
Units: 192 Probe 1 Mothership
Upgrades:

boberto

7 Posts

November 22 2010 20:48 GMT

#397

On November 22 2010 23:45 Conti wrote:
(Edit: Eh, just found out that you can only build one Mothership at a time. You learn something new every day! Still curious what the heck the program is trying to do in this case, though.)

I just found a rather curious bug. Or at least I think it's one. Anyone ever tried to get it to build 2 Motherships? If I tell it to build one it almost immediately gets an acceptable time (< 8 min.) and improves from there. If I tell it to build two.. it builds Probes until it's almost maxed out and then builds one Mothership right before the Target Time. And all the time there's only one Probe on gas. I'm on a laptop right now, so I only got 6 million games so far, but there's no sign of improvement whatsoever.

Target: 2 Motherships
Target Time: 1500 Seconds

Results after 6 Million games:
+ Show Spoiler +

6 million games is really nothing... I only start making conclusions about a build when I reach 100 million, but I know further refinements happen up into the billions of games.

AcTiVillain

Australia81 Posts

November 22 2010 23:46 GMT

#398

How many lines of code is your genetic algorithm =P

Careful mate, don't give yourself RSI.

I'd imagine modding this for Terran is fairly simple, except with the Addon mechanic. hnnmmm

CarbonTwelve

Australia525 Posts

November 23 2010 02:32 GMT

#399

On November 23 2010 08:46 AcTiVillain wrote:
How many lines of code is your genetic algorithm =P

The GA part itself I'm not sure, probably 1,000 or so. The entire app though would be close to 10,000 I think.

Careful mate, don't give yourself RSI.

Given coding is my job, hopefully won't happen

I think I'm more likely to get RSI from the practice I've been doing trying to learn Zerg macro...

I'd imagine modding this for Terran is fairly simple, except with the Addon mechanic. hnnmmm

Yeah, addon swapping will be the worst part of it. Not so much for the coding aspect, but I think the algorithm will struggle to get build orders doing it well. Won't know for sure until I actually code it & test it though.

CarbonTwelve

Australia525 Posts

November 23 2010 09:32 GMT

#400

New release time! And this one's a big one (hence why it's been a few days): Zerg module is ready!

v6 changelog:
Zerg module!
Known issues:
Constant drone production doesn't do anything
Multiple queens spawning larvae on same hatchery
Larvae not split per hatchery
Creep tumors aren't working
Various inefficiencies in Zerg code

I expect there'll still be other bugs with the Zerg module, so if it's not mentioned above, please let me know, and also be gentle on me - bit of a quick release for this stuff.

Plan for next release will be to fix up the above known issues, then probably to work on the custom non-target priorities (minerals vs gas vs workers etc.). After that I'll probably start work on the Terran version (likely v8).

Prev 1 18 19 20 21 22 76 Next

Please or register to reply.

SCFusion - WoL, HotS & LotV Build Order Optimizer - Page 20

Completed

Ongoing

Upcoming