Search results

own envset. This might be necessary to test code with a new compiler, or to test a new set of art libraries, or test a new verison of geant or other UPS product

stken # enstore $ ecrc -0 raw.mu2e.file_test.v0.000.art CRC 3565947252 # dCache $ ecrc -1 -h raw.mu2e.file_test.v0.000.art CRC 0xc9a20975 note the SCD systems

read FF; do ln -s $FF; done rm cd3 mkdir cd3 # continue with links and replacing with real files where needed # check that real files are there find /cvmfs/mu2e

gov\"))' " Another example: -l '+MU2E_TEST=true' --append_condor_requirements='(TARGET.MU2E_TEST==true)' Most jobs can be tested interactively, and they will run

and sometimes scripts are under test or text files used by the code are kept under data. Many directories don't need test or data - see the TrkReco directory

PORT:localhost:PORT <kerberos_username>@mu2egpvm04.fnal.gov notes: replace PORT with 5900+ID , replace mu2egpvm04 with the name of the machine where you started

hh" namespace mu2e { class DbServiceTest : public art::EDAnalyzer { private: mu2e::DbHandle<mu2e::TstCalib1> _testCalib1; }; }; in the event method, the

sets of tracking efficiency and resolution plots are: TrkDiag/test/KalFit.C TrkDiag/test/ce.C KalFit.C does all of the physics work; ce.C manages I/O and

with klist, run kinit <username>@FNAL.GOV to make a new one. Make sure to replace <username> with your FNAL username. Open a terminal and start an ssh tunnel

while free is used to deallocate. At line 114 (in BLEvaluator::evaluate() replace free(in); with delete[] in; There are numerous gcc 12 linter warnings, but

requests the tests be run. They also select which tests, if any, to run on this PR. Currently, the requirements for running tests are: 1) the build tests get run

you need to tag the branch to label a particular commit, perhaps for testing, replace the "branch" with the version of the tag. The version will start at

interfaces to the detector ROC prototypes that are available for slice testing. - learn how to connect and mockup different scenarios by connecting optical

Sandbox/src/BarService_service.cc Sandbox/src/XBarTest_module.cc Sandbox/test/footest.fcl Sandbox/test/bartest.fcl Sandbox/test/xbartest.fcl In the era of the conditions

files so I can tell if they run. We created two test files: /home/test1 which contains "printenv" /home/test2 which contains "#!/bin/bash \n printenv" shifter

until you kcrondestroy..) Tokens are a form of authentication intended to replace x509 certs in the process of authenticating grid job submission dCache reads

error codes Elastic Analysis Facility (EAF) Spack - setup and build tool to replace UPS and MRB SpackMaintenance - expert procedures and debugging Legacy_Access_to_SL7

TrkAna. 01/15/20 PR 104 Changes to the fcl files to allow the MT POT and g3test_03 configurations to run using the Mu2eG4MT module. 01/11/20 PR 103 Small

DAQ/src/SConscript - DAQ/src/TrkPacketProducer_module.cc - DAQ/test/PacketProducerTest_RootInput.fcl 2) Sept 21, 2018 Rob Kutsckhe GeneralUtilities/inc/csv

and sometimes scripts are under test or text files used by the code are kept under data. Many directories don't need test or data - see the TrkReco directory