CodeDepencyGraph: Difference between revisions

From Mu2eWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 6: Line 6:
  git clone ssh://p-mu2eofflinesoftwaremu2eoffline@cdcvs.fnal.gov/cvs/projects/mu2eofflinesoftwaremu2eoffline/Offline.git
  git clone ssh://p-mu2eofflinesoftwaremu2eoffline@cdcvs.fnal.gov/cvs/projects/mu2eofflinesoftwaremu2eoffline/Offline.git


<li>Remove files that unnecessarily complicate the picture.</li>
<li>Remove files that unnecessarily complicate the picture. This includes all modules, which natuallry all sit at the top dependence layer, and a few directories like Sandbox.  This does actual file deletes in the release...</li>
  #    Once upon a time I checked that everything would build if we
  #    Once upon a time I checked that everything would build if we
  source ~kutschke/LinkLoops/trim.sh
  source ~kutschke/LinkLoops/trim.sh

Revision as of 16:16, 22 October 2018

Instructions to make the code dependency graph on computing division machine woof.

  1. Clean checkout
  2. git clone ssh://p-mu2eofflinesoftwaremu2eoffline@cdcvs.fnal.gov/cvs/projects/mu2eofflinesoftwaremu2eoffline/Offline.git
  3. Remove files that unnecessarily complicate the picture. This includes all modules, which natuallry all sit at the top dependence layer, and a few directories like Sandbox. This does actual file deletes in the release...
  4. # Once upon a time I checked that everything would build if we source ~kutschke/LinkLoops/trim.sh
  5. Create the file that contains the dependency pairs
  6. cd Offline time /home/greenc/work/cet-is/sources/cetbuildtools/bin/code-dep-graph -v -o ../trimmed.dot >& ../trimmed.log
  7. Transitive reduction and create graph
  8. # This step issues a warning if 1 or more loops exist. # The loop is neither complete nor super informative tred trimmed.dot | dot -Tpng -o trimmed.png
  9. Create graph without transitive reduction - impossible to read
  10. dot trimmed.dot -Tpng -o trimmed_notred.png