Those doing active research in the AI group should have accounts and home directories on the AI group machines.  This AI home directory will be different than your CS dept student home directory on agate (if you have one). Be sure to set up email forwarding if you need to.  We use NIS to coordinate passwd and group info across the AI machines, so if you want to change your password, use yppasswd, and if you want to change your shell, use ypchsh. If we need to reboot a machine to install a patch and you are logged in, we will try to contact you, so please make sure your location and phone number are updated using the ypchfn command.

 

Group stuff is available in /home/aifs2/group.   If you accidentally delete a file, check out /home/aisnaps to retrieve a backup copy.  Snapshots are taken every 12 hours (noon and midnight) and kept for various lengths of time.

 

If you need to lookup someone's phone number to contact them, try "group/bin/finger <loginid>".

 

If you are having trouble setting up public key login for SSH, try this fix.

 

Robotics is covered on its own page.

 

AI group machines

 

All are running 64-bit Ubuntu.

 

Please check system activity with the `top' command before starting experiments.  If someone else is running a job, please use a different machine.  The simplest way to run experiments across multiple machines is just to have a seperate terminal, emacs, and ocaml toplevel for each machine. If you find a better way, please post it!

 

Desktops

For all development, general use, and quick pilot experiments.  Although desktops are usually assigned to specific people, they are still a shared resource - you may ssh into any desktop and use it, as long as you do not interfere in any way with the main interactive user.  This means using at most half the RAM, using at most half the cores, and using the nice -n 19 command for long-running jobs to ensure that your process only uses spare cycles.  If the main user installs patches and wants to reboot, they should try to reach you first (you have your current cell number updated using ypchfn, right?), but if they can't reach you, they will reboot anyway.  If a "spare" desktop is listed, you should probably prefer that one for remote login, since it is less likely to get rebooted.

 

If you have an AI desktop, please be sure to keep your machine up-to-date with the latest Ubuntu patches, and check for other users before rebooting! 

• corona.cs - Bryan's desktop, Precision T7910, dual Xeon E5-2637v3 3.5GHz (quad core), 32GB DDR4-2133 RAM, nVidia GTX 760, dual 27" WQHD monitors 
• byodoin.cs - Devin's desktop, same as corona (or hydra?)
• zelinka.cs - Steve's desktop, same as corona
• aerials.cs - same as corona, curently offline
• katsura.cs - Wheeler's desktop, System76 Thelio Mira, i5-13600K (`Raptor Lake'), 32 GB DDR4 RAM, nVidia RTX 3060

 

Inactive:

• old katsura - Optiplex 990, Core i5 2400 3.1GHz (quad core), 8GB DDR3 RAM, ATI FirePro MV 2460

 

Not ours:

• hydra.cs - Madison's desktop, same as corona but nVidia GTX 960 
• kraken.cs - Bahram' desktop - same as hybra (or corona?)

 

 

Compute servers

Only for running heavy experiments.  Not for random login. It is important to run only one program at a time on each machine in order to get accurate CPU time measurements, even on a multi-core system.

