Not the first time anyone's done that -- but all it allows others to do is submit results in his name, so it's hardly a big deal, is it.Majestas32 wrote:You do realized you just revealed your payosha256 key right danny?
apgsearch v4.0
- Apple Bottom
- Posts: 1034
- Joined: July 27th, 2015, 2:06 pm
- Contact:
Re: apgsearch v4.0
If you speak, your speech must be better than your silence would have been. — Arabian proverb
Catagolue: Apple Bottom • Life Wiki: Apple Bottom • Twitter: @_AppleBottom_
Proud member of the Pattern Raiders!
Catagolue: Apple Bottom • Life Wiki: Apple Bottom • Twitter: @_AppleBottom_
Proud member of the Pattern Raiders!
Re: apgsearch v4.0
The linear growth pattern in that yl82 (which also contains a lot of chaos) is this:muzik wrote: EDIT: A third time as well. Can that yl82 be rescued from its apgcode?
(yl82_1_13_442e9e06ce8ff98bb88fbf07d6b84fd0)
Code: Select all
x = 9, y = 6, rule = B026/S1
7bo$8bo$5bo$6bo$3bo$o3bo!
Re: apgsearch v4.0
FALSEHOOD! It is actually a p41 gun:77topaz wrote:The linear growth pattern in that yl82 (which also contains a lot of chaos) is this:
Code: Select all
x = 13, y = 17, rule = R2,C0,M1,S10..19,B4..4,NM
6b2o2bo$5bo$7b3o2bo$3bo3b3o2bo$2bo2b6obo$bo2b2ob2o3bo$3bo3bob2o$ob9o$
2b3o2bob3o$ob9o$3bo3bob2o$bo2b2ob2o3bo$2bo2b6obo$3bo3b3o2bo$7b3o2bo$5b
o$6b2o2bo!
Re: apgsearch v4.0
To be fair, you can claim the key by submitting it as your own key as I did back in the day with WWei, so that all their hauls are submitted in your name.Apple Bottom wrote:Not the first time anyone's done that -- but all it allows others to do is submit results in his name, so it's hardly a big deal, is it.Majestas32 wrote:You do realized you just revealed your payosha256 key right danny?
Re: apgsearch v4.0
which is why i switchedRhombic wrote: To be fair, you can claim the key by submitting it as your own key as I did back in the day with WWei, so that all their hauls are submitted in your name.
Re: apgsearch v4.0
Oops, my bad. Several of the soups/errors Muzik was referring to in that conversation originated from B026/S1, so I thought that apgcode was also referring to a pattern in that rule, and in B026/S1 said apgcode did indeed produce a linear growth pattern along with a lot of replicator-y chaos which apgsearch would struggle with. I should've realised it would be weird for a p16 rake to be tagged as p82.danny wrote:FALSEHOOD! It is actually a p41 gun:Code: Select all
x = 13, y = 17, rule = R2,C0,M1,S10..19,B4..4,NM 6b2o2bo$5bo$7b3o2bo$3bo3b3o2bo$2bo2b6obo$bo2b2ob2o3bo$3bo3bob2o$ob9o$ 2b3o2bob3o$ob9o$3bo3bob2o$bo2b2ob2o3bo$2bo2b6obo$3bo3b3o2bo$7b3o2bo$5b o$6b2o2bo!
Re: apgsearch v4.0
I recently started running apgmera v3.28 again after many months idle. It's generally running with 2-8 threads depending on what else I'm doing.
For b3s23/C1 is there an advantage to running v4? Is it faster or better?
For b3s23/C1 is there an advantage to running v4? Is it faster or better?
- Apple Bottom
- Posts: 1034
- Joined: July 27th, 2015, 2:06 pm
- Contact:
Re: apgsearch v4.0
v4 has a couple of improvements, at least some of which should also translate to faster performance, but in my experience it's actually a bit slower for B3/S23/C1. And there's been some issues with sample soups not generating the objects they were reported to, unaddressed so far, so my personal (!) recommendation is to stick with 3.28 for the time being -- for Conway Life anyway.tod222 wrote:I recently started running apgmera v3.28 again after many months idle. It's generally running with 2-8 threads depending on what else I'm doing.
For b3s23/C1 is there an advantage to running v4? Is it faster or better?
If you speak, your speech must be better than your silence would have been. — Arabian proverb
Catagolue: Apple Bottom • Life Wiki: Apple Bottom • Twitter: @_AppleBottom_
Proud member of the Pattern Raiders!
Catagolue: Apple Bottom • Life Wiki: Apple Bottom • Twitter: @_AppleBottom_
Proud member of the Pattern Raiders!
Re: apgsearch v4.0
My apgsearch has suddenly stopped working properly:
When I try to search b3s23/C1, I get this error message:
For another rule (b2ci3ae4ety5ciy678s2cek3-aij4-w5cejry6-e78/C1), I get this:
Yet b36is234j/C1 searches normally, without any errors.
When I try to search b3s23/C1, I get this error message:
Code: Select all
Traceback (most recent call last):
File "lifelib/avxlife/rule2asm.py", line 939, in <module>
main()
File "lifelib/avxlife/rule2asm.py", line 853, in main
makeasm(rulestring)
File "lifelib/avxlife/rule2asm.py", line 784, in makeasm
ix.genlogic(logstring)
File "lifelib/avxlife/rule2asm.py", line 234, in genlogic
for i in xrange(8):
NameError: name 'xrange' is not defined
Code: Select all
Configuring rule b2ci3ae4ety5ciy678s2cek3-aij4-w5cejry6-e78; symmetry C1
Traceback (most recent call last):
File "ntcanon.py", line 34, in <module>
for i in xrange(512):
NameError: name 'xrange' is not defined
Valid symmetry: C1
Success!
g++ -c -Wall -O3 -march=native --std=c++11 main.cpp -o main.o
In file included from main.cpp:16:
In file included from ./lifelib/upattern.h:3:
./lifelib/avxlife/uli.h:5:10: fatal error: 'lifelogic/iterators_all.h' file not found
#include "lifelogic/iterators_all.h"
^~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
make: *** [main.o] Error 1
- Apple Bottom
- Posts: 1034
- Joined: July 27th, 2015, 2:06 pm
- Contact:
Re: apgsearch v4.0
You seem to be having a problem with your Python installation. What OS are you on? Did you recently update your packages, install a new system, or something else along those lines?77topaz wrote:My apgsearch has suddenly stopped working properly:
If you speak, your speech must be better than your silence would have been. — Arabian proverb
Catagolue: Apple Bottom • Life Wiki: Apple Bottom • Twitter: @_AppleBottom_
Proud member of the Pattern Raiders!
Catagolue: Apple Bottom • Life Wiki: Apple Bottom • Twitter: @_AppleBottom_
Proud member of the Pattern Raiders!
Re: apgsearch v4.0
Specifically, since xrange() is available in Python 2.x but not in Python 3.x, a superficially plausible theory is that your system is now trying to run apgsearch with Python 3.x (for whatever reason).Apple Bottom wrote:You seem to be having a problem with your Python installation. What OS are you on? Did you recently update your packages, install a new system, or something else along those lines?77topaz wrote:My apgsearch has suddenly stopped working properly:
Re: apgsearch v4.0
I recently installed Anaconda for one of my university classes, which I think includes Python 3.x, but apgsearch still says it's running Python 2.7.10 (which is the computer's built-in version of Python). How could I fix this problem?dvgrn wrote:Specifically, since xrange() is available in Python 2.x but not in Python 3.x, a superficially plausible theory is that your system is now trying to run apgsearch with Python 3.x (for whatever reason).
Re: apgsearch v4.0
Yikes, no idea. I mean, theoretically you could rewrite ntcanon.py to be Python 3 compatible, but that's a really lousy idea since you'd probably have to do the same thing for rule2asm.py, etc...77topaz wrote:I recently installed Anaconda for one of my university classes, which I think includes Python 3.x, but apgsearch still says it's running Python 2.7.10 (which is the computer's built-in version of Python). How could I fix this problem?dvgrn wrote:Specifically, since xrange() is available in Python 2.x but not in Python 3.x, a superficially plausible theory is that your system is now trying to run apgsearch with Python 3.x (for whatever reason).
Maybe the place to start is to prove that the problem really is that this line in rule2asm.py, which is clearly running in Python 2.x (it's full of xranges also) --
Code: Select all
status = os.system('python ntcanon.py "%s"' % rulestring)
Code: Select all
print(sys.version)
I'm assuming that this will in fact report Python 3.x... which basically means that your Anaconda installation (or something since then) has modified the PATH variable on your system, such that the path to Python 3.x now comes before the path to Python 2.x.
Or something like that. I probably have the details wrong, and I'm not particularly good at fixing this kind of multi-Python mess anyway.
I'm guessing if you renamed your Python 3 executable temporarily, apgluxe would stop throwing those errors. So that's another thing you could try --!
Re: apgsearch v4.0
The print(sys.version) thing doesn't work, because the "sys" itself creates an error:
Note that when I run b36is234j/C1, it still says this:
EDIT: When I open a new console window and type "python --version", it returns this:
Code: Select all
Configuring rule b2ci3ae4ety5ciy678s2cek3-aij4-w5cejry6-e78; symmetry C1
Traceback (most recent call last):
File "ntcanon.py", line 4, in <module>
print(sys.version)
NameError: name 'sys' is not defined
Valid symmetry: C1
Success!
g++ -c -Wall -O3 -march=native --std=c++11 main.cpp -o main.o
In file included from main.cpp:16:
In file included from ./lifelib/upattern.h:3:
./lifelib/avxlife/uli.h:5:10: fatal error: 'lifelogic/iterators_all.h' file not found
#include "lifelogic/iterators_all.h"
^~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
make: *** [main.o] Error 1
Code: Select all
Lifelib version: ll1.23
Compiler version: 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.39.2)
Python version: '2.7.10 (default, Jul 30 2016, 19:40:32) [GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.34)]'
Code: Select all
Python 3.6.4 :: Anaconda, Inc.
Re: apgsearch v4.0
Sorry, yeah, add another line "import sys" just before the print line, to take care of that.77topaz wrote:The print(sys.version) thing doesn't work, because the "sys" itself creates an error...
That's all definitely consistent with the theory that -- for some reason -- running Python from inside Python gets hold of a %PATH% variable (or Mac equivalent, I don't know the details) that points to Python 3.6.4, whereas the console window where you're running recompile.sh -- for some reason -- is accessing a version of %PATH% that doesn't know about the Anaconda Python.77topaz wrote:Note that when I run b36is234j/C1, it still says this:EDIT: When I open a new console window and type "python --version", it returns this:Code: Select all
Lifelib version: ll1.23 Compiler version: 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.39.2) Python version: '2.7.10 (default, Jul 30 2016, 19:40:32) [GCC 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.34)]'
Code: Select all
Python 3.6.4 :: Anaconda, Inc.
I suspect your easiest solution may be to modify the lifelib/avxlife/rule2asm.py line to say specifically
Code: Select all
status = os.system("/specific/path/to/python ntcanon.py "%s"' % rulestring)
Re: apgsearch v4.0
I think I found the correct directory for Python 2.7, so I changed the line to this:dvgrn wrote:-- you figure out where exactly your 2.7.10 Python is located, and edit the above to point to that path.
Code: Select all
status = os.system('/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 ntcanon.py "%s"' % rulestring)
Code: Select all
Configuring rule b2ci3ae4ety5ciy678s2cek3-aij4-w5cejry6-e78; symmetry C1
sh: /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7: is a directory
Valid symmetry: C1
Success!
g++ -c -Wall -O3 -march=native --std=c++11 main.cpp -o main.o
In file included from main.cpp:16:
In file included from ./lifelib/upattern.h:3:
./lifelib/avxlife/uli.h:5:10: fatal error: 'lifelogic/iterators_all.h' file not found
#include "lifelogic/iterators_all.h"
^~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
make: *** [main.o] Error 1
Re: apgsearch v4.0
The error is trying to tell you exactly what the problem is. The original line started with "python", which is an executable file not a directory. You probably just need77topaz wrote:Configuring rule b2ci3ae4ety5ciy678s2cek3-aij4-w5cejry6-e78; symmetry C1
sh: /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7: is a directory...
Code: Select all
status = os.system('/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/python ntcanon.py "%s"' % rulestring)
Re: apgsearch v4.0
There is no file just called "python", though, and trying exactly the line you wrote gave me "No such file or directory". There is, however, a file named Python.h, but trying that doesn't work either, as I get "Permission denied":dvgrn wrote:The error is trying to tell you exactly what the problem is. The original line started with "python", which is an executable file not a directory. You probably just need
Code: Select all
status = os.system('/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/python ntcanon.py "%s"' % rulestring)
Code: Select all
Configuring rule b2ci3ae4ety5ciy678s2cek3-aij4-w5cejry6-e78; symmetry C1
sh: /Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7/Python.h: Permission denied
Valid symmetry: C1
Success!
g++ -c -Wall -O3 -march=native --std=c++11 main.cpp -o main.o
In file included from main.cpp:16:
In file included from ./lifelib/upattern.h:3:
./lifelib/avxlife/uli.h:5:10: fatal error: 'lifelogic/iterators_all.h' file not found
#include "lifelogic/iterators_all.h"
^~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
make: *** [main.o] Error 1
Re: apgsearch v4.0
Yeah, you've dug way down into source code somewhere. Try looking elsewhere.77topaz wrote:There is no file just called "python", though, and trying exactly the line you wrote gave me "No such file or directory". There is, however, a file named Python.h, but trying that doesn't work either...
Here's a suggestion from StackOverflow: try running in a console window
type -a python
or possibly
which Python
...?
Re: apgsearch v4.0
The first search gave two results: the Python file from Anaconda, plus another one at "/usr/bin/python", a directory which I didn't even know existed (though it's mentioned in the very first line of rule2asm.py). The second one gave only the Anaconda one. So, I changed the line in rule2asm.py to:dvgrn wrote:Yeah, you've dug way down into source code somewhere. Try looking elsewhere.
Here's a suggestion from StackOverflow: try running in a console window
type -a python
or possibly
which Python
...?
Code: Select all
status = os.system('/usr/bin/python ntcanon.py "%s"' % rulestring)
Code: Select all
Configuring rule b2ci3ae4ety5ciy678s2cek3-aij4-w5cejry6-e78; symmetry C1
Compressing 512-bit lookup table for rule b2ci3ae4ety5ciy678s2cek3-aij4-w5cejry6-e78...
Creating magic sauce for rule b2ci3ae4ety5ciy678s2cek3-aij4-w5cejry6-e78...
...completed.
Traceback (most recent call last):
File "lifelib/avxlife/rule2asm.py", line 939, in <module>
main()
File "lifelib/avxlife/rule2asm.py", line 905, in main
for hist in xrange(3):
NameError: name 'xrange' is not defined
Re: apgsearch v4.0
Okay, that is fairly strange. Whereas before your system seemed to be successfully running rule2asm.py, now it's acting as if it's trying to use your Anaconda Python 3 to run that file as well. That's pretty mysterious behavior, as if Anaconda is very gradually taking over your computer.77topaz wrote:Traceback (most recent call last):
File "lifelib/avxlife/rule2asm.py", line 939, in <module>
main()
File "lifelib/avxlife/rule2asm.py", line 905, in main
for hist in xrange(3):
NameError: name 'xrange' is not defined
[/code]
Theoretically the solution is the same as before. This time, edit lines 60 and 61 in recompile.sh --
Code: Select all
python lifelib/avxlife/rule2asm.py $rulearg
python mkparams.py $rulearg $symmarg
Code: Select all
/usr/bin/python lifelib/avxlife/rule2asm.py $rulearg
/usr/bin/python mkparams.py $rulearg $symmarg
Re: apgsearch v4.0
Okay, I changed those lines in recompile.sh, and it works normally now! Thank you very much for your help!
- 2718281828
- Posts: 738
- Joined: August 8th, 2017, 5:38 pm
Re: apgsearch v4.0
I am not sure if this suggestion should go to the catagolue discussion thread or here.
I would like that apgsearch does not only allow 2^N x 2^(8-N)
1x256
2x128
4x64
8x32
I would like to run the other numbers as well (at least up to 7), i.e.
3x85
5x51
6x42
7x36
9x28
10x25
11x23
12x21
13x19
14x18
15x17
Of course a few bits would remain unused, but that shouldn't be a problem.
I think esp. 3x85 (1 bit is unused) would be of interest for glider/spaceship synthesis. I happens that certain objects does not or only trivially occur in the actual soups, but might pop up in a synthesis suitable way in such a soup.
I would like that apgsearch does not only allow 2^N x 2^(8-N)
1x256
2x128
4x64
8x32
I would like to run the other numbers as well (at least up to 7), i.e.
3x85
5x51
6x42
7x36
9x28
10x25
11x23
12x21
13x19
14x18
15x17
Of course a few bits would remain unused, but that shouldn't be a problem.
I think esp. 3x85 (1 bit is unused) would be of interest for glider/spaceship synthesis. I happens that certain objects does not or only trivially occur in the actual soups, but might pop up in a synthesis suitable way in such a soup.
- Apple Bottom
- Posts: 1034
- Joined: July 27th, 2015, 2:06 pm
- Contact:
Re: apgsearch v4.0
You could probably implement without too much difficulty -- the soup generation code is in includes/hashsoup2.h, hashsoup_inner(). Be sure to use a _Test symmetry if you do!2718281828 wrote:I would like to run the other numbers as well (at least up to 7), i.e.
3x85
5x51
6x42
7x36
9x28
10x25
11x23
12x21
13x19
14x18
15x17
Of course a few bits would remain unused, but that shouldn't be a problem.
I think esp. 3x85 (1 bit is unused) would be of interest for glider/spaceship synthesis. I happens that certain objects does not or only trivially occur in the actual soups, but might pop up in a synthesis suitable way in such a soup.
If you speak, your speech must be better than your silence would have been. — Arabian proverb
Catagolue: Apple Bottom • Life Wiki: Apple Bottom • Twitter: @_AppleBottom_
Proud member of the Pattern Raiders!
Catagolue: Apple Bottom • Life Wiki: Apple Bottom • Twitter: @_AppleBottom_
Proud member of the Pattern Raiders!