Instructions for using the DCFaultFinder on JLab - mckunkel/DCFaultFinder GitHub Wiki

  • CLAS12 dependancies should be changed in the pom.xml file
  • As of writing this, the CLAS12 maven repository was up to date. However there was no software management tool available to ensure this projects CLAS12 dependencies stayed upto date. Therefore it is recommended that the pom.mxl file be changed to point to the latest CLAS12 COATJava needed to analyze data if CLAS12 does not update their Maven repository. See class12-offline-software for instructions on how to build the COATJava libraries.
  1. Clone the repository
  2. In the directory FaultFinder
    1. Update pom.xml to latest COATJava
    2. Execute the buildPackage.pl to build the package on the JLab cluster 
      1. ./buildPackage.pl
    3. Execute the runDCFaultFinder.pl to run the GUI 
      1. ./runDCFaultFinder.pl
  • If you are building the clas12-offline-software from source, the following is needed
  • Once COATJava is built
  • Run this command in the clas12-offline-software directory to install COATJava into your .m2 directory
mvn install:install-file -Dfile=coatjava/lib/clas/coat-libs-5.1-SNAPSHOT.jar -DgroupId=org.jlab.coat -DartifactId=coat-libs -Dversion=5.1-SNAPSHOT -Dpackaging=jar
  • Remove these lines from the pom.xml file located in the FaultFinder directory
<repositories>
<repository>
<id>clas12maven</id>
<url>https://clasweb.jlab.org/clas12maven</url>
</repository>
</repositories>
  • Rerun step 2

Questions? Feature Request? Bug Report? email: [email protected]

⚠️ **GitHub.com Fallback** ⚠️