Rule tree that crashes golly (atleast on ipad)

[danieldb]

Code: Select all

@RULE crashlife

@TREE

num_states=2
num_neighbors=8
num_nodes=32
1 0 0
2 0 0
1 0 1
2 0 2
3 1 3
1 1 1
2 2 5
3 3 6
4 4 7
2 5 0
3 6 9
4 7 10
5 8 11
3 9 1
4 10 13
5 11 14
6 12 15
3 1 16
4 13 17
5 14 18
6 15 19
7 16 20
4 17 17
5 18 22
6 19 23
7 20 24
8 21 25
5 22 22
6 23 27
7 24 28
8 25 29
9 26 30

Run r pentomino for 4 generations.

Why does this happen?

[gmc_nxtman]

Please post the rule in a non-tree form, so it's easier to diagnose the problem.

It seems as though it's likely that there are there are two mutually annihilating transitions (and this has happened to me before), however I haven't investigated the code to know if it's a different problem.

[Andrew]

Why does this happen?

Dunno. How did you create the tree data? I'm assuming you didn't just type it in, so please supply the Python/C++/Java code that generated the tree data. Thanks.

[danieldb]

It's a modified version of life. The 18th node was 3 1 1, and I changed it to 3 1 16

[Andrew]

It's a modified version of life. The 18th node was 3 1 1, and I changed it to 3 1 16

It would've saved time if you'd mentioned that in your 1st post!

The tree data is not meant to be edited. It's created by a high-level program (see the examples supplied in Rules/TreeGenerators) or by a Python transition function passed via the clipboard to the make-ruletree.py script in Scripts/Python/Rule-Generators.

Having said that, it's not ideal that Golly crashes if the tree data is bad. I'll mention this to Tom and see if it's practical to do some sort of sanity checking when the rule is 1st loaded.

[rokicki]

I've checked in a change that properly rejects that file.

Every node at levels > 1 must point to nodes one level down.
This is now enforced.

Let me know if there are any questions.