Those doing active research in the AI group should have accounts and home directories on the AI group machines. Note that 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.

 

If you accidentally delete a file, check out /home/aisnaps1 or 2 (corresponding to whichever aifs your home directory is on) to retrieve a backup copy.  Snapshots are taken every 12 hours and kept for various lengths of time.

 

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!

 

Please check system activity with the `top' command before starting experiments.  If someone else is running a job, please use a different machine.  It is important to run only one process at a time on each machine in order to get accurate CPU time measurements, even on a multi-core system.  Please be sure not to approach the limit of physical RAM on the desktop machines, as they need to maintain interactive performance.

 

AI group machines

 

All are running 64-bit Ubuntu. Group stuff is available in /home/aifs2/group.  Note that 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. If you are having trouble setting up public key login for SSH, try this fix.

 

Desktops

For all development, general use, and quick pilot experiments.  Not for memory-hungry or long-running jobs unless you get main user's permission.  For remote login, prefer the "spare" desktop, since it is less likely to get rebooted.

• cypress.cs - Jordan's desktop, Optiplex 960, Core2 duo E8500 3.16 GHz, 8Gb RAM, ATI Radeon HD 3450 (rv620)
• soong.cs - Ethan's desktop, same as cypress
• yorishiro.cs - Seth's desktop, same as cypress but ATI Radeon HD 2400 XT (rv610)
• katsura.cs - Wheeler's desktop, same as yorishiro

• zelinka.cs - Chris' desktop, Optiplex 745, Core2 duo E6600 2.4GHz, 4Gb RAM, ATI x1300 (rv516)
• byodoin.cs - spare desktop, same as zelinka

If you have an AI desktop, please recognize that it is a shared resource and check for other users before rebooting!

 

Compute servers

Only for running heavy experiments.  Not for random login.  Be sure not to stomp on another user's jobs (use top!).  group/bin/rups will show load across all machines.

• ai1-5.cs - AI group compute servers. Optiplex 755, Core2 duo E8500 3.16GHz, 8Gb RAM
• ??.cs - AI group multi-core compute server.  PowerEdge T710, dual quad-core Xeon X5550 (Nehalem `Gainestown') 2.66Ghz, 48Gb RAM (1333MHz), disks: 160 (boot), 7x1Tb (hardware RAID)

 

File servers

Not for general login use.

• behemoth.cs - Vostro 420, Core2 quad Q6600 2.4Ghz, 4Gb RAM, disks: 80 (boot), 2x300Gb (data+mirror), 2x300Gb (snapshots). also ATI Radeon HD 3450.  Serves aifs1 and NIS.
• leviathan.cs - same as behemoth. serves aifs2.
• ziz.iol - remote back-up.  same as behemoth except disks: 80Gb and 1Tb

 

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

 

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.

• 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 3Ghz, 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, birch.  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.