|
|
| Line 1: |
Line 1: |
| This is a rough draft of a tutorial for basic LLSSS spaceship searches. Feel free to edit this page.
| |
|
| |
| Lattice Life slice spaceship search (LLSSS) is a part of [[Keith Amling]]'s rlife search suite available [https://codeberg.org/amling/rlife here]. It is inspired by [[Andrew J. Wade]]'s [[LSSS]] search program. Any questions about installing and using LLSSS can be asked in [https://conwaylife.com/forums/viewtopic.php?f=9&t=5646 this forum thread].
| |
|
| |
| == Installing ==
| |
| === Prerequisites === | | === Prerequisites === |
| LLSSS is written in [https://www.rust-lang.org/ Rust] and requires the Rust compiler. You can install the Rust compiler for your system by following the steps given [https://www.rust-lang.org/learn/get-started here]. This tutorial assumes that you are using a Unix-like command line terminal with [https://git-scm.com/ git]. Those running Windows may wish to compile and run LLSSS through Windows subsystem for Linux (WSL2). Compilation of LLSSS may take up to 10GB of RAM. | | LLSSS is written in [https://www.rust-lang.org/ Rust] and requires the Rust compiler. You can install the Rust compiler for your system by following the steps given [https://www.rust-lang.org/learn/get-started here]. This tutorial assumes that you are using a Unix-like command line terminal with [https://git-scm.com/ git]. Those running Windows may wish to compile and run LLSSS through Windows subsystem for Linux (WSL2), in which case you will need to find instructions for installing Rust on Linux. |
| | |
| === Downloading and compiling the program ===
| |
| First, create a new folder for LLSSS and open a command-line terminal in this folder. Clone the rlife repository with the following command:
| |
| <nowiki>git clone https://codeberg.org/amling/rlife</nowiki>
| |
| Next, enter the newly created <code>rlife</code> folder by running
| |
| cd rlife
| |
| To compile the program, run the following command:
| |
| cargo build --release
| |
| Compilation will take several minutes and may take up to 10GB of RAM. Have patience.
| |
|
| |
|
| When compilation is complete, the program binary will be contained in the newly created folder <code>target/release</code>. To enter this folder, run
| | Compilation of LLSSS may take up to 14GB of RAM. If your system does not have this amount available to it, the compilation step may fail after several minutes with an error message stating <code>process didn't exit successfully</code>. In this case, you will need to increase the available amount of swap memory for your system. Guides on how to do this for various operating systems can be found online. An explanation for WSL2 is given below. |
| cd target/release
| |
| You are now ready to run LLSSS. When running LLSSS in the future, you can simply open a command terminal in the <code>release</code> folder without needing to recompile the program.
| |
|
| |
|
| == A simple example search ==
| | To increase the swap memory available to WSL2, you will need to create a file with the name <code>.wslconfig</code> in the folder <code>C:\Users\<UserName></code>, where <code><UserName></code> is your Windows user name. If the file already exists, then you can edit the existing file. The file should contain at least the following lines: |
| rlife actually contains three variants of LLSSS, called <code>llsss</code>, <code>llsss-recentering</code>, and <code>llsss-recentering-wao</code>. Each works slightly differently and requires slightly different input. For this example, we will find the [[turtle]] using a front-to-back search with even symmetry using each LLSSS variant.
| |
| | |
| First, we will set an environment variable that tells LLSSS to stop when it finds a solution. This is accomplished by running
| |
| export LLSSS_HALT_ON_ENDS=true
| |
| If you wish to turn this feature off again, simply use the same command with <code>true</code> replaced by <code>false</code>. If <code>LLSSS_HALT_ON_ENDS</code> is <code>false</code>, then many searches will run forever. If you want to kill a search while it's running, you can use the keyboard shortcut <code>Ctrl</code>+<code>C</code>.
| |
| | |
| === llsss ===
| |
| To find the turtle using a fixed-width search, you can run the following command:
| |
| ./rlife llsss --rule 'B3/S23' --left-edge even --filters wcaf c3-f2b '@zero:9' > output.txt
| |
| Let's break down the input:
| |
| * <code>./rlife</code> tells the terminal to run the rlife binary that we just compiled.
| |
| * <code>llsss</code> tells rlife to run a fixed-width LLSSS search.
| |
| * <code>--rule 'B3/S23'</code> sets the rule to [[Conway's Game of Life|Life]].
| |
| * <code>--left-edge even</code> sets the left edge to have even-width bilateral symmetry.
| |
| * <code>--filters wcaf</code> is the "W-cycle avoidance filter". In this case, it stops the search if at some point all partial results have an empty first row (this would mean that no ships exist at the given width).
| |
| * <code>c3-f2b</code> is the geometry of the search. In this case we're searching for c/3 orthogonal ships from front to back.
| |
| * <code>'@zero:9'</code> is a "magic grid generator" for the geometry (see the [[#start_file|<var>start_file</var> section]] for more details). In this case we are searching for a ship starting from empty ("zero") rows with "width" 9.
| |
| * <code>> output.txt</code> sends the output to the file <code>output.txt</code>.
| |
| | |
| There are two things to note in particular about the above input. First, the "width" of the search is 9, but finding the turtle in an even-symmetric search should only require a width of 6. The extra 3 columns come from the fact that LLSSS includes both the duplicated column on the left (due to symmetry), and two empty columns on the right.
| |
| | |
| The other thing to note is that <code>--filters wcaf</code> isn't actually necessary for this search. In this example, the turtle will be found regardless of whether it's included. We include it here as a matter of good practice. If we did not include it, and a ship did not exist at this width, then the search would continue forever. To see this, you can try running the above search at width 8 with and without <code>--filters wcaf</code>.
| |
| | |
| The above search will only take a few seconds to run. To locate the completed spaceship in the output, we need to search <code>output.txt</code> for the first occurrence of <code>[Info] End</code>. In this case, you'll find something like this: | |
| <pre> | | <pre> |
| [INFO] End ("LlsssEndsZero"):
| | # Settings apply across all Linux distros running on WSL 2 |
| [INFO] | ......... | ......... | ......... |
| | [wsl2] |
| [INFO] | ......... | ......... | ......... |
| |
| [INFO] | ......... | **....... | **....... |
| |
| [INFO] | ***.*.... | ..*.**... | **.***... |
| |
| [INFO] | ***.**... | ....**... | ......*.. |
| |
| [INFO] | **....*.. | ...*.*... | ..**.*... |
| |
| [INFO] | ***...... | ..**..... | **....... |
| |
| [INFO] | ...**.... | **.**.... | **..*.... |
| |
| [INFO] | ...*..... | ..*...... | ***.*.... |
| |
| [INFO] | ..*.*.... | ....*.... | ...*..... |
| |
| [INFO] | ****..... | ....*.... | ......... |
| |
| [INFO] | ****..... | ......... | ***.*.... |
| |
| [INFO] | ....**... | *****.... | ******... |
| |
| [INFO] | ......... | ....**... | ***.**... |
| |
| [INFO] | .....*... | ......... | ......... |
| |
| [INFO] | **....... | ......... | ......... |
| |
| [INFO] | ......... | ......... | ......... |
| |
| [INFO] | ......... | | |
| |
| </pre>
| |
| Notice that this shows just one of the symmetric halves of the [[turtle]] in each of its three phases. You will need to construct the complete symmetric spaceship yourself using a Life editing application, such as [[Golly]] or [[LifeViewer]].
| |
| | |
| === llsss-recentering ===
| |
| | |
| <code>llsss-recentering</code> is a variant of LLSSS that allows the center of the search to drift to the left or right analogously to [[Ikpx#Floating_rows|floating rows]] in ikpx. The input is almost identical to that for <code>llsss</code>:
| |
| ./rlife llsss-recentering --rule 'B3/S23' --left-edge even --filters wcaf c3-f2b '@zero' 6 > output.txt
| |
| Besides replacing <code>llsss</code> with <code>llsss-recentering</code>, the only other difference is replacing <code>'@zero:9'</code> with <code>'@zero' 6</code>. The new parameter after <code>'@zero'</code> is called the <var>[[#mid_steps|mid_steps]]</var> and can be thought of as the "width" of a recentering search. In this case, a <var>mid_steps</var> value of 6 is sufficient to find the turtle. To locate the completed spaceship in the output, we can again search <code>output.txt</code> for the first occurrence of <code>[Info] End</code>.
| |
| | |
| === llsss-recentering-wao ===
| |
| | |
| <code>llsss-recentering-wao</code> is an alternate recentering variant of LLSSS that uses a different method (other than <code>--filters wcaf</code>) to force live cells in the first row. The input looks somewhat different from the previous two setups:
| |
| ./rlife llsss-recentering-wao --wao-left-pad 0 --wao-right-pad 0 --wao-idx ALL --rule 'B3/S23' --left-edge even --wao-left-edge-errors c3-f2b '@zero' 6 > output.txt
| |
| First, notice that we removed <code>--filters wcaf</code>, as it's no longer necessary. We also added several new options. Most importantly, the new option <code>--wao-left-edge-errors</code> must be included if you set <code>--left-edge</code> to some form of symmetry. It should not be included in an asymmetric search. The options <code>--wao-left-pad</code>, <code>--wao-right-pad</code>, and <code>--wao-idx</code> are not discussed here. We will simply be including them with the respective values <code>0</code>, <code>0</code>, and <code>ALL</code> in all wao searches in this tutorial. As before, the completed spaceship is marked by the first occurrence of <code>[Info] End</code> in <code>output.txt</code>.
| |
| | |
| == Basic LLSSS options ==
| |
| | |
| This section covers only some of the basic LLSSS options. A complete list of options can be generated by running
| |
| ./rlife <search-method> --help
| |
| where <code><search-method></code> is one of <code>llsss</code>, <code>llsss-recentering</code>, or <code>llsss-recentering-wao</code>.
| |
|
| |
|
| === Environment variables ===
| | # Sets amount of swap storage space to 16GB, default is 25% of available RAM |
| Environment variables must be defined before the search is started. In a Linux terminal they can be set by running the command
| | swap=16GB |
| export <variable>=<value>
| |
| To reset an LLSSS environment variable to its default value, run the command
| |
| unset <variable>
| |
| A full list of LLSSS-specific environment variables and their current values can be obtained by running
| |
| <pre>
| |
| ./rlife show-env
| |
| </pre> | | </pre> |
| | | Here 16GB was chosen to be sufficient for compiling rlife. After creating or editing this file, you will need to restart WSL2 for the changes to take effect. You can check the total amount of available swap memory in WSL2 by running |
| Below is a table containing some of the basic LLSSS environment variables:
| |
| {| class="wikitable"
| |
| ! Variable !! Possible values !! Default value !! Description
| |
| |-
| |
| | <code>LLSSS_HALT_ON_ENDS</code>
| |
| | <code>true</code>, <code>false</code>
| |
| | <code>false</code>
| |
| | If set to <code>true</code>, LLSSS will halt when one of the ends given by the <code>--ends</code> option is found.
| |
| |-
| |
| | <code>LLSSS_INIT_CA_CHECKS</code>
| |
| | <code>true</code>, <code>false</code>
| |
| | <code>true</code>
| |
| | If set to <code>true</code>, LLSSS will filter the initial search state based on the cellular automaton rule give by the <code>--rule</code> option. This limits the size of the <var>[[#start_file|start_file]]</var>, so if you have a very large file that you know is valid, you can set the value of this variable to <code>false</code>. This variable should be set to <code>true</code> when using wildcards, which are not covered by this tutorial.
| |
| |-
| |
| | <code>LLSSS_MAX_TABLE_SIZE</code>
| |
| | integers ≥ 9
| |
| | <code>27</code>
| |
| | Limits the size of rule check tables. These tables are built each time you run LLSSS, and allow the main search to run slightly faster. For some geometries (especially diagonal geometries) these tables can take over a minute to be built, so if you intend to run very short searches it can be beneficial to lower this value. In such cases, a recommended low value is <code>15</code>.
| |
| |}
| |
| | |
| === Required arguments ===
| |
| | |
| There are a few required command line arguments that can be placed anywhere among the options, but must be given in a particular order. They are the <var>geometry</var>, <var>start_file</var>, and <var>mid_steps</var>, and are described below. The third argument, <var>mid_steps</var>, only applies to searches run with <code>llsss-recentering</code> or <code>llsss-recentering-wao</code>, and should not be included in searches run with <code>llsss</code>.
| |
| | |
| ==== geometry ====
| |
| The <var>geometry</var> is a string indicating both the velocity of the desired spaceship and the direction in which the search progresses. The substrings <code>f2b</code>, <code>b2f</code>, and <code>s2s</code> mean "front-to-back", "back-to-front", and "side-to-side" respectively, and indicate the direction that the search progresses relative to the direction of travel of the desired spaceship. A complete list of valid geometries is given in the following table, where <code>K</code> is the displacement (empty <code>K</code> if <code>K=1</code>) and <code>N</code> is the period of the desired spaceship:
| |
| | |
| {| class="wikitable"
| |
| ! Geometry !! Spaceship direction !! Search direction
| |
| |-
| |
| | <code>KcN-f2b</code> || orthogonal north || south
| |
| |-
| |
| | <code>KcN-b2f</code> || orthogonal south || south
| |
| |-
| |
| | <code>KcN-s2s</code> || orthogonal west || south
| |
| |-
| |
| | <code>KcNd-f2b</code> || diagonal northwest || southeast
| |
| |-
| |
| | <code>KcNd-b2f</code> || diagonal southeast || southeast
| |
| |-
| |
| | <code>KcNd-s2s</code> || diagonal northwest || southwest
| |
| |-
| |
| | <code>KcNd-down</code> || diagonal northwest || south (f2b-like)
| |
| |-
| |
| | <code>KcNd-up</code> || diagonal southeast || south (b2f-like)
| |
| |-
| |
| | <code>KcNk-1</code> || knight-wise north-northwest || south (most f2b-like)
| |
| |-
| |
| | <code>KcNk-2</code> || knight-wise west-northwest || south
| |
| |-
| |
| | <code>KcNk-3</code> || knight-wise east-southeast || south
| |
| |-
| |
| | <code>KcNk-4</code> || knight-wise south-southeast || south (most b2f-like)
| |
| |-
| |
| | <code>pN</code> || none (oscillator) || south
| |
| |-
| |
| | <code>raw:...</code> || custom || custom
| |
| |}
| |
| <code>pN</code> and <code>raw</code> geometries are not described in this tutorial.
| |
| | |
| ==== start_file ====
| |
| The <var>start_file</var> represents the cells present at the beginning of the search. It can either be a file or a magic grid generator. The construction of an actual <var>start_file</var> can be difficult, and some basic <var>start_file</var> construction is shown in the [[#Extending partial results|extending partial results]] section.
| |
| | |
| Magic grid generators are simple command line inputs that give us an easy way to set up a search starting from empty rows or from a small selection of predefined [[agar]]s. For <code>llsss-recentering</code> and <code>llsss-recentering-wao</code> searches, the magic grid generator representing empty rows is <code>'@zero'</code>, while the magic grid generator for agars is <code>'@agar:<agar-name>'</code>. Possible values for <code><agar-name></code> can be found by running the command
| |
| ./rlife grid-tool agar-info
| |
| The current list of predefined agars is
| |
| <pre> | | <pre> |
| b0
| | free -h |
| blocks
| |
| horizontal-stripes
| |
| vertical-stripes
| |
| zero
| |
| </pre> | | </pre> |
| Searches with an agar background cannot be run naively, as they will need some additional options to run properly. For example, see the [[#B0 searches|B0 search section]], which shows how to set up a spaceship search in rules with B0.
| |
|
| |
| For <code>llsss</code> searches, the magic grid generator must also include an additional colon (<code>:</code>) followed by the width of the search. In this case, the width includes some extra columns that are not traditionally considered part of the width of the spaceship. For example, see the [[#llsss|simple example search]] section.
| |
|
| |
| ==== mid_steps ====
| |
| <var>mid_steps</var> is an integer that can be thought of as the "width" of a recentering search, although it does not translate perfectly to traditional notions of spaceship width. This argument must be included in <code>llsss-recentering</code> and <code>llsss-recentering-wao</code> searches, but should not be included in <code>llsss</code> searches. For <code>llsss</code> searches, the width is instead included as part of the [[#start_file|<var>start_file</var>]].
| |
|
| |
| === Options ===
| |
|
| |
| The following table contains only those options and values used in this tutorial. There are more options and some of the options listed can take more values than are presented here.
| |
|
| |
| {| class="wikitable"
| |
| ! Option !! Possible values !! Default value !! Details
| |
| |-
| |
| | <code style="white-space: nowrap;">--rule '<rulestring>'</code>
| |
| | a rulestring in [[Hensel notation|Hensel]] or [[Isotropic_non-totalistic_rule#Hexagonal_grid|Callahan]] notation
| |
| | <code style="white-space: nowrap;">B3/S23</code>
| |
| | Rulestrings should be enclosed in single quotes (<code>'</code>). A list of forbidden neighborhoods can be specified at the end of the birth and survival conditions, preceded by an exclamation mark (<code>!</code>). For example, to search in rule B3/S23 for ships that never contain the B6, S4i, or S5k neighborhoods, use <code style="white-space: nowrap;">--rule 'B3!6/S23!4i5k'</code>.
| |
| |-
| |
| | <code style="white-space: nowrap;">--left-edge <boundary-condition></code>,
| |
| <code style="white-space: nowrap;">--right-edge <boundary-condition></code>
| |
| | <code>even</code>, <code>odd</code>, <code>gutter</code>, <code>gse</code>, <code>gso</code>, <code>zero</code>, <code style="white-space: nowrap;">agar:<agar-name></code>
| |
| | <code>zero</code>
| |
| | This defines the boundary condition of the specified side. The value is either a symmetry type, empty (<code>zero</code>), or an agar. Values <code>gse</code> and <code>gso</code> are "glide-symmetric even" and "glide-symmetric odd" respectively. Values for <code style="white-space: nowrap;"><agar-name></code> are given in the [[#start_file|<var>start_file</var> section]].
| |
| |-
| |
| | <code style="white-space: nowrap;">--wao-left-edge-errors</code>,
| |
| <code style="white-space: nowrap;">--wao-right-edge-errors</code>
| |
| |
| |
| |
| |
| | These options should be included in an <code style="white-space: nowrap;">llsss-recentering-wao</code> search if the respective <code style="white-space: nowrap;">--left-edge</code> or <code style="white-space: nowrap;">--right-edge</code> boundary conditions are set to a symmetry type. They should not be included if the boundary condition is <code>zero</code> or an agar.
| |
| |-
| |
| | <code style="white-space: nowrap;">--filters <filters></code>
| |
| | <code>wcaf</code>, <code style="white-space: nowrap;">acaf:<agar-name></code>
| |
| |
| |
| | These are filters that remove parts of the search state as certain conditions are met. Multiple filters can be included, separated by commas (<code>,</code>). <code>wcaf</code> is the "W-cycle avoidance filter" that prevents a search starting with empty rows from continuing forever if there are no spaceships. Analogously, <code>acaf</code> is the "agar-cycle avoidance filter". Values for <code style="white-space: nowrap;"><agar-name></code> are given in the [[#start_file|<var>start_file</var> section]].
| |
| |-
| |
| | <code style="white-space: nowrap;">--partials <partials></code>
| |
| | <code>srv2</code>, <code>srv2:<w_min>:<w_max></code>
| |
| |
| |
| | This option causes LLSSS to print some extra partial results that have narrowed or have split into two narrow branches. The printing of these partial results can take some extra time, so this option should not be set unless you think you might use the extra partial results. More details are given in the [[#Seam ripper partials|seam ripper partials section]].
| |
| |-
| |
| | <code style="white-space: nowrap;">--ends <end-conditions></code>
| |
| | <code>even</code>, <code>odd</code>, <code>gse</code>, <code>gso</code>, <code>zero</code>, <code style="white-space: nowrap;">skew_gutter:<skew></code>, <code style="white-space: nowrap;">agar:<agar-name></code>
| |
| | <code>zero</code>
| |
| | This option causes LLSSS to print results with the specified end conditions. Multiple ends can be included, separated by commas (<code>,</code>). For example, <code style="white-space: nowrap;">--ends zero,even,odd</code> will print any results where the bottom of the search becomes bilaterally symmetric (<code>even</code> and <code>odd</code>) or empty (<code>zero</code>). Values <code>gse</code> and <code>gso</code> are "glide-symmetric even" and "glide-symmetric odd" respectively. Values for <code style="white-space: nowrap;"><agar-name></code> are given in the [[#start_file|<var>start_file</var> section]].
| |
| |-
| |
| | <code style="white-space: nowrap;">--halts <halt-conditions></code>
| |
| | <code style="white-space: nowrap;">w_pos:<max-w_pos></code>
| |
| |
| |
| | This option halts the search when it reaches the given depth (<var>w_pos</var>).
| |
| |-
| |
| | <code style="white-space: nowrap;">--wao-left-pad <wao-pad></code>,
| |
| <code style="white-space: nowrap;">--wao-right-pad <wao-pad></code>
| |
| | nonnegative integers
| |
| | <code>1</code>
| |
| | A very technical explanation of these options can be found in two consecutive forum posts starting [https://conwaylife.com/forums/viewtopic.php?p=199576#p199576 here]. For all searches in this tutorial using <code style="white-space: nowrap;">llsss-recentering-wao</code> we will set these values to <code>0</code>.
| |
| |-
| |
| | <code style="white-space: nowrap;">--wao-idx <indices></code>
| |
| | nonnegative integers, <code>ALL</code>
| |
| |
| |
| | A very technical explanation of this option can be found in two consecutive forum posts starting [https://conwaylife.com/forums/viewtopic.php?p=199576#p199576 here]. For all searches in this tutorial using <code style="white-space: nowrap;">llsss-recentering-wao</code> we will set this value to <code>ALL</code>.
| |
| |}
| |
|
| |
| == <tt>B0</tt> searches ==
| |
|
| |
| In rules with B0 and without S8, the background of the CA universe has period 2, alternating between dead and alive cells. This strobing agar background must be indicated in our inputs if we want to search for spaceships in these rules. This is accomplished with the built-in agar <code>b0</code>.
| |
|
| |
| We assume for this section that the [[#Environment variables|environment variable]] <code>LLSSS_HALT_ON_ENDS</code> has been set to <code>true</code>.
| |
|
| |
| === A simple working example ===
| |
|
| |
| Here is a setup for a fixed-width, odd-symmetric c/2 orthogonal search in B026/S2:
| |
| ./rlife llsss --rule 'B026/S2' --left-edge odd --right-edge agar:b0 --filters acaf:b0 --ends agar:b0 c2-f2b '@agar:b0:8'
| |
| Notice that, compared to [[#A simple example search|our earlier example search]], we can no longer use the default values for <code>--right-edge</code> and <code>--ends</code> and must instead set them both to <code>agar:b0</code>. We also must replace the <code>wcaf</code> filter with its <code>b0</code> agar equivalent, <code>acaf:b0</code>. Finally, we must use the agar magic grid generator <code>'@agar:b0:8'</code> to represent the start of the search. Notice that in the output, one phase of the discovered spaceship has live cells on the (non-symmetric) borders, while the other has dead cells on the borders, as should be expected in a rule with B0:
| |
| <pre>
| |
| [INFO] End ("LlsssEndsAgar"):
| |
| [INFO] | ******** | ........ |
| |
| [INFO] | ******** | ........ |
| |
| [INFO] | *.*..*** | .*.*.... |
| |
| [INFO] | *..***** | ..**.... |
| |
| [INFO] | .....*** | **.*.... |
| |
| [INFO] | *.....** | ..*.*... |
| |
| [INFO] | ....*.** | ..**.... |
| |
| [INFO] | ....*.** | ***..... |
| |
| [INFO] | ....**** | ****.... |
| |
| [INFO] | .....*** | ***..... |
| |
| [INFO] | .....*** | *....... |
| |
| [INFO] | .*..*.** | *.***... |
| |
| [INFO] | ...*..** | ........ |
| |
| [INFO] | .**.*.** | ........ |
| |
| [INFO] | ***...** | ....*... |
| |
| [INFO] | *....*** | ..*.*... |
| |
| [INFO] | *....*** | ........ |
| |
| [INFO] | **..*.** | ..**.... |
| |
| [INFO] | **..**** | ..**.... |
| |
| [INFO] | *....*** | ..**.... |
| |
| [INFO] | **..**** | ........ |
| |
| [INFO] | *.**.*** | ........ |
| |
| [INFO] | ******** | ........ |
| |
| [INFO] | ******** | |
| |
| </pre>
| |
|
| |
| === B0 searches with symmetric ends ===
| |
|
| |
| Currently, symmetric ends do not work properly in B0 rules when using <code>llsss</code> or <code>llsss-recentering</code>, so such searches must be done with <code>llsss-recentering-wao</code>. For example, consider the following side-to-side c/2 orthogonal search with <code>llsss-recentering</code>:
| |
|
| |
| ./rlife llsss-recentering --rule 'B026/S2' --left-edge agar:b0 --right-edge agar:b0 --filters acaf:b0 --ends even,odd,agar:b0 c2-s2s '@agar:b0' 9
| |
|
| |
| Here we use <code>--ends even,odd,agar:b0</code>, because we want the search to finish if it finds half of a symmetric ship. This search terminates quickly with the following reported false end:
| |
| <pre>
| |
| [INFO] End [thinnest] "LlsssEndsReflect(Even)":
| |
| [INFO] | ZZ | ZZ |
| |
| [INFO] | ** | .. |
| |
| [INFO] | ** | .. |
| |
| [INFO] | ** | .. |
| |
| </pre>
| |
| Unfortunately, this is just a small patch of the background agar, not an actual spaceship.
| |
|
| |
| Fortunately, we can make this search work if we instead run the "equivalent" <code>llsss-recentering-wao</code> search:
| |
| ./rlife llsss-recentering-wao --wao-left-pad 0 --wao-right-pad 0 --wao-idx ALL --rule 'B026/S2' --left-edge agar:b0 --right-edge agar:b0 --ends even,odd,agar:b0 c2-s2s '@agar:b0' 9
| |
| This time we get the following proper spaceship:
| |
| <pre>
| |
| [INFO] End [thinnest] "LlsssEndsReflect(Odd)":
| |
| [INFO] | ZZZZZZZZZZZZ | ZZZZZZZZZZZZ |
| |
| [INFO] | ************ | ............ |
| |
| [INFO] | ************ | ............ |
| |
| [INFO] | *******...** | ............ |
| |
| [INFO] | *****..*..** | .......*.... |
| |
| [INFO] | ***..*..**** | .....*...... |
| |
| [INFO] | **.*.*.*..** | ...*...*.... |
| |
| [INFO] | **..*.*...** | ..*......... |
| |
| [INFO] | ****...***** | ............ |
| |
| [INFO] | **..*..*.*** | ..*.*....... |
| |
| [INFO] | **.*...***** | .....**..... |
| |
| [INFO] | **.**...**** | ...**.*..... |
| |
| [INFO] | **.....*.*** | ..*..*...... |
| |
| [INFO] | ****.*.***** | ....*....... |
| |
| </pre>
| |
| Note that this is only half of the spaceship. The end is reported as <code>LlsssEndsReflect(Odd)</code>, so the complete spaceship has odd-width bilateral symmetry, with the bottom row of the above pattern representing the center of the ship.
| |
|
| |
| == Seam ripper partials ==
| |
|
| |
| Under construction.
| |
|
| |
| == Extending partial results ==
| |
|
| |
| Under construction.
| |
|
| |
| == Saving and loading the search state ==
| |
|
| |
| Under construction.
| |
|
| |
| == See also ==
| |
| [[Tutorials/LSSS]]
| |