<?xml version="1.0" encoding="ISO-8859-1"?>
<rss version="2.0">
<channel>
<title>ELOG How-To</title>
<link>http://as-phy-radiorm.asc.ohio-state.edu/elog/How-To</link>
<description>Place to document instructions for how to do things</description>
<generator>ELOG V3.1.5</generator>
<image>
<url>http://as-phy-radiorm.asc.ohio-state.edu/elog/How-To/elog.png</url>
<title>ELOG How-To</title>
<link>http://as-phy-radiorm.asc.ohio-state.edu/elog/How-To</link>
</image>
<item>
<title>Jacob Weiler, How to install AraSim on OSC, Software</title>
<link>http://as-phy-radiorm.asc.ohio-state.edu/elog/How-To/50</link>
<description>
&lt;p&gt;# Installing AraSim on OSC&lt;/p&gt;

&lt;p&gt;Readding this because I realized it was deleted when I went looking for it &lt;img alt=&quot;laugh&quot; height=&quot;23&quot; src=&quot;https://as-phy-radiorm.asc.ohio-state.edu/elog/ckeditor/plugins/smiley/images/teeth_smile.png&quot; title=&quot;laugh&quot; width=&quot;23&quot; /&gt;&lt;/p&gt;

&lt;p&gt;Quick Links:&lt;br /&gt;
- https://github.com/ara-software/AraSim # AraSim github repo (bottom has installation instructions that are sort of right)&lt;br /&gt;
- Once AraSim is downloaded: AraSim/UserGuideTex/AraSimGuide.pdf (manual for AraSim) might have to be downloaded if you can&amp;#39;t view pdf&amp;#39;s where you write code&lt;/p&gt;

&lt;p&gt;Step 1:&amp;nbsp;&lt;br /&gt;
We need to add in the dependancies. AraSim needs multiple different packages to be able to run correctly. The easiest way on OSC to get these without a headache is to add the following to you .bashrc for your user.&lt;/p&gt;

