## CCC '16 S5 - Circle of Life

View as PDF

Points: 20 (partial)
Time limit: 2.0s
Memory limit: 128M

Author:
Problem type
Allowed languages
Ada, Assembly, Awk, Brain****, C, C#, C++, COBOL, CommonLisp, D, Dart, F#, Forth, Fortran, Go, Groovy, Haskell, Intercal, Java, JS, Kotlin, Lisp, Lua, Nim, ObjC, OCaml, Octave, Pascal, Perl, PHP, Pike, Prolog, Python, Racket, Ruby, Rust, Scala, Scheme, Sed, Swift, TCL, Text, Turing, VB, Zig
##### Canadian Computing Competition: 2016 Stage 1, Senior #5

You may have heard of Conway's Game of Life, which is a simple set of rules for cells on a grid that can produce incredibly complex configurations. In this problem we will deal with a simplified version of the game.

There is a one-dimensional circular strip of cells. The cells are numbered from to in the order you would expect: that is, cell and cell are adjacent, cell and cell are adjacent, and so on up to cell , which is adjacent to cell . Since the trip is circular, cell is also adjacent to cell .

Each cell is either alive (represented by a 1) or dead (represented by a 0). The cells change over a number of generations. If exactly one of the cell's neighbours is alive in the current generation, then the cell will be alive in the next generation. Otherwise, the cell will be dead in the next generation.

Given the initial state of the strip, find the state after generations.

#### Input Specification

The first line will contain two space-separated integers and (). The second line will contain a string consisting of exactly characters, representing the initial configuration of the cells. Each character in the string will be either 0 or 1. The initial state of cell is given by the character of the string. The character 1 represents an alive cell and the character 0 represents a dead cell.

• For 1 of the 15 available marks, and .
• For an additional 6 of the 15 available marks, .
• For an additional 4 of the 15 available marks, and .

Note that for full marks, solutions will need to handle 64-bit integers. For example:

• in C/C++, the type long long should be used;
• in Java, the type long should be used;
• in Pascal, the type int64 should be used.

#### Output Specification

Output the string of characters representing the final state of the cells, in the same format and order as the input.

#### Sample Input 1

7 1
0000001

#### Output for Sample Input 1

1000010

#### Explanation for Output for Sample Input 1

Cell and cell are adjacent to cell , and thus alive after one generation.

#### Sample Input 2

5 3
01011

#### Output for Sample Input 2

10100

#### Explanation for Output for Sample Input 2

After one generation, configuration becomes 00011.

After two generations, configuration becomes 10111.

• commented on Nov. 22, 2020, 12:51 a.m. edit 2

I'm TLE'ing on Case 3 of Batch 6. My Java solution should implement in O(N log T) time. Does anyone have any suggestions?

Edit: Never mind, I fixed by using character array instead of string manip

• commented on July 10, 2020, 1:57 a.m.

Wow this problem is very elegant.

• commented on April 16, 2020, 12:39 p.m.

This comment is hidden due to too much negative feedback. Click here to view it.

• commented on April 16, 2020, 4:07 p.m. edit 2

I'd suggest you take a look on the upper bounds of and . If we're generous, and assume that DMOJ judges can run ~1e8 operations per second for Python 3, and your algorithm is , then we can ballpark your algorithm to run for approximately seconds years. In that time, we will:

• most likely have upgraded to better judges at some point
• possibly find a conclusion for
• probably find a theory for quantum gravity
• witness the 31st nuclear winter
• u͏n̴̹͕l̺̹̯͚e͘a̤̻̭͎̞ͅs͏̪̟h͖͚͖͕ ̮̥͚t͎h͔̦̼͍͓͚͙e̙̺̞͍̗͈ͅ ̭k̻̕r͔̥͉̗̦a̸̼͚k͕̩̥̦e̯͖ņ̤͖
• likely have achieved AI supremacy
• probably all died out from said AI supremacy

TL;DR: is a very big number. Can you think of a way to greatly reduce this number down? (A starting place might be to think of cycles.)

If you're still struggling, the editorial exists :blobthumbsup: (but not for you to copy and gain free points).

• commented on April 16, 2020, 4:09 p.m.

:richard:

• commented on April 16, 2020, 4:19 p.m.

This comment is hidden due to too much negative feedback. Click here to view it.

• commented on April 16, 2020, 5:35 p.m.

This comment is hidden due to too much negative feedback. Click here to view it.

• commented on Jan. 11, 2020, 8:21 p.m. edited

I'm getting WA on the 2nd test case, is there something basic I'm missing? Currently, my algorithm copies values to a new array, XOR's adjacent values in the old array and repeats.

• commented on June 26, 2019, 7:22 p.m.

Getting TLE for batch 4-6 any tips or general directions to look into. A bit stuck here.

• commented on July 1, 2019, 8:19 a.m.

Remember that can be very large, look at the editorial for a faster algorithm

• commented on Dec. 23, 2017, 12:47 p.m.

This comment is hidden due to too much negative feedback. Click here to view it.

• commented on Nov. 22, 2020, 7:53 p.m.

how to get away with murder

• commented on Dec. 23, 2017, 1:30 p.m. edited

I'm pretty sure this is what they call asking for a ban.

Edit: How did that banhammer taste?

• commented on Dec. 23, 2017, 1:59 p.m.

That is correct.

• commented on Feb. 9, 2017, 6:52 p.m. edited

This is a reminder that copy-pasting the editorial submission is neither approved, nor is it a learning opportunity. As such, anyone who has copy-pasted the editorial will:

1. Be banned from the problem.
2. Have their submission replaced with a cheeky message.
3. Have their points removed. ­
• commented on Feb. 23, 2016, 4:16 p.m.

I got WA on the second last test case... but the same code AC'd

• commented on Feb. 23, 2016, 4:29 p.m. edited

This is likely due to the floating-point precision errors caused by different behavior of the function log on different judges.

• commented on Feb. 23, 2016, 4:34 p.m.

I'm getting WA on wcipeg

• commented on Feb. 23, 2016, 4:35 p.m.

Try writing your own log function.

• commented on Feb. 23, 2016, 4:36 p.m.

Thanks, that worked!

• commented on Feb. 21, 2016, 4:37 p.m.

What does Invalid Return mean? I guess my algorithm isn't just outputting a wrong answer but something else entirely?

• commented on Feb. 21, 2016, 4:51 p.m.

likely, you are going over the python recursion depth limit ( times is too much)

here is a link to stackoverflow

• commented on Feb. 21, 2016, 4:46 p.m.

This comment is hidden due to too much negative feedback. Click here to view it.