|
|
#1 |
![]() Join Date: Jun 2011
Reputation: 4
Posts: 78
|
Reducing Number of Cycles?
My question is "How can i reduce cycles?" , because i don't know which the number of cycles depends on. :S
Ps: I hope you can understand me, because my english isn't good. :S |
|
|
|
|
|
#2 |
![]() Join Date: Feb 2010
Reputation: 561
Posts: 8,143
|
All the actions produce cycles. A waldo moves? Cycles. A waldo comes over an action icon? More cycles. Reduce the amount of movement and actions.
|
|
|
|
|
|
#3 |
![]() Join Date: Jun 2011
Reputation: 4
Posts: 78
|
But i reduced the way a waldo moves and the number of cycles is the same
|
|
|
|
|
|
#4 |
![]() Join Date: May 2011
Reputation: 5
Posts: 85
|
Well I think the explanation above is wrong, the cycles clearly depends on time and nothing more, so let's break it down: on the lowest speed 1 cycle equals 1 second. In 1 second a waldo moves exactly one square, or performs one rotate. (Thats the only action consuming a "cycle", while staying on the same square, whereas all other actions are instantly finished, except syncs ofcourse and maybe input/output in production levels when the input line is empty or the output line clogged.)
So if you want to reduce your cycles you have to produce the output quicker, it doesn't matter how many actions you are using, as long they help you to finish your task faster. |
|
|
|
|
|
#5 |
![]() Join Date: Oct 2008
Reputation: 45
Posts: 486
|
Cycles = time. Simple as.
Keep in mind that if your solution has a bottleneck (e.g. one slow reactor in a production assignment, or a research assignment with one waldo path longer than the other and a sync command on both), then optimising anything other than the bottleneck will have no effect on the number of cycles - the thing you've optimised will just spend more time waiting. |
|
|
|
|
|
#6 |
![]() Join Date: Apr 2011
Reputation: 5992
Posts: 348
|
Make your loops as small as possible. Keep everything tight.
|
|
|
|
|
|
#7 |
![]() Join Date: May 2010
Reputation: 54
Posts: 386
|
|
|
|
|
|
|
#8 |
![]() Join Date: May 2010
Reputation: 351
Posts: 1,548
|
Spot on.
Also, notice when you set your machine in motion, there's a count in the bottom right of the screen telling you how many 'cycles' have elapsed. Basically 'cycles' is just the unit of time used for this game. So statements like, "Waldos move at 1 tile per cycle" make sense. |
|
|
|
![]() |
|
||||||
| Thread Tools | |
| Display Modes | |
|
|