<html><body><div style="font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000"><div>I should've also included the documentation, from https://data.jlab.org/drupal/?q=node/43 :</div><div><br data-mce-bogus="1"></div><div><h2 class="rtejustify" style="margin-bottom: 0.5em; font-size: 1em; text-align: justify; color: rgb(0, 0, 0); font-family: Verdana, Arial, Helvetica, sans-serif; font-style: normal; font-variant: normal; letter-spacing: normal; line-height: 17.0240001678467px; orphans: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);" data-mce-style="margin-bottom: 0.5em; font-size: 1em; text-align: justify; color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-style: normal; font-variant: normal; letter-spacing: normal; line-height: 17.0240001678467px; orphans: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: #ffffff;">Compiler</h2><p style="margin: 0px; color: rgb(0, 0, 0); font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 12.1599998474121px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 17.0240001678467px; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);" data-mce-style="margin: 0px; color: #000000; font-family: Verdana, Arial, Helvetica, sans-serif; font-size: 12.1599998474121px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 17.0240001678467px; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: #ffffff;">Detailed notes on how ROOT was compiled is shown in the <span data-scayt_word="README_BOB" data-scaytid="15">README_BOB</span> file in the ROOT directory, e.g. /apps/root/5.34.13/<span data-scayt_word="README_BOB" data-scaytid="16">README_BOB</span>. I normally just used the default <span data-scayt_word="gcc" data-scaytid="17">gcc </span>compiler that was available at the time, but note that version 6.02.00 was compiled with <span data-scayt_word="gcc" data-scaytid="18">gcc</span> 4.8.2 which you can load by typing "module load gcc_4.8.2" on <span data-scayt_word="ifarm" data-scaytid="14">ifarm</span>.</p></div><div><br data-mce-bogus="1"></div><div>Sandy</div><div><br data-mce-bogus="1"></div><div>-----</div><div><br data-mce-bogus="1"></div><div data-marker="__QUOTED_TEXT__"><div style="font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000" data-mce-style="font-family: arial,helvetica,sans-serif; font-size: 12pt; color: #000000"><div>Hi Mark,<br></div><br><div>Note that for Root 6, gcc 4.8 is available for the farm systems although it is not the current default. You can load its module as below:<br></div><br><div>ifarm1401> module avail<br>------------------------------------------ /usr/share/Modules/modulefiles ------------------------------------------<br>dot module-cvs module-info modules null use.own<br><br>------------------------------------------------- /etc/modulefiles -------------------------------------------------<br>anaconda cuba gcc_4.8.2 gcc_4.9.2 java_1.7 maven3<br>ifarm1401> module load gcc_4.8.2<br>ifarm1401> gcc -v<br>Using built-in specs.<br>COLLECT_GCC=gcc<br>COLLECT_LTO_WRAPPER=/u/apps/gcc/4.8.2/bin/../libexec/gcc/x86_64-unknown-linux-gnu/4.8.2/lto-wrapper<br>Target: x86_64-unknown-linux-gnu<br>Configured with: ../gcc-4.8.2/configure --prefix=/apps/gcc/4.8.2 --with-gmp=/apps/gmp --with-mpfr=/apps/mpfr --with-mpc=/apps/mpc --enable-languages=c,c++,fortran<br>Thread model: posix<br>gcc version 4.8.2 (GCC)<br>ifarm1401><br></div><br><div>Regards,<br></div><div>Sandy<br></div><br><hr id="zwchr"><div><b>From: </b>"Mark Ito" <marki@jlab.org><br><b>To: </b>"GlueX Offline Software Email List" <halld-offline@jlab.org><br><b>Cc: </b>"Amber Boehnlein" <amber@jlab.org><br><b>Sent: </b>Thursday, July 23, 2015 12:10:07 PM<br><b>Subject: </b>[Halld-offline] Offline Software Meeting Minutes, July 22, 2015<br></div><br><div>Folks,<br>
<br>
Find the minutes below and at<br>
<br>
<a class="moz-txt-link-freetext" href="https://halldweb.jlab.org/wiki/index.php/GlueX_Offline_Meeting,_July_22,_2015#Minutes" target="_blank">https://halldweb.jlab.org/wiki/index.php/GlueX_Offline_Meeting,_July_22,_2015#Minutes</a><br>
<br>
-- Mark<br>
___________________________________________________<br>
<br>
<div id="globalWrapper">
<div id="column-content">
<div id="content" class="mw-body"> <span dir="auto"></span>GlueX
Offline Software Meeting<span class="mw-headline" id="Minutes">,
Minutes</span><br>
<div id="bodyContent" class="mw-body-content">
<div id="mw-content-text" dir="ltr" class="mw-content-ltr" lang="en">
<br>
Present:
<br>
<ul>
<li> <b>BlueJeans</b>: Kei Moriya</li>
<li> <b>CMU</b>: Curtis Meyer</li>
<li> <b>FSU</b>: Aristeidis Tsaris</li>
<li> <b>JLab</b>: Alex Barnes, Amber Boehnlein, Mark
Ito (chair), David Lawrence, Paul Mattione, Eric
Pooser, Matt Shepherd, Nathan Sparks, Simon Taylor,
Beni Zihlmann</li>
<li> <b>NU</b>: Sean Dobbs</li>
</ul>
<br>
Find a recording of this meeting at <a rel="nofollow" class="external free" href="https://bluejeans.com/s/8qJ6/" target="_blank">https://bluejeans.com/s/8qJ6/</a>
.
<br>
<br>
<span class="mw-headline" id="Announcements">Announcements</span><br>
<ol>
<li> <b><a rel="nofollow" class="external text" href="https://mailman.jlab.org/pipermail/halld-offline/2015-July/002081.html" target="_blank">Turning
the Fine-Mesh Field Map into a Resource</a></b>.
Sean led us through his email. Before this change the
fine-mesh map was computed on the fly if not present
and then stored in the current working directory. This
change allows the user to put the files in a single
configurable location. If there is no fine-mesh field
for a given field map file, the system falls back to
the old procedure.</li>
<li> <b>Moving the Plug-Ins</b>. We went over the
emails from <a rel="nofollow" class="external text" href="https://mailman.jlab.org/pipermail/halld-offline/2015-July/002084.html" target="_blank">Paul</a>
and <a rel="nofollow" class="external text" href="https://mailman.jlab.org/pipermail/halld-offline/2015-July/002091.html" target="_blank">Sean</a>.
David had to do some work to modify the SCons scheme
to build the plug-ins in their new location.</li>
<li> <b>Instructions for <a href="https://halldweb.jlab.org/wiki/index.php/Setting_Up_the_GlueX_Environment" title="Setting Up the GlueX Environment" target="_blank">Setting
Up the GlueX Environment</a></b>. Mark reminded us
about the wiki page he announced earlier. Paul has
recently added a list of environment variables that
the user might want to set that are not set by the
general use scripts.</li>
<li> <b>Nightly Builds Working from the Git
Repositories</b>. The scripts have been modified to
get the latest versions of HDDS and sim-recon using
Git. They use a local clone of the GitHub
repositories.</li>
<li> <b><a rel="nofollow" class="external text" href="https://mailman.jlab.org/pipermail/halld/2015-July/000252.html" target="_blank">SQL
Injection Vulnerability, Offline Monitoring Pages</a></b>.
A team from DOE probing for cyber security
vulnerabilities performed a successful <a rel="nofollow" class="external text" href="https://en.wikipedia.org/wiki/SQL_injection" target="_blank">SQL
injection</a> attack against a couple of the Offline
Monitoring CGI Python scripts. Justin had the scripts
fixed on the same day and they are back up and running
now.</li>
</ol>
<br>
<span class="mw-headline" id="Offline_Monitoring">Offline
Monitoring</span><br>
<br>
Kei gave a brief report:
<br>
<ul>
<li> The last launch was two Fridays ago.</li>
<li> The next launch is scheduled for this Friday.</li>
<li> He plans to run a hybrid system of SWIF and jproj
for this launch, taking advantage of SWIF's faster job
submission mechanism. He is working with Chris Larrieu
of SciComp on this.</li>
<li> For the launch after that he hopes to have
converted to an all-SWIF system.</li>
<li> He plans to give an update on the conversion
process and the final product at the next Offline
Meeting. His goal is to produce something that others
can use for their farm projects.</li>
</ul>
<br>
Sean reported that Marty Wise has fixed a problem on our
database server (hallddb.jlab.org) that was causing the
offline monitoring database access to hang. In the process
Marty identified some queries that could use some
optimization. Sean also mentioned that he and Justin are
looking into whether the database tables need to be
re-factored.
<br>
<br>
<span class="mw-headline" id="Spring_2015_Commissioning_Simulations">Spring 2015
Commissioning Simulations</span><br>
<br>
Sean gave the report. Mark has done a first pass through
running all of the jobs listed on the <a href="https://halldweb.jlab.org/wiki/index.php/Spring_2015_Commissioning_Simulations" title="Spring 2015 Commissioning Simulations" target="_blank">wiki page</a>.
He is filling in jobs that got stuck in bggen and
timed-out without producing output.
<br>
Sean planning to run the same monitoring jobs on these
files as is used in the offline monitoring jobs.
<br>
<br>
<span class="mw-headline" id="Geant4_Update">Geant4 Update</span><br>
<br>
David gave the update. He has extracted some of the key
classes from Richard's HDGeant4 repository and
incorporated them in the CPP simulation he has been
working on, in particular those that handle the geometry.
Right now execution is very fast, but he is not sure that
all of the material is seen by the generated particles. He
suspects there is some subtlety having to do with Geant4's
"parallel worlds" feature.
<br>
Beni asked if was possible to run HDGeant4 and pipe the
output to mcsmear. David told us that he thought that
problem has already been solved for HDGEANT, but he has
not tried it himself.
<br>
<br>
<span class="mw-headline" id="Mixing_Simulated_Events">Mixing
Simulated Events</span><br>
<br>
Sean described his work on mixing electromagnetic
background (EMB) events with hadronic events from bggen.
The hope is that time can be saved during simulation if
the EMB does not have to be generated for every event.
<br>
He got David's hddm_merge_events program running. The
program does not attempt to combine hits that are close in
time when doing the mixing. He did comparisons between
events that were generated with EMB in the standard way
(where combination is done) and events where pre-generated
EMB events were mixed with clean bggen events. In most
cases the agreement is pretty good, within a few percent
or better. The approach looks promising but there are
still some unanswered questions. See <a rel="nofollow" class="external text" href="https://halldweb.jlab.org/wiki/images/7/75/Sdobbs_OfflineMtg_EMBkgd_July2015.pdf" target="_blank">his
slides</a> for details.
<br>
We discussed using real EMB events rather than simulated
ones. This would likely give much more realistic simulated
events.
<br>
<ul>
<li> Currently, we could use pair spectrometer triggers
that we already have.</li>
<li> A dedicated random trigger would probably be
better. There is a question of whether or not it needs
to be synchronized with the machine RF.</li>
<li> Right now there is a practical difficulty: real
data is in EVIO format and the simulated events are in
HDDM format. The mixing program works when both
sources are HDDM. Sean and David will discuss a way
around this.</li>
</ul>
<br>
<span class="mw-headline" id="Conversion_from_Subversion_to_Git">Conversion from
Subversion to Git</span><br>
<br>
Mark summarized the conversion we did last week. In
particular he went over new items on the <a href="https://halldweb.jlab.org/wiki/index.php/Conversion_from_Subversion_to_Git" title="Conversion from Subversion to Git" target="_blank">wiki page</a>
documenting the process. Among the items he mentioned
were:
<br>
<ul>
<li> There is local copy of the Git repositories for
hdds and sim-recon on our group disk at JLab. These
are updated at noon and midnight and are now used to
support the nightly builds.</li>
<li> He posted some notes on the details of the
conversion process to serve as a guide for future
conversion efforts.</li>
</ul>
<br>
Sean asked about how we approach conversion of other
directories from Subversion to Git in the future. At one
point Mark proposed that we discuss any such conversion at
this meeting and have the group decide on a case-by-case
basis. We decided to adopt this as our policy.
<br>
<br>
<span class="mw-headline" id="ROOT_6">ROOT 6</span><br>
<br>
Beni has succeeded in building our software (under Ubuntu)
using ROOT 6. He has already checked in the necessary
changes to sim-recon. The system is still compatible with
ROOT 5; the code senses which version is being used. He
also had to make changes to JANA, but did not check those
changes into the JANA repository.
<br>
GCC version 4.8 is required. The JLab batch farm is at 4.4
so we cannot use ROOT 6 for large-scale production at the
Lab.
<br>
We thought we should go ahead and complete the work needed
to have a ROOT-6-compatible system. We will continue to
try and maintain compatibility with ROOT 5 so we don't
lock ourselves out of the JLab Farm.
<br>
<br>
<span class="mw-headline" id="Action_Item_Review">Action
Item Review</span><br>
<ol>
<li> Work out details of doing an HDDM/EVIO merge.</li>
<li> Complete work on changes to be compatible with ROOT
6.</li>
</ol>
</div>
<div class="printfooter">
Retrieved from "<a href="https://halldweb.jlab.org/wiki/index.php?title=GlueX_Offline_Meeting,_July_22,_2015&oldid=68832" target="_blank">https://halldweb.jlab.org/wiki/index.php?title=GlueX_Offline_Meeting,_July_22,_2015</a>"<br>
<br>
</div>
</div>
</div>
</div>
</div>
<br>_______________________________________________<br>Halld-offline mailing list<br>Halld-offline@jlab.org<br>https://mailman.jlab.org/mailman/listinfo/halld-offline<br></div></div><br>_______________________________________________<br>Halld-offline mailing list<br>Halld-offline@jlab.org<br>https://mailman.jlab.org/mailman/listinfo/halld-offline<br></div></div></body></html>