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 16:43:47 2026
Author
*
:
Subject
*
:
<p>Attendance: Julie, Evelyn, Mitchell, Ryan, Alex M.</p> <p>Since we have been having issues with the lack of availability of GPUs on OSC, we have come up with a new to-do list:</p> <ol> <li>Try to keep running on Pitzer with 1 core instead of 40. Based on first attempts, it is saying this will reduce wait times to ~3 hours (will vary based on usage), and after that 3 hours, human interaction will be needed. So the plan is, someone requests a job in the morning, and when the interactive job starts, the person is responsible for doing the thing which will allow the generation to run. We will aim for one generation per day under this plan, taking turns. Better than no evolving.</li> <li>I have asked Heechang at OSC if we can install the latest version of XF on Ruby and/or Owens. That would be better. There seems to be more available on Owens at least.</li> <li>Our initial attempt to run on Ruby is giving us an error which is probably to do with different inputs required in different versions. Will attempt to pursue this as a last resort, but the older version of XF does require lots more human interaction so until other options are exhausted it's not worth it.</li> </ol> <h2><u>Today's Tasks</u></h2> <p><strong>Mitchell: </strong>Worked on Python Project, learned to evolve (note: Mitchell may leave the group at the end of the semester)</p> <p><strong>Ryan:</strong> Starting the Python project</p> <p><strong>Evelyn:</strong> Finish bash project.</p> <p><strong>Julie: </strong>C++ project, look at Amy's proposal draft. </p> <p><strong>Alex M: </strong>Fix XF solver to submit each individual as a separate job (thus we can request a smaller wall time for each job)</p> <p> </p> <h2><strong><u>TO-DO List</u></strong></h2> <ol> <li><u>Scaling test run:</u> Do a test run to see if the scaling (when we also scale the grid spacing) actually affects the run time for XF. <ol> <li>We are going to pause on working on this, because we are struggling to get GPU time. We will test this whenever we see OSC less busy (ie if we log on at a lucky time). </li> </ol> </li> <li><u>Evolve</u>: Try to keep running on Pitzer with 1 core instead of 40. Based on first attempts, it is saying this will reduce wait times to ~3 hours (will vary based on usage), and after that 3 hours, human interaction will be needed. So the plan is, someone requests a job in the morning, and when the interactive job starts, the person is responsible for doing the thing which will allow the generation to run. We will aim for one generation per day under this plan, taking turns. Better than no evolving.</li> <li> <p dir="ltr"><u>Parallelize the AraActualBicone job.</u></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 parallelized. (ALEX M)</p> </li> <li> <p dir="ltr">As of 3/5, I have not gotten an update on this. I will check on the status of this. </p> </li> </ol> </li> <li> <p dir="ltr"><u>Comment code thoroughly (Everyone needs to help with this)</u></p> <ol> <li> <p dir="ltr"><u>​</u>Julie made some progress on this over the weekend. </p> <ol> <li> <p dir="ltr">Made comments on what each bash script version does, and cleaned up our directories from old code so that it doesn't confuse the others when they start helping </p> </li> </ol> </li> <li> <p dir="ltr">WAY more needs to still be done. </p> </li> </ol> </li> <li> <p dir="ltr"><u>Get new proposal results for March 12th deadline:</u></p> <ol> <li> <p dir="ltr"><u>​</u>Julie is looking at what Amy wrote <a href="https://docs.google.com/document/d/1J_26zhoipZeK1xmPW35Iw6QeUPNR6XPQZ5zCBcoXTFU/edit">here </a></p> </li> </ol> </li> </ol>
Encoding
:
HTML
ELCode
plain
Suppress Email notification
Attachment 1:
Drop attachments here...
Draft saved at 00:00:00
ELOG V3.1.5-fc6679b