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 4 17:17:10 2020
Author*:
Subject*:
<p dir="ltr">As of 01/30/2020, the proposal was submitted! The project description and summary are attached below. </p> <h2 dir="ltr" style="text-align:center"><u>Bicone Loop Status Update: </u></h2> <p dir="ltr">The loop currently runs; however, it does seem that if AraSim jobs are left to run while the user is away, it doesn't properly write one or more of the flags, and makes the loop get stuck at AraSim. We must then re-run from that state by manually editing the Save State text file. </p> <p dir="ltr">The loop currently has the following additions implemented.</p> <ul dir="ltr"> <li>Functionalized loop (XF_Loop_AraSeed.sh) <ul> <li>Cleaner bash script which runs smaller bash scripts, instead of one massive script. </li> <li>Submits multiple AraSim jobs in parallel for each individual to increase speed.  <ul> <li>Ie if 100k neutrinos are thrown per individual ($NNT=100000, $Seed=10) we can, say, break it up into a "seed" of 10 -- which then submits 10 jobs with NNT=10k for each individual. </li> </ul> </li> <li><em><span style="background-color:#FFFF00">Still needs this to be fixed: The AraSim run in Gen 0 that gets Veff for the ARA actual bicone input file is not currently being seeded. It is just submitting one job the following way.</span></em> <ul> <li><em><span style="background-color:#FFFF00">If NNT=100000 and Seed=10 (ie 10 jobs with 10k neutrinos), it will only run AraActualBicone as 1 run with 10k neutrino number (ie NNT/seed=NNT_New).</span></em></li> </ul> </li> </ul> </li> <li>Save State  <ul> <li>After every "part" -- ie part a, part b, etc -- of the loop, we save state by writing a series of numbers to a text file.  <ul> <li> <p>${gen}, ${state}, {indiv}</p> </li> </ul> </li> <li> <p>If the loop is killed for any reason during the process, the text file is read in, and the loop can continue forward from the last completed item/section. </p> </li> <li> <p>This saves the state after every individual runs through XF. </p> </li> </ul> </li> <li> <p>Antenna sizing</p> <ul> <li> <p>The larger the antenna, the longer XF takes to run. A true-to-size ARA antenna takes anywhere from 1.5 to 2 hours per individual. </p> </li> <li> <p>What we've done: Allowed us to scale the antenna by a factor of "x".</p> <ul> <li> <p>If we make the gaussian centered around something, say, 5 times smaller than the ARA antenna size, we then make the frequencies 5 times larger. This should have the same effect. </p> </li> <li> <p>This also means we've had to scale these sizes back up when plotting. </p> </li> <li> <p><em><span style="background-color:#FFFF00">Still needs this to be fixed: all of this has been hardcoded in! We need to make these variables in the MANY places we need to adjust for this scaling. See the to-do list below for details. </span></em></p> </li> </ul> </li> </ul> </li> </ul> <p dir="ltr"><br /> <br /> <br /> Moving forward, I will be doing the following:</p> <ol dir="ltr"> <li>Getting our less coding-savvy teammates familiar with bash, python, and c++. This will be crucial for us when we start adding more parameters to our GA. </li> <li>Mastering XF (along with Alex, and Alex). </li> <li>Getting the team to clean up some messy coding done during the proposal hustle. </li> <li>Fixing some errors. </li> <li>Teach the ENTIRE team git. </li> </ol> <h2 style="text-align:center"><br /> <br /> <u>TO-DO List</u></h2> <p>The following is our coding to-do list:</p> <ol dir="ltr"> <li> <p dir="ltr">Get our Ara sim error fixed (Alex, Julie) </p> <ol> <li> <p dir="ltr">It seems that if AraSim jobs are left to run while the user is away, it doesn't properly write one or more of the flags, and makes the loop get stuck at AraSim. We must then re-run from that state by manually editing the Save State text file.</p> </li> <li> <p dir="ltr">We are going to try to get XF to run at the command line so that we can submit it as a job. This would alleviate us using an interactive job. We hope this would fix the error since the user wouldn't be "gone" while utilizing a GPU in an interactive job. </p> <ol> <li> <p dir="ltr">Alex emailed XF to ask a few questions! Stay tuned!</p> </li> </ol> </li> </ol> </li> <li> <p dir="ltr">Make Hardcoded directories variables.</p> <ol> <li> <p dir="ltr">Xmacros (use sed command) </p> </li> <li> <p dir="ltr">All over bash script functions.</p> </li> <li> <p dir="ltr">AraSim job files (sed command?)</p> </li> </ol> </li> <li> <p dir="ltr">Make the following variables in the bash script:</p> <blockquote> <p><br /> <u>In xmacros/simulationPECmacroskeleton_prototype.txt (use sed command):</u></p> <pre> Grid spacing=0.1 Frequency= factor of n higher This factor of "n" higher in frequency has to be the same as the Multiplier_factor in the roulette algorithm AND the same as GeoFactor in fitnessFunction_ARA_amy.cpp. </pre> <p><u>In roulette_algirithm.cpp</u></p> <pre> Length = 50cm/Multiplier_factor; STD= 15cm/Multiplier_factor Radius = 1.5cm/Multiplier_factor; STD= 0.75cm/Multiplier_factor Also the "Multiplier_factor" line 89. This "Multiplier_factor"has to be the same as the GeoFactor in fitnessFunction_ARA_amy.cpp AND the same as the factor higher in frequency in the xmacro. NOTE:THIS MUST BE RECOMPILED AFTER CHANGING. </pre> <p><u>In fitnessFunction_ARA_amy.cpp:</u></p> <pre> GeoFactor=2 This GeoFactor has to be the same as the Multiplier_factor in the roulette algorithm AND the same as the factor higher in frequency in the xmacro NOTE: THIS MUST BE RECOMPILED AFTER CHANGING. </pre> </blockquote> </li> <li> <p dir="ltr">Get rid of all code we are not using anymore.  </p> <ol> <li> <p dir="ltr">Currently using: XF_loop_AraSeed.sh</p> <ol> <li> <p dir="ltr">Look at what items are being called in here, and remove old versions such as XF_loop_Prototype.sh, XF_loop_Functionized.sh, and the related scripts. </p> </li> <li> <p dir="ltr">These can temporarily moved to on "old code" directory and we can delete once we finalize the loop. </p> </li> </ol> </li> </ol> </li> <li> <p dir="ltr">Turn tournament on in the GA. </p> </li> <li> <p dir="ltr">Parallelize the AraActualBicone job.</p> <ol> <li> <p dir="ltr">The AraSim run in Gen 0 that gets Veff for the ARA actual bicone input file is not currently being seeded.</p> </li> </ol> </li> </ol> <p dir="ltr"> </p> <p dir="ltr"> </p> Encoding: HTML ELCode plain Suppress Email notification Resubmit as new entry

Attachment 1:	project_description.pdf
Attachment 2:	project_summary.pdf
Attachment 3:
Drop attachments here...

ELOG V3.1.5-fc6679b