ELOG GENETIS

Updates and Results Talks and Posters Advice Ideas Important Figures Write-Ups Outreach How-To Funding Opportunities GENETIS

GENETIS

Fields marked with * are required
Entry time:	Tue Feb 3 12:09:11 2026
Author*:
Subject*:
<table border="1" cellpadding="1" cellspacing="1"> <tbody> <tr> <td>Name</td> <td>Update</td> <td>Plans for Tomorrow</td> </tr> <tr> <td>Alex M</td> <td> <p>(See below the table for a review of the past couple of days since ELOG has been down.)<br /> We may have found what was causing the error in Eliot and Leo's version. They were getting 0 effective volumes. I edited their output macroskeletons to use pro grid (I figured it was the default setting, but it looks like not). This seems to have fixed the issue with their .uan files having all 0s and 180s for the phase and -300 gain. However, it wasn't writing to the vEffective.csv and fitnessScores.csv files correctly. We realized they may have needed to recompile. We did that and ran a preliminary tset, where we got some promising results. The effective volumes and fitness scores seem to have been read out and plotted correctly, but they didn't appear to match the previous two runs Alex P and I did. That might be because we were messing around with the save state sloppily. Currently, Eliot is rerunning from the beginning with the intention of seeing if it will go all the way through generation 0 smoothly. From there, we'll need to compare the effective volumes and fitness scores with the previous two runs Alex P and I did (although I can confirm that the generation 0 DNA matches). Then we'll need to let it run for a few more generations to make sure it evolves the same individuals those two previous runs evolved.</p> </td> <td> <p>If it looks like these fixes worked and the effective volumes are being made correctly and the same individuals are evolved as in the previous two runs Alex P and I did, then we'll be ready to start merging. The first step will be to fix a merge conflict on the asymmetric bicone branch. Then, we'll have to carefully merge and resolve merge conflicts. The order should be that the asymmetric bicone branch merges onto the database branch, which will then merge onto the master branch. Once that's done, we'll be able to do a proper run.</p> </td> </tr> <tr> <td>Alex P</td> <td>Worked with Alex, Eliot, and Leo to fix an error on Eliot and Leo's branch since we got both the normal and database version working on the Alex's branch. Had some problems with 0 vEffectives and saw that XF was giving 0 gains so searched through for a while to see what was different and had to enable PrOGrid, and then that made the vEffectives nonzero but it still seemed like they might have been too high.</td> <td>Get Eliot/Leo's branch working hopefully have test run overnight that shows that and then merge tomorrow is the plan.</td> </tr> <tr> <td>Eliot</td> <td> </td> <td> </td> </tr> <tr> <td>Leo</td> <td>Like both Alexs said, Eliot and I worked with them to get our version to get the same results as their version. The main problem we worked on were the 0 vEffectives and fitness scores. We realized that the fitness scores and vEffectives were printing to the terminal, but not to the plots or .csv files. We check the fitness function called in the loop and it turned out we compliled to a wrong version. After recompiling the fitness score correctly Eliot started a new run and it is currently running over night.</td> <td>Tomorrow, we will take a look at Eliot's run to see how it did and find any other areas that may cause for different results between our's and the Alexs' runs.</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>Worked with Ben on running AraSim and fixing errors it would output</td> <td> </td> </tr> </tbody> </table> <p>Review of the past two days (wrt the bicone loop) since ELOG has been down:<br /> Alex P and I were able to fix errors in the database version of the loop. It now evolves the same individuals as the original version (when using seeds). We want to test the asymmetric version, but we ran into some errors. First, we needed to add in the cutoff length and the change in Detector.cc to set negative gains equal to 0. Once we did that, we tried running but found some more errors. Specifically, the effective volumes coming from AraSim were all 0. We may have fixed the error today, but we're waiting for the run to finish the 0th generation to be able to tell.</p> <p> </p> Encoding: HTML ELCode plain Suppress Email notification

Attachment 1:
Drop attachments here...

ELOG V3.1.5-fc6679b