• ai1-15.cs - AI group compute servers.  These are the machines to use for testing single-threaded algorithms. Optiplex 3000, Intel i3-12100 (`Alder Lake'), 64GB DDR4 RAM
• ais1-6.cs - spare AI group compute server.   Optiplex 960, Core2 duo E8500 3.16 GHz, 8GB RAM

To use them, see slurm

 

Multicore compute servers: please use only if you need multiple cores for a single program, lots of disk, or more RAM than an aiX machine.

• shugakuin.cs - PowerEdge T710, dual quad-core Xeon X5550 (Nehalem `Gainestown') 2.66Ghz, 48GB RAM (1333MHz), disks: 160 (boot), 7x1TB (WD RE3 drives on PERC 6/i hardware RAID).  Disks individually mounted at /srv/local/a-g.  Let Wheeler know if you want hardware RAID.
• scylla.cs - PowerEdge T710, dual 6-core Xeon X5660 (Westmere `Gulftown', aka `Westmere-EP') 2.8GHz, 12GB RAM (1333MHz), disks: 160 (boot), 12x320 (WD Scorpio Black drives on PERC H700 RAID.)  Disks individually mounted at /srv/local/a-l.  Let Wheeler know if you want hardware RAID.
• charybdis.cs - same as scylla

 

Service servers

Not for general login use.

File servers:

• thoth.cs - PowerEdge T620, Xeon E5-2620 (6 cores, 2.0GHz), 20GB DDR3 RAM, disks via PERC H710 RAID: 500GB (boot), 2x6TB WD RE4 (RAID 1 aifs), 3x2TB WD RE Gold (RAID 1 aisnaps).  Also serves NIS.
• ziz.iol - remote back-up.  Vostro 420, Core2 quad Q6600 2.4Ghz, 4GB RAM, ATI Radeon HD 3450, 80GB and 6TB disks.

spare:

• behemoth.cs - same as ziz except disks.  failed?

Retired

• legion.cs - AI group multi-core compute server: Sun T5440 with 4 1.2GHz T2+ processors (8 cores per processor, 8 threads per core), 64 Gb RAM, serial console to ai3

 

 

IDA* performance versus SPEC int 2006 base benchmark

 

 

 

CS dept servers

 

General-purpose research compute servers

Using these machines for real experiments is discouraged unless you are very careful, since CPU timing can get thrown off by other users' jobs.  Also, they use a separate filesystem.

• c00.cs - four 15-core processors, 1 TB RAM 
• c0.cs - R900 (four socket mobo), dual six-core Xeon X7460 (Core `Dunnington') 2.66GHz, 32Gb RAM, 1 300Gb SAS disk (PERC 6/i)
• c1.cs, c2.cs - dual quad-core Xeon E5320 1.86GHz, 16Gb RAM
• c3.cs - dual quad-core Xeon E5450 3.0 Ghz, 16Gb RAM
• c4.cs - dual-core PentiumD 3.2GHz, 4Gb RAM 

All are running 64-bit Fedora.

ccluster@cs is the mailing list for coordinating their use. Send email before any long-running batches or periods of heavy use.

 

Other servers

Not for heavy experiments!

• agate.cs is the student file server and general use machine. dual quad-core Xeon E5450 3.0 GHz, 16 Gb RAM, 32-bit Fedora.
• lava.cs is the faculty/admin file server and general use machine.
• mica.cs is the faculty research file server.

 

Random 32-bit desktops: hickory, cherry, oak, chert?

 

CIS servers

 

Working at CIS is discouraged since they have a separate filesystem. 

• gauss.unh - dual quad-core Xeon 2.66GHz, 4Gb RAM, 64-bit RHEL
• zeno.unh - dual-core Xeon 3.8GHz, 4Gb, 32-bit RHEL
• euler.unh - dual-core Xeon 3.6GHz, 2Gb, 32-bit RHEL

See here for more info on the public-use CIS servers.

 

---

 

Code

We've got a lot of domains and solvers already implemented, so chances are if you want to do work on a specific problem, you can start working pretty quickly

 

Domains:

Directory	Domain Name	Condition
antic-grocery	Anticipatory Grocery Planner	Unknown
dyn_robot	Dynamic Robot Path Planning	Unknown
grid	Gridword Pathfinding	Working
msa	Multiple Sequence Alignment	Broken
tiles	Sliding Tile Puzzle	Working
topspin	Topspin Game	Unknown
tplan	Temporal Planning	Working
tsp	Travelling Salesman Problem	Working

 

Solvers:

There are many, many heuristic search algorithms which all have different strengths and weaknesses.  We have the following on hand:

Algorithm	Directory	Condition
A*	shortest_path	Working
Iterative Deepening A*	bounded_depth	Working
Greedy Search	shortest_path	Working
Speedy Search	shortest_path	Working
A* epsilon	bugsy	Working
weighted A*	shortest_path	Working
Dynamically Weighted A*	shortest_path	Working
Optimistic Search	george	Needs Optimizing
Alpha A*	shortest_path	Needs Optimizing
A epsilon	shortest_path	Needs Optimizing
Anytime Heuristic Search	bugsy	Working
Anytime Repairing A*	bugsy	Unknown
BUGSY	bugsy	Unknown
Clamped Adaptive Search	george	Working

 

 

Problems

Domains and solvers aren't interesting without problems to solve.

Domain	Directory	Description
Grid	uniform	Grids with Uniform Obstacle Distribution
Grid	uniform_region	Grids where a rectangular sub-region has uniformly distributed obstacles
Grid	lines	Grids with lines drawn across them
Grid	game	Grids from popular real time strategy and roleplaying games
Grid	benchmark	Large Uniform Obstacle Grids, used for benchmarking machines
MSA	morphed
MSA	real	Real Sequences
Tiles	huge	Really Big Sliding Tile Problems
Tiles	korf	All 100 instances from Korf's paper on IDA*
Tiles	korf_25_easy	The 25 Easiest instances of the Korf instances
Tiles	korf_easy
Tiles	Random	Randomly Generated Problems
Temporal Planning	blocksworld	Stack and unstack blocks on a table
Temporal Planning	logistics	Shipping things between places, making sure they arrive on time.
Temporal Planning	rovers	Mission planning for rovers
Temporal Planning	satellite	Mission planning for a satellite
Temporal Planning	zenotravel	Travel using many means of conveyance
Travelling Salesman	pkhard	Instances similar to those used in Pearl and Kim's paper
Travelling Salesman	usquare	Going from A to B and B to A have the same cost.