From a5e378e2b4c075f09d3293ccc301f0e504cb20d7 Mon Sep 17 00:00:00 2001 From: Brian Cully Date: Fri, 19 Feb 2021 15:27:22 -0500 Subject: Alter rule flow MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit It’s simpler to put kill/clone buttons on the final step, so kill the initial clone step. This is probably more sensible overall. The old, clone first method was done to simplify the state machine at the time, at the cost of expected instruction order. --- index.html | 35 +++++++++++++---------------------- 1 file changed, 13 insertions(+), 22 deletions(-) (limited to 'index.html') diff --git a/index.html b/index.html index aa3a25b..2d96b9d 100644 --- a/index.html +++ b/index.html @@ -29,26 +29,22 @@ -- more times:
    -
  1. - the genome to - start mutating it. -
  2. -
  3. Roll to find the nucleotide to mutate. +
  4. + +
  5. + Depending on the roll: +
    • If the roll is between 1 through 18, inclusive, select that nucleotide.
    • -
    • Otherwise, skip mutation and clone the genome - again.
    • +
    • Otherwise, skip mutation and + the + genome again.
  6. -
  7. - Select the rolled - nucleotide in the sequence. -
  8. -
  9. Roll to see what kind of mutation to perform.
  10. @@ -76,12 +72,12 @@
  11. Depending on the change to the codon:
      -
    • If the mutation caused a change in the amino acid being - coded, mark this mutation as lethal, and start - over with the genome from the previous iteration.
    • +
    • If the mutation caused a change in the amino acid + being coded, then it and + start again with the previous generation.
    • -
    • Otherwise, mark the mutation as non-lethal, - and continue with this new genome.
    • +
    • Otherwise, this + genome for the next generation.
@@ -130,11 +126,6 @@ - - -- cgit v1.2.3