to convert this to plain html, but I wanted to make sure that BOSSNODE
was expanded! We need some mechanism for dynamic content contained
within .html files. Hmm, maybe use shtml for stuff like this?

addresses of the interfaces used so that its easier to set the
accesspoint using link_config and tevc. It would be nice if we did the
mapping for the user (from lan0-node1 to MAC) but that would require
changes to the scheduler to look inside events, and I do not want to
got there yet.

agent was created for each link,link-vnode in a link/lan only when
that link has a delay/linkdelay. Well, with the link-agent that will
be used on wireless lans, lets just stick those agents into the table
for all links/lans in the experiment; its harmless. Might revisit this
at some point.

something we are continually being asked to do! This script will only
operate in UNAPPROVED users; once a user is approved it becomes too
difficult to deal with cause of existing directories which might be
exported to active experiments. We can probably deal with this, but we
rarely do this to an approved user, so its not a big deal.

Obvious: This script can get out of sync with the DB, but of course.

with parsing assign's output.

the conglomerate link object, not the real link, for the reversed
flag.

makes link conglomerates.

we might be combining links that go in different directions. Keep
track of which direction a link points, and reverse the interfaces
when we print it out, if it's going the opposit direction than the
other links in the conglomerate.

see (or remember) any reason for this slot to be 20 chars, when the
name of every other vname slot is 32. I looked in the event scheduler
and there do not appear to be any problems there with bumping it. Note
that I choose 64 cause we tend to construct agent names that might be
longer then 32 since they are based on real vnames (lan0, node0, etc).

data.  Add hostkeys() to the node module so we can get the SSH host
keys from nodes.

new directive for your NS file: tb-use-physnaming(1) which means that
if you have a line like this:

	set pc6 [$ns node]

and pc6 is an actual name of a physical node, then do an implicit
"fixnode" to pc6. In other words, pc6 is the name of the node in your
NS file (virtual topo) *and* will be fixed to the real pc6. Needless
to say, if pc6 is allocated when you go to swapin, you lose.

Add a new function, factor_out_fixednodes, that takes a set of nodes
and a reference to another coarsening function. Seperately coarsens
the fixed nodes and passes the non-fixed nodes to the other coarsener.

Intended for debugging, and to use used with assign's pre-check
feature to catch experiments that will never be mappable.

around from the last boot, and we have more than one CPU: line.
Sometimes (such as at Wisc.), the first instance contains garbage. So,
instead of exiting after the first CPU: line, use a different method
of handling unknown CPU speeds, modeled after chipset.awk .

currently available to only people with stud=1 status in the DB.

* www/tbauth.php3: Add a STUDLY() function to check that bit.

* www/linktest.php3: New page to run linktest on the fly. The level
  defaults to the current level in the experiments table, but you can
  override that via the form on the page.

* www/showexp.php3: Add link to aforementioned page. STUDLY() only.

* www/beginexp_form.php3: Add an option (selection) to set the linktest
  level for create/swapin. Defaults to 0 (no linktest). STUDLY() only.

* www/editexp.php3: Add an option to edit the default linktest level
  for an experiment. STUDLY() only.

* tbsetup/batchexp.in and tbsetup/swapexp.in: Add code to optionally run
  the linktest, sending email if it fails (exists with non-zero status).
  Failure does not affect the swapin.

experiment table rows after a parse. It used to be that slots that
were not explicitly given values by the parser would be left as
whatever they were in the DB. Now I get the default values by doing
a "describe experiments" query, inserting those values for any slot
that is not set by the parser.

In the ptop file, put the specific protocol (ie. 80211a) on the link
line.

In the ptop file, there is now only one fake airswitch. It can take
on all wireless types. We now only print one link line for each
physical wireless interface - it has the maximum bandwidth supported
by the interface, and is able to take on any protocol supported by the
interface.

match what ptopgen puts into to ptop file.

is_string() function returns true for numeric strings. I guess this
makes some sense, but it wasn't what I was expecting.

the temperature gets below zero, or becomes NaN (which can happen if
the solution stabilizes during melting.)

in some (okay, many) cases. Not sure why, though.

epsilon termination (and ALLOW_NEGATIVE_EPSILON), it used to be the case that
we wrapped the termination condition in a fabs(), and compared that to epsilon.
The termination condition is basically a measure of how 'stable' of a score
we're at. What this meant was that we used to keep going until we reached a
space where the solution was going neither up nor down too much. All this is
relative to the difference between initial socre and the best score - so, if
those are close (ie. it's an easy problem), we could end up thrashing a whole
lot. With the new behavior, if we ever hit a spot in which solutions start
getting worse, we'll stop.

Also, fix the GNUPLOT_OUTPUT code, which I used to debut this.

parsing code (for simplistic xml we spit from the parser).

and ptopgen.

Add link typing to assign. Each virtual link is given a single type.
Each physical link is given one or more types. A virtual link will
only be mapped to a physical link which can satisfy its type. In both
the top and ptop files, the link types are now mandatory, and they
fall at the end of the mandatory link arguments.

This differers from the 'regular' type system in two ways. First, a
plink is not constrained to filling only one type at a time. If we are
using emulated links, a plink could satisfy, say, an 'ethernet' link
and an 'fxp' link at the same time. This seems to more naturally match
the way we'll use link types.  Second, there are no counts assoicated
with link types, as there are for node types. ie. a link is not an
'ethernet:1' link, it's an 'ethernet' link. Presumably, when
multiplexing virtual links onto a physical one, it's bandwidth that's
the factor that limits the multiplexing.

The link type is now taken into account when constructing pclasses,
and in the mapping precheck.

As a side-effect of these changes, the silly 'count' argument on the
end of link lines in the ptop file, which was used for the fake LAN
nodes, is no longer supported.

The implementation could be a bit more efficient, but that would mean
tossing more of the stuff we do with boost's graph library. I think
this should happen, but today is not the day.

Modify assign_wrapper and ptopgen to spit out top and ptop files in
the new format.

Changed the constant LINK_UKNOWN to LINK_UNMAPPED - the new name more
accurately reflects the way this constant is used.

Add a new '-n' flag that tells assign not to do annealing, just exit
after the type precheck.

Clarify the usage message for the -c flag.

Removed some dead code for dealing with LAN nodes.