Updates and Results
Talks and Posters
Advice
Ideas
Important Figures
Write-Ups
Outreach
How-To
Funding Opportunities
GENETIS
GENETIS
Draft saved at 00:00:00
Fields marked with
*
are required
Entry time:
Tue Feb 3 18:01:40 2026
Author
*
:
Subject
*
:
<table border="1" cellpadding="1" cellspacing="1"> <tbody> <tr> <td>Name</td> <td>Update for Today</td> <td>Plans for Tomorrow</td> </tr> <tr> <td>Alex M</td> <td> <p>Continued the run from yesterday. Alex P and I applied the changes we made to the bash script for fixing the bugs we found in the simulation number to the database version. Once we get 15 generations of data for this run we'll start testing the database version. Once that works we'll have Eliot and Leo run their version with only 3 genes and if we get the same genes all around we'll be able to merge the asymmetric branch with the database branch and then merge with master. I also fixed up a bug I found in one of the plotting programs that meant it was missing the first individual, it should be good now.</p> <p>Ryan and I talked a bit about how to apply crossover and mutation to the paperclip. I'm not sure that crossover makes sense, but I think it's possible. He's going to start by doing crossover of the chromosomes and then when that's working he can try crossing over the genes (this is where I'm not sure things make sense, but who knows). Then he can implement mutation in that function.</p> <p>Julie and I spoke with Ben about AREA and started helping him siftt through all the files. We're going to meet with Ethan tomorrow to catch him up to speed and start reviewing the bash script that runs all of AREA.</p> </td> <td> <p>Finish this run, test the database. I'll meet with Julie, Ben, and Ethan to talk about AREA. Also, Eliot and Leo found a potential issue in the roulette algorithm that I asked them to look at, so we might try making a fix in there and see if that allows our mutations to be more reasonable. Alex and I are going to have to meet with Eliot and Leo soon so we can all work together on merging our branches and resolving merge conflicts.</p> <p> </p> </td> </tr> <tr> <td>Alex P</td> <td>Made a version of my c++ programs that detect whether an individual matches the database and logs that/writes to the database in a way that allows the number of genes to be a variable so that it can be compatible with new antenna designs. Then set to fix the scripts that used the database to fix the error of the right simulation numbers while continuing the current run so that we can test if the database version gives the same results and then will start running the database version and make sure it is good before we merge.</td> <td>Run database test and if it has any differences or bugs from the original, fix those before we merge. Also have Eliot and Leo run thiers but with just three parameters so that we can test and make sure the accuracy between all versions is the same and none have bugs present before we merge.</td> </tr> <tr> <td>Eliot</td> <td> </td> <td> </td> </tr> <tr> <td>Leo</td> <td> </td> <td> </td> </tr> <tr> <td>Evelyn</td> <td> </td> <td> </td> </tr> <tr> <td>Ryan</td> <td> </td> <td> </td> </tr> <tr> <td>Ben</td> <td> </td> <td> </td> </tr> <tr> <td>Ethan</td> <td> </td> <td> </td> </tr> </tbody> </table> <p> </p>
Encoding
:
HTML
ELCode
plain
Suppress Email notification
Attachment 1:
Drop attachments here...
Draft saved at 00:00:00
ELOG V3.1.5-fc6679b