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 12:09:46 2026
Author
*
:
Subject
*
:
<p> <table width="98%" align="center" cellspacing="1" style="border:1px solid #486090;"> <tbody> <tr> <td cellpadding="3px" style="background-color:#486090; font-weidht:bold; color:white;">Quote:</td></tr> <tr> <td cellpadding="10px" style="background-color:#FFFFB0;"><table border="1" cellpadding="1" cellspacing="1"> <tbody> <tr> <td>Name</td> <td>Today's Update</td> <td>Plans for Tomorrow</td> </tr> <tr> <td>Alex M.</td> <td> <p>Met with Alex P. and Amy to think about how we can make sure the data coming from AraSim makes sense (specifically, to figure out why we're getting effective volumes of 0 on some antennas). Amy suggested we use a function in AraSim that let's us simulate identical events so that we can compare the same events between two different antennas. I asked Jorge in the #general chat to see if he could point us to where to look in AraSim for that function.</p> <p>Met with Amy and Julie about people interested in joining the group and what upcoming project we have. We also talked about Karoo and Kai's thesis and how we can use machine learning to classify noise in the Anita data.</p> </td> <td>I won't be able to meet tomorrow or Friday morning, but I'll try to jump on in the afternoon on Friday and I should be able to make the GENETIS call. Also, Julie wanted to find a time where we could both meet with one of the new members if they have time this week.</td> </tr> <tr> <td> <p>Alex P.</p> </td> <td>Worked in morning with Alex trying to find AraSim's 0 vEff problem, set it up to save AraOut files from now on in Run_Outputs in order to more easily look through. Continued with Git and successfully have working copies set up across multiple people and branches so we can all work without any conflicts. </td> <td>Continue to run and try to debug. Next idea is probably to set it up to pass exact events as specified so we know exactly what event is running and find error that way.</td> </tr> <tr> <td>Eliot</td> <td> <p>Today we finalized the GA. It now works with 2 chromosomes, where only length varies across chromosomes. In addition we got the tournament selection working (we don’t think it was working for even 1 chromosome prior). It is ready to begin being implemented tomorrow. We also met with Julie and others to discuss git and related topics.</p> </td> <td> <p>Tomorrow we will implement the GA and begin editing Xmacros to 1) tell XF the new antenna type, etc and 2) have it read the new 2 chromosome data properly. This will likely take multiple days.</p> </td> </tr> <tr> <td>Leo</td> <td> </td> <td> </td> </tr> <tr> <td>Evelyn</td> <td>Learned more about git and github from Julie </td> <td>Find the old paperclip code and learn how to run and how it works! </td> </tr> <tr> <td>Ryan</td> <td>Continued learning about Git and Github uses from Julie. Went back in the elog history to learn more about a previous "paperclip algorithm" for future uses.</td> <td>Learn more about the paperclip algorithm ad possibly help with more runs. </td> </tr> </tbody> </table> <p> </p></td> </tr> </tbody> </table> </p><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