MINOS Computing at the University of Minnesota
This page contains descriptions of the computing
facilities for MINOS collaborators at the University of Minnesota.
Document Contents
Computers
Printing
System Software
MINOS Software
Computers
There are currently nine MINOS computers, all running Redhat 7.3 with
linux kernel 2.4.18 and autofs cross mounting of each others drives.
- minos-server.hep.umn.edu (128.101.222.16)
- AMD Athlon XP 1500+
- RAM -- 512Mb
- 2 Hard Drives (hda = 120Gb, hdb = 160Gb)
- hda1 = 7.7Gb, / locally, not available on network
- hda2 = 25Gb, /export/home locally, /home/minos on network
- hda3 = 2.0Gb, swap partition
- hda5 = 60Gb, /local_data locally, /data/minos1 on network
- hdb1 = 160Gb, /local/data2 locally, /data/minos2 on network
- HP CD-Writer+ 8200 -- Burning CDs
- minos-pc1.hep.umn.edu (128.101.222.10)
- AMD Athlon XP 2100+
- RAM -- 512Mb
- 2 Hard Drives (hda = 120Gb, hdb = 120Gb)
- hda1 = 8.0Gb, / locally, not available on network
- hda2 = 2.0Gb, swap partition
- hda3 = 104Gb, /local/data1 locally, /data/minos2 on network
- hdb1 = 113Gb, /local/data2 locally, /data/minos2 on network
- minos-pc2.hep.umn.edu (128.101.222.11)
- AMD Athlon XP 2100+
- RAM -- 512Mb
- 3 Hard Drives (hda = 120Gb, hdb = 160Gb, hdd = 120Gb)
- hda1 = 8.0Gb, / locally, not available on network
- hda2 = 2.0Gb, swap partition
- hda3 = 106Gb, /local/data1 locally, /data/minos2 on network
- hdb1 = 147Gb, /local/data2 locally, /data/minos2 on network
- hdd1 = 113Gb, /local/data3 locally, /data/minos2 on network
- minos-pc3.hep.umn.edu (128.101.222.17)
- 800MHz AMD Athlon
- RAM -- 256Mb
- 2 Hard Drives (hda = 15Gb , hdb = 80Gb)
- hda1 = 3.0Gb, / locally, not available on network
- hda2 = 0.5Gb, swap partition
- hda3 = 11.5Gb, /local_data locally, /data/pc3 on network
- hdb3 = 54Gb, /local_data_bad locally, /data/pc3 on network
- hdb4 = 14Gb, /home_bad locally, /data/pc3 on network
- minos-pc4.hep.umn.edu (128.101.222.18)
- 800MHz AMD Athlon
- RAM -- 196Mb
- 2 Hard Drives (hda = 20Gb, hdb = 20Gb)
- hda1 = 3Gb, / locally, not available on network
- hda2 = 1Gb, swap partition
- hda3 = 16Gb, /local_data locally, /data/pc4 on network
- minos-pc5.hep.umn.edu (128.101.222.19)
Not currently operational
- urheim.hep.umn.edu (128.101.222.121)
- 1.3GHz AMD Athlon
- RAM -- 512Mb
- 2 Hard Drives (hda = 20Gb, hdb = 80Gb)
- hda1 = 3Gb, / locally, not available on network
- hda2 = 1Gb, swap partition
- hda3 = 16Gb, /local_data locally, /data/urheim on network
- hdb1 = 76Gb, /local_data2 locally, /data/urheim on network
- kasahara.hep.umn.edu (128.101.222.49)
- 500MHz Pentium III
- RAM -- 256Mb
- 1 Hard Drive (hda = 26Gb)
- hda1 = 3.0Gb, / locally, not available on network
- hda3 = 0.5Gb, swap partition
- hda5 = 5Gb, /export/home locally, /home/urheim on network
- hda6 = 4Gb, /local locally, /mnt/urusr on network
- hda7 = 13Gb, /local_data locally, /data/urheim1 on network
- speakman.hep.umn.edu (128.101.222.15)
Not currently operational
- gallagher.hep.umn.edu (128.101.222.128)
- 550MHz Pentium III
- RAM -- 256Mb
- 1 Hard Drive (hde = 20Gb)
- hde1 = 3Gb, / locally, not available on network
- hde2 = 0.5Gb, swap partition
- hde3 = 16.5Gb, /local_data locally, /data/gallagher on network
Each system can print to following printers, where the queue name is the room number.
| Queue Name |
Printer hostname |
Color? |
Duplex? |
| 246 |
clj2.spa.umn.edu |
yes |
no |
| 260 |
lj9.spa.umn.edu |
no |
yes |
| 216 |
lj10.spa.umn.edu |
no |
yes |
| 431 |
lj3.spa.umn.edu |
no |
no |
| 431c |
clj1.spa.umn.edu |
yes |
no |
| 153 |
lj153.spa.umn.edu |
no |
no |
| 155 |
lj155.spa.umn.edu |
no |
no |
To print to these here are a few commands which are handy:
- lpr -P[Queue Name] [filename]
- a2ps -P[Queue Name] [filename]
- -2 for two pages side-by-side on a page
- -s2 for duplex printing
- --borders=[on,off] turns on or off borders for side-by-side printing
- enscript -P [Queue] [text filename]
- -T [tabsize] to denote number of spaces in a tab
- -G for fancy formatting with title and page number header
- -r for landscape printing mode
- -2 for 2 pages per sheet
Each of these commands has several more options which can be found in there
man pages. There are a few handy aliases that wrap these commands located in
the file .myaliases placed in the home of all new users. If you are an old
user, .myaliases is located in /etc/skel/ on minos-server. If you are printing
by laptop through the physics network you can still print to these queues
through minos-server by replacing 'Queue Name' with 'Queue
Name'@minos-server.hep.umn.edu for network print services. This will not work
outside the Firewall that sits in front of the entire Physics Building.
System Software
I have installed several non-standard software items on all of these
machines that aren't directly related to MINOS code. I will only list
here those programs which aren't found on the Redhat 7.3 OS disks.
- Generic Installation
I have written simple script to build and install a product which
uses GNU autoconf and automake, called
generic_install.csh. This can either be modified for individual
packages, or read from environment variables the package
specifics.
| Variable |
Definition |
Default |
| BASE |
package-version |
testing-1.1 |
| BUILD_DIR |
top level build directory |
/local_data/bspeak/build |
| INSTALL_DIR |
installation directory |
/usr/local/ |
| TAR_DIR |
location of ${BASE}.tar.gz |
/data/minos1/bspeak/tarchive |
| LOG_DIR |
logging directory |
${BUILD_DIR}/${BASE}/log |
| CONFIG_OPTIONS |
options other than --prefix |
"" |
MINOS Software
- libsigc++
Install with the script
sigc_install.csh and the tar gzipped file libsigc++-1.2.5.tar.gz
- UPS/UPD
UPS (Unix Product Support) is a software toolkit developed by the
Fermilab computing division used to manage the multiple software
package distributions. For a complete description, look to the
Official FNAL UPS
site. In order to use UPS/UPD to download products from Fermi Lab
FTP accees, you must first register with computing division on this
internet
form. Once your system is registered to access FTP at FNAL, follow
up with installation instructions and
use instructions.
- Labyrinth
Labyrinth is the collaboration's current Fortran MC simulation and
reconstruction effort. Robert Hatcher, who has made significant
contributions to this effort, has an excellent
homepage
describing Labyrinth. Otherwise you can look at my pages on how to
install and how to
use labyrinth software on the UofMN
computers.
- Root
Root is on object-oriented analysis framework developed at CERN.
Please see the official web site
for complete information about root. The UofM computing of root is
described in how to install and how to
use root.
.
- Minossoft SRT
The MINOS collaboration is developing its analysis code as
object-oriented and based on the root framework. The distribution and
version control of this software is done with Fermilab product
SoftRelTools.
For a full description of the
Minossoft SRT
How to install and how to
use
- MINOS Data
In an effort to optimize the use of our hard drive space, I have
created a central storage area for MINOS data in
/data/pc2/root_data.
You can contact me at
bspeak@hep.umn.edu