From Earlham Cluster Department

(Difference between revisions)
Jump to: navigation, search
Line 26: Line 26:
== Notes ==
== Notes ==
* <code>. /cluster/software/</code> gets it working
* <code>. /cluster/software/</code> gets it working
* <code>/cluster/software/modules</code> is where the actual configuration files for each module (ie each piece of software) is stored in text files
* <code>/cluster/software/modules-sw</code> is where the common source code gets installed to (not bobsced-specific)

Revision as of 16:58, 5 October 2009

Software build options

  ARCHPATH=`uname -s`/`/cluster/software/os_release`/`uname -p`

Multiple Repositories

That's still doable with multiple modules repositories. We can setup
meta-modules that don't actually point you at software but alter how
modules itself behaves. The master meta-module would prepend MODULEPATH
with (say) "/cluster/software/modules" for software that's the same
across all the clusters, and modules-bobsced would prepend MODULEPATH
with "/cluster/bobsced/software/modules". Just like with PATH, the first
hit within a module repository is used. If Perl is only in the master
software repository it'll be grabbed from there, but if OpenMPI is in
both it'll be grabbed from the bobsced repository since it comes before
the master repository.


Personal tools
this semester