&lt;p&gt;cvmfs () {&lt;br /&gt;
&amp;nbsp; &amp;nbsp; module load gnu/4.8.5&lt;br /&gt;
&amp;nbsp; &amp;nbsp; export CC=`which gcc`&lt;br /&gt;
&amp;nbsp; &amp;nbsp; export CXX=`which g++`&lt;br /&gt;
&amp;nbsp; &amp;nbsp; if [ $# -eq 0 ]; then&lt;br /&gt;
&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; local version=&amp;quot;trunk&amp;quot;&lt;br /&gt;
&amp;nbsp; &amp;nbsp; elif [ $# -eq 1 ]; then&lt;br /&gt;
&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; local version=$1&lt;br /&gt;
&amp;nbsp; &amp;nbsp; else&lt;br /&gt;
&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; echo &amp;quot;cvmfs: takes up to 1 argument, the version to use&amp;quot;&lt;br /&gt;
&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; return 1&lt;br /&gt;
&amp;nbsp; &amp;nbsp; fi&lt;br /&gt;
&amp;nbsp; &amp;nbsp; echo &amp;quot;Loading cvmfs for AraSim&amp;quot;&lt;br /&gt;
&amp;nbsp; &amp;nbsp; echo &amp;quot;Using /cvmfs/ara.opensciencegrid.org/${version}/centos7/setup.sh&amp;quot;&lt;br /&gt;
&amp;nbsp; &amp;nbsp; source &amp;quot;/cvmfs/ara.opensciencegrid.org/${version}/centos7/setup.sh&amp;quot;&lt;br /&gt;
&amp;nbsp; &amp;nbsp; #export JUPYTER_CONFIG_DIR=$HOME/.jupyter&lt;br /&gt;
&amp;nbsp; &amp;nbsp; #export JUPYTER_PATH=$HOME/.local/share/jupyter&lt;br /&gt;
&amp;nbsp; &amp;nbsp; #export PYTHONPATH=/users/PAS0654/alansalgo1/.local/bin:/users/PAS0654/alansalgo1/.local/bin/pyrex:$PYTHONPATH&lt;br /&gt;
}&lt;/p&gt;

&lt;p&gt;&lt;br /&gt;
If you want to view my bashrc&lt;br /&gt;
- /users/PAS1977/jacobweiler/.bashrc&lt;/p&gt;

&lt;p&gt;Reload .b</description>
<pubDate>
Wed, 12 Jun 2024 12:10:05 -0400</pubDate>
</item>
<item>
<title>Jason Yao, How to profile a C++ program, Software</title>
<link>http://as-phy-radiorm.asc.ohio-state.edu/elog/How-To/49</link>
<description>
&lt;p&gt;This guide is modified from section (d) of the worksheet inside&amp;nbsp;Module 10&amp;nbsp;of Phys 6810 Computational Physics (Spring 2023).&lt;/p&gt;

&lt;p&gt;NOTE:&amp;nbsp;gprof does&amp;nbsp;&lt;strong&gt;not&lt;/strong&gt;&amp;nbsp;work on macOS. Please use a linux machine (such as OSC)&lt;/p&gt;

&lt;p&gt;To use gprof, compile and link the relevant codes with the&amp;nbsp;&lt;strong&gt;-pg&lt;/strong&gt;&amp;nbsp;option:&lt;br /&gt;
Take a look at the Makefile&amp;nbsp;&lt;strong&gt;make_hello_world&lt;/strong&gt;&amp;nbsp;and modify both the&amp;nbsp;&lt;strong&gt;CFLAGS&lt;/strong&gt;&amp;nbsp;and&amp;nbsp;&lt;strong&gt;LDFLAGS&lt;/strong&gt;&amp;nbsp;lines to include&amp;nbsp;&lt;strong&gt;-pg&lt;/strong&gt;&lt;br /&gt;
&lt;br /&gt;
Compile and link the script by typing&lt;br /&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;make -f make_hello_world&lt;/p&gt;

&lt;p&gt;Execute the program&lt;br /&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;./hello_world.x&lt;/p&gt;

&lt;p&gt;With the &lt;strong&gt;-pg&lt;/strong&gt;&amp;nbsp;flags, the execution&amp;nbsp;will generate&amp;nbsp;a file called&amp;nbsp;&lt;strong&gt;gmon.out&lt;/strong&gt;&amp;nbsp;that is used by gprof.&lt;br /&gt;
The program has to exit normally&amp;nbsp;(e.g. we can&amp;#39;t stop with a ctrl-C).&lt;br /&gt;
&lt;strong&gt;Warning:&amp;nbsp;&lt;/strong&gt;Any existing gmon.out file will be overwritten.&lt;/p&gt;

&lt;p&gt;Run gprof and save the output to a file (e.g., gprof.out) by&lt;br /&gt;
&amp;nbsp; &amp;nbsp; gprof hello_world.x &amp;gt; gprof.out&lt;/p&gt;

&lt;p&gt;We should at this point see a text file called &lt;strong&gt;gprof.out&lt;/strong&gt; which contains the profile of hello_world.cpp&lt;br /&gt;
&amp;nbsp;&amp;nbsp; &amp;nbsp;vim gprof.out&lt;/p&gt;</description>
<pubDate>
Thu, 14 Sep 2023 22:30:06 -0400</pubDate>
</item>
<item>
<title>Alan Salcedo , Doing IceCube/ARA coincidence analysis, </title>
<link>http://as-phy-radiorm.asc.ohio-state.edu/elog/How-To/48</link>
<description>
&lt;p&gt;These documents contain information on how to run IceCube/ARA coincidence simulations and analysis. All technical information of where codes are stored and how to use them is detailed in the technical note. Other supportive information for physics understanding is in the powerpoint slides. The technical note will direct you to other documents in this elog in the places where you may need supplemental information.&lt;/p&gt;</description>
<pubDate>
Thu, 08 Jun 2023 16:29:45 -0400</pubDate>
</item>
<item>
<title>William Luszczak, PUEO simulation stack installation instructions, Software</title>
<link>http://as-phy-radiorm.asc.ohio-state.edu/elog/How-To/47</link>
<description>
&lt;p&gt;These are instructions I put together as I was first figuring out how to compile PueoSim/NiceMC. This was originally done on machines running CentOS 7, however has since been replicated on the OSC machines (running RedHat 7.9 I think?). I generally try to avoid any `module load` type prerequisites, instead opting to compile any dependencies from source. You _might_ be able to get this to work by `module load`ing e.g. fftw, but try this at your own peril.&lt;/p&gt;

&lt;p&gt;#pueoBuilder Installation Tutorial&lt;/p&gt;

&lt;p&gt;This tutorial will guide you through the process of building the tools included in pueoBuilder from scratch, including the prerequisites and any environment variables that you will need to set. This sort of thing is always a bit of a nightmare process for me, so hopefully this guide can help you skip some of the frustration that I ran into. I did not have root acces on the system I was building on, so the instructions below are what I had to do to get things working with local installations. If you have root access, then things might be a bit easier. For reference I&amp;#39;m working on CentOS 7, other operating systems might have different problems that arise.&amp;nbsp;&lt;/p&gt;

&lt;p&gt;##Prerequisites&lt;br /&gt;
As far as I can tell, the prerequisites that need to be built first are:&lt;/p&gt;

&lt;p&gt;-Python 3.9.18 (Apr. 6 2024 edit by Jason Yao, needed for ROOT 6.26-14)&lt;br /&gt;
-cmake 3.21.2 (I had problems with 3.11.4)&lt;br /&gt;
-gcc 11.1.0 (9.X will not work) (update 4/23/24: If you are trying to compile ROOT 6.30, you might need to downgrade to gcc 10.X, see note about TBB in &amp;quot;Issues I ran into&amp;quot; at the end)&lt;br /&gt;
-fftw 3.3.9&lt;br /&gt;
-gsl 2.7.1 (for ROOT)&lt;br /&gt;
-ROOT 6.24.00&lt;br /&gt;
-OneTBB 2021.12.0 (if trying to compile ROOT 6.30)&lt;/p&gt;

&lt;p&gt;###CMake&lt;br /&gt;
You can download the source files for CMake here: https://cmake.org/download/. Untar the source files with:&lt;/p&gt;

&lt;p&gt;&amp;nbsp; &amp;nbsp; tar -xzvf cmake-3.22.1.tar.gz&lt;/p&gt;

&lt;p&gt;Compiling CMake is as easy as following the directions on the website: https://cmake.org/instal</description>
<pubDate>
Mon, 24 Apr 2023 11:51:42 -0400</pubDate>
</item>
<item>
<title>Alex M, OSC License Request, </title>
<link>http://as-phy-radiorm.asc.ohio-state.edu/elog/How-To/46</link>
<description>
&lt;p&gt;Some programs on OSC require authorized access to use in the form of a &lt;strong&gt;license&lt;/strong&gt;. The license will be automatically read if it is available whenever you open a program on OSC, provided you have access to the license. In order to have access to a license, you need to fill out the attached form and send it to Amy to forward to OSC. Available programs (at least some of) which require a license can be found here:&amp;nbsp;https://www.osc.edu/resources/available_software/software_list . Replace the name of the program at the top of the form with the desired software.&lt;/p&gt;</description>
<pubDate>
Tue, 02 Aug 2022 14:34:15 -0400</pubDate>
</item>
<item>
<title>William Luszczak, &quot;Help! AnitaBuildTools/PueoBuilder can't seem to find FFTW!&quot;, Software</title>
<link>http://as-phy-radiorm.asc.ohio-state.edu/elog/How-To/45</link>
<description>
&lt;p&gt;Disclaimer: This might not be the best solution to this problem. I arrived here after a lot of googling and stumbling across this thread with a similar problem for an unrelated project: https://github.com/xtensor-stack/xtensor-fftw/issues/52. If you&amp;#39;re someone who actually knows cmake, maybe you have a better solution.&lt;/p&gt;

&lt;p&gt;When compiling both pueoBuilder and anitaBuildTools, I have run into a cmake error that looks like:&lt;/p&gt;

&lt;pre&gt;
&lt;code&gt;CMake Error at /apps/cmake/3.17.2/share/cmake-3.17/Modules/FindPackageHandleStandardArgs.cmake:164 (message):
  Could NOT find FFTW (missing: FFTW_LIBRARIES)&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;(potentially also missing FFTW_INCLUDES). Directing CMake to the pre-existing FFTW installations on OSC does not seem to do anything to resolve this error. From what I can tell, this &lt;em&gt;might &lt;/em&gt;be related to how FFTW is built, so to get around this we need to build our own installation of FFTW using cmake instead of the recommended build process. To do this, grab the whatever version of FFTW you need from here: http://www.fftw.org/download.html (for example, I needed 3.3.9). Untar the source file into whatever directory you&amp;#39;re working in:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;&amp;nbsp; &amp;nbsp; tar -xzvf fftw-3.3.9.tar.gz&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Then make a build directory and cd into it:&lt;br /&gt;
&amp;nbsp; &amp;nbsp;&amp;nbsp;&lt;br /&gt;
&lt;code&gt;&amp;nbsp; &amp;nbsp; mkdir install&lt;br /&gt;
&amp;nbsp; &amp;nbsp; cd install&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;Now build using cmake, using the flags shown below.&lt;/p&gt;

&lt;p&gt;&lt;code&gt;&amp;nbsp; &amp;nbsp; cmake -DCMAKE_INSTALL_PREFIX=$(path_to_install_loc) -DBUILD_SHARED_LIBS=ON -DENABLE_OPENMP=ON -DENABLE_THREADS=ON ../fftw-3.3.9&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;For example, I downloaded and untarred the source file in `/scratch/wluszczak/fftw/`, and my install prefix was `/scratch/wluszczak/fftw/install/`. In principle this installation prefix can be anywhere you have write access, but for the sake of organization I usually try to keep everything in one place.&lt;/p&gt;

&lt;p&gt;Once you have configured cmake, go ahead and install:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;&amp;nbsp; &amp;nbs</description>
<pubDate>
Fri, 04 Feb 2022 13:06:25 -0500</pubDate>
</item>
<item>
<title>Keith McBride, NASA Proposal fellowships, Other</title>
<link>http://as-phy-radiorm.asc.ohio-state.edu/elog/How-To/42</link>
<description>
&lt;p&gt;Here is a useful link for astroparticle grad students related proposals from NASA:&lt;/p&gt;

&lt;p&gt;&amp;nbsp;&lt;/p&gt;

&lt;p&gt;https://nspires.nasaprs.com/external/solicitations/summary.do?solId=%7BE16CD59F-29DD-06C0-8971-CE1A9C252FD4%7D&amp;amp;path=&amp;amp;method=init&lt;/p&gt;

&lt;p&gt;Full email I received regarding this information was:&lt;/p&gt;

&lt;p&gt;_______________________________________________________________________________________________________________________________________________________________________________________________________________________________________________&lt;/p&gt;

&lt;p&gt;&lt;span style=&quot;color:black; font-family:arial,sans-serif; font-size:11.0pt&quot;&gt;ROSES-19 Amendment adds a new program element to ROSES-2019: &lt;/span&gt;&lt;span style=&quot;font-family:arial,sans-serif; font-size:11.0pt&quot;&gt;&lt;a href=&quot;https://nspires.nasaprs.com/external/solicitations/summary.do?solId=%7BE16CD59F-29DD-06C0-8971-CE1A9C252FD4%7D&amp;amp;path=&amp;amp;method=init&quot; rel=&quot;noopener noreferrer&quot; target=&quot;_blank&quot;&gt;Future Investigators in NASA Earth and Space Science and Technology (FINESST), the ROSES Graduate Student Research Program Element, E.6&lt;/a&gt;.&lt;/span&gt;&lt;/p&gt;

&lt;p style=&quot;margin-right:.5in&quot;&gt;&lt;strong&gt;&lt;span style=&quot;font-family:arial,sans-serif; font-size:11.0pt&quot;&gt;&amp;nbsp;&lt;/span&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;span style=&quot;color:black; font-family:arial,sans-serif; font-size:11.0pt&quot;&gt;Through FINESST, the &lt;/span&gt;&lt;span style=&quot;font-family:arial,sans-serif; font-size:11.0pt&quot;&gt;Science Mission Directorate (SMD) solicits proposals&lt;span style=&quot;color:black&quot;&gt; from accredited U.S. universities and other eligible organizations for graduate student-designed and performed research projects that contribute to SMD&amp;#39;s science, technology and exploration goals.&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;&lt;span style=&quot;font-family:arial,sans-serif; font-size:11.0pt&quot;&gt;&amp;nbsp;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;&lt;span style=&quot;color:black; font-family:arial,sans-serif; font-size:11.0pt&quot;&gt;A Notice of Intent is not requested for E.6 FINESST. Proposals to FINESST are due by &lt;/span&gt;&lt;span style=&quot;font-family:arial,sans-serif; font-size:11.0pt&quot;&gt;February 4, 2020.</description>
<pubDate>
Tue, 05 Nov 2019 16:22:16 -0500</pubDate>
</item>
<item>
<title>Amy , How to start a new undergrad hire, Other</title>
<link>http://as-phy-radiorm.asc.ohio-state.edu/elog/How-To/41</link>
<description>
&lt;p&gt;If an undergrad has been working with the group on a volunteer basis, they will need that clarified, so that they have not up to then we working for pay without training. &amp;nbsp;There is a form that they sign saying they have been working as a volunteer.&lt;/p&gt;

&lt;p&gt;Below is an email that Pam sent in July 2019 outlining what they need. &amp;nbsp;Other things to remember:&lt;/p&gt;

&lt;p&gt;Undergrads receive emails&amp;nbsp;from the department&amp;nbsp;to remind them about orientation and scheduling prior to first day of hire,&amp;nbsp;and other emails from ASC. They receive more&amp;nbsp;information&amp;nbsp;at orientation.&lt;/p&gt;

&lt;p&gt;They will need to show ID. &amp;nbsp;&lt;/p&gt;

&lt;p&gt;If an undergrad (or any hire) does not waive retirement/OPERs within 30 days, they will have to have this deducted from their paycheck. This is another reason that orientation is important.&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
For the person hiring them:&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
1. &amp;nbsp; &amp;nbsp; &amp;nbsp;Tell your admin (Lisa) asap who, when, etc you want to hire. ASAP is important because (Pam)&amp;nbsp;will process over 75 undergraduates hires in the Fall and over 100 in the summer. Each takes 20 days on average (see below)&lt;br /&gt;
2. &amp;nbsp; &amp;nbsp; &amp;nbsp;On the first day of employment &amp;ndash; ask your new hire if they have completed their orientation with the ASC.&lt;br /&gt;
&amp;nbsp;&lt;/p&gt;

&lt;p&gt;From: Hood, Pam&amp;nbsp;&lt;br /&gt;
Sent: Tuesday, July 23, 2019 4:49 PM&lt;br /&gt;
To: &amp;#39;physics-all@lists.osu.edu&amp;#39; &amp;lt;physics-all@lists.osu.edu&amp;gt;&lt;br /&gt;
Subject: Undergraduate Fall Hires&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
Hello all,&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
Fall is almost upon us and I am working on having positions ready to fill as well as posting on the OSU student job site and Federal Work study job boards. In order to plan my workflow, if you would let me know:&lt;br /&gt;
&amp;nbsp;&lt;br /&gt;
1. &amp;nbsp; &amp;nbsp; &amp;nbsp;Approximately how many undergraduate student assistants you plan to hire and at what rate of pay. Our department&amp;rsquo;s current average rate of pay is $10.00 - $10.50/hour, however it does depend on the position. Range is $8.</description>
<pubDate>
Fri, 11 Oct 2019 13:43:35 -0400</pubDate>
</item>
<item>
<title>Dustin Nguyen, Advice (not mine) on writing HEP stuff , Other</title>
<link>http://as-phy-radiorm.asc.ohio-state.edu/elog/How-To/40</link>
<description>
&lt;p&gt;PDF of advice by Andy Buckley (U Glasgow)&amp;nbsp;on writing a HEP thesis (and presumably HEP papers too)&amp;nbsp;that was forwarded by John Beacom to the CCAPP mailing list&amp;nbsp;a few months back.&amp;nbsp;&lt;/p&gt;</description>
<pubDate>
Thu, 25 Jul 2019 16:50:43 -0400</pubDate>
</item>
<item>
<title>Justin Flaherty, Installing PyROOT for Python 3 on Owens, Software</title>
<link>http://as-phy-radiorm.asc.ohio-state.edu/elog/How-To/39</link>
<description>
&lt;p&gt;In order to get PyROOT working for Python 3, you must build ROOT with a flag that specifies Python 3 in the installation.&amp;nbsp; This method will create a folder titled&amp;nbsp;&lt;em&gt;root-6.16.00&amp;nbsp;&lt;/em&gt;in your current directory,&amp;nbsp;so organize things how you see fit.&amp;nbsp;Then the steps are relatively simple:&lt;/p&gt;

&lt;p style=&quot;margin-left:40px&quot;&gt;wget https://root.cern/download/root_v6.16.00.source.tar.gz&lt;br /&gt;
tar -zxf root_v6.16.00.source.tar.gz&lt;br /&gt;
cd root-6.16.00&lt;br /&gt;
mkdir obj&lt;br /&gt;
cd obj&lt;br /&gt;
cmake .. -Dminuit2=On -Dpython3=On&lt;br /&gt;
make -j8&lt;/p&gt;

&lt;p&gt;If you wish to do a different version of ROOT, the steps should be the same:&lt;/p&gt;

&lt;p style=&quot;margin-left:40px&quot;&gt;wget https://root.cern/download/root_v&amp;lt;version&amp;gt;.source.tar.gz&lt;br /&gt;
tar -zxf root_v&amp;lt;version&amp;gt;.source.tar.gz&lt;br /&gt;
cd root-&amp;lt;version&amp;gt;&lt;br /&gt;
mkdir obj&lt;br /&gt;
cd obj&lt;br /&gt;
cmake .. -Dminuit2=On -Dpython3=On&lt;br /&gt;
make -j8&lt;/p&gt;</description>
<pubDate>
Thu, 11 Jul 2019 10:05:37 -0400</pubDate>
</item>
</channel>
</rss>
