Gridexport: Difference between revisions

Latest revision as of 18:14, 20 July 2024

This page is obsolete. Making tarballs of locally-built code is now done using Muse#Tarball.

This page will be deleted once we are sure that nothing links to it.

@@ Line 1: / Line 1: @@
-The ups package gridexport will export a build of Mu2e Offline or a build of a satellite release for use on a grid worker node.
+<font size=+2>This page is obsolete. Making tarballs of locally-built code is now done using [[Muse#Tarball]].</font>
-Until January 2018, the bluearc disk /mu2e/app was mounted on worker nodes on Fermigrid; it was possible to build code on that disk and run it on Fermigrid.  That is no longer possible.  If you have a build of Mu2e code on a computer that can see /pnfs/mu2e/scratch, then you can use gridexport to produce a bzipped tar file of your build area.  You can then submit a grid job that copies the bzipped tar file, unpacks it and runs the code that it finds inside.  In particular you can use gridexport on any of the mu2egpvm* machines to export a build that is located on /mu2e/app or in your home area.
+This page will be deleted once we are sure that nothing links to it.
-When you have exported code in this way, you can submit jobs to site in OSG; previously, if you were running a build on /mu2e/app you were restricted to running on Fermigrid, the only site that mounted that disk on its worker nodes.
-To use gridexport: