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:49 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;"><p><strong><span style="font-size:20px">                                                        </span></strong><u><strong><span style="font-size:20px">General update</span></strong></u></p> <p>The following were the fixes we made to make AraSim run:</p> <p>(1) As of March, the loop breaks at AraSim. We have found that our program XFintoARA.py does not properly format the output in the form that AraSim is looking for (as an input). Jorge gave us a sample AraSim input file to help us edit XFintoARA.py so that it formats the file correctly. Note that we found white space is also must match in order for the format to be correct. </p> <p>Now that we have fixed this, AraSim now runs. Attached is the following sample Jorge gave us of the proper AraSim inputs. If needed, it's available to refer back to. </p> <p>(2) After correcting the AraSim input file formats (outputs of XFintoARA.py), we ran it. It failed to finish running after hours of run time. We found that we were using default input parameters for AraSim -- which wasn't triggering in a timely fashion. Once we edited the parameters, it ran successfully. <em>Note that this was not run within the loop. Confirmation of the full loop running has not been completed. </em></p> <p>The parameters of interest need to be edited in setup.txt. To see which file in AraSim I am referring to, please see the .txt file attached. Note that we will be editing the bash script to allow the user to change these input parameters there. The following <span style="color:#B22222">red lines</span> are what need to be set:</p> <p><em><span style="font-size:11px"><span style="color:#B22222">EXPONENT=21</span><br /> <span style="color:#B22222">NNU=100 // number of neutrino events<br /> NNU_PASSED=10 // number of neutrino events that are allowed to pass the trigger</span><br /> <span style="color:#B22222">ONLY_PASSED_EVENTS=1 // 0 (default): AraSim throws NNU events whether or not they pass; 1: AraSim throws events until the number of events that pass the trigger is equal to NNU_PASSED (WARNING: may cause long run times if reasonable values are not chosen)</span><br /> NOISE_WAVEFORM_GENERATE_MODE=0 // generate new noise waveforms for each events<br /> NOISE_EVENTS=16 // number of pure noise waveforms<br /> <span style="color:#B22222">TRIG_ANALYSIS_MODE=0 // 0 = signal + noise, 1 = signal only, 2 = noise only</span><br /> DETECTOR=1 // ARA stations 1 to 7<br /> NOFZ=1<br /> core_x=10000<br /> core_y=10000</span></em></p> <p><span style="color:#B22222">EXPONENT</span> gives the energy of the neutrinos. Note that higher energies will have more pass, as the energies don't dissipate as rapidly. For now, we are running at this energy. Eventally, we will want to use the full Kotera spectrum. Otherwsie, we would be finding the performance of an antenna at only one energy. Just to check the loop, we are going to use EXPONENT=21 to get events to trigger faster. </p> <p><span style="color:#B22222">ONLY_PASSED_EVENTS</span> decides which of the two options to use to determine when AraSim is finished running: (1) Throws '<span style="color:#B22222">NNU</span>' number of events at antennas and stops regardless of how many pass (in this case <span style="color:#B22222">ONLY_PASSED_EVENTS=0</span>) , or (2) throws as many events at the antenna as needed until '<span style="color:#B22222">NNU_PASSED</span>' number triggers (in this case <span style="color:#B22222">ONLY_PASSED_EVENTS=1</span>). Ie if this number is 10, we throw as many neutrinos at the antenna as necessary until 10 events trigger. Note that this can result in a longer run time. Additionally, a higher <span style="color:#B22222">EXPONENT</span> will make them trigger faster. </p> <p><span style="color:#B22222">TRIG_ANALYSIS_MODE</span> is a setting that determines what is being thrown. Ie- 0=signal + noise (which is what we want, and is the 'real' case), 1=signal only (would make it run faster), 2=noise only (not of interest for us). </p> <p><strong><span style="font-size:18px">       </span></strong></p> <p> </p> <p><strong><span style="font-size:18px">                                                                </span></strong><u><strong><span style="font-size:18px">To-Do List</span></strong></u></p> <p>(1) Commit version of XFintoARA.py since recent formatting change. </p> <p>(2) Figure out how to add in Kotera spectrum (note that we wont want to do this until the WHOLE loop is functional)</p> <p>(3) Edit the bash script to recreat the setup.txt making the variables in <span style="color:#B22222">red</span> above an editable option in the top of the bash script. Ie our variables in <span style="color:#B22222">red</span> above will be at the top of the bash script. Later in the bash script we will need to have it create this .txt file with the user inputs for those variables. We can do this by either (1) creating a skeleton, or (2) creating another .sh script that is run in our XFLoop.sh -- which writes the first handfull of lines based on the user inputs for our variables in <span style="color:#B22222">red</span> above, and then pastes in the rest of what is unchanged in setup.txt. </p> <p>(4) Run the whole loop: update- we tried this today and keep getting a Veff-0 for our first antenna along with the error </p> <p>Warning in <TFile::Init>: no StreamerInfo found in /datapool/software/anita/lib/G__RootFftwWrapper_rdict.pcm therefore preventing schema evolution when reading this file.<br /> Error in <TStreamerInfo::Build>: AraEventCalibrator, discarding: unsigned short* fAtriPeds, no [dimension]<br /> others run as expected</p> <p>(5) Work on the paper: Amy added a skeleton of sections to add for the GA. Date of completion should be in-line with APS. </p> <p>(6) APS talk slides. </p> <p>(7) Edit the manual and add: </p> <ul> <li>The changes that will occur when task (3) is done.</li> <li>A sample of how AraSim inputs -- or XFintoARA.py outputs -- should look. </li> <li>This stuff: <a href="http://radiorm.physics.ohio-state.edu/elog/GENETIS/8">http://radiorm.physics.ohio-state.edu/elog/GENETIS/8</a></li> <li>Max's AraSim plotting software (when it's done)</li> <li>Evelyn and Sophie's plotting software info (when it's done). </li> </ul> <p>(8) Finish Max's AraSim plotting software.</p> <p>(9) Finish Evenlyn and Sophie's plotting softare. </p></td> </tr> </tbody> </table> </p><p> </p> Encoding: HTML ELCode plain Suppress Email notification

Attachment 1:
Drop attachments here...

ELOG V3.1.5-fc6679b