GitLab

what locpiper to connect to. Locpiper now binds a dynamic port, and
stores that into the DB, and the php script expects to get that pid,eid
back.

Changed the showexp page so that pid,eid are passed to the robotrack
top level page.

Changed the robotrack page so that if it does not get a pid,eid, it looks
for an experiment running (a locpiper). If none is running, let the applet
start of course, but there will be an error dialog when it starts. You can
still play with the applet of course. If there is more then one experiment
running, then just pick first one. At some point I might add a page to ask
which experiment, but its low priority.

adding the nodes, or else they check in and get a dynamic address
again. I'm kinda surprised this has not come up before?

in debugging.  The frames are dumped to disk on SIGHUP or if an
MTP_SNAPSHOT packet is received.  Fortunately, we can do this since
there is just barely enough CPU and RAM to do this for all four
cameras on a machine.

to the fault detection code.

obstacles that represent a robot.

thing; restart mysqld after it gets a signal other then TERM.

* Use the "role" slot of the interfaces table, instead of joining with
  node_type, to find the control interface. Must do this inside an
  inner Elab of course, since the node_types table does not reflect
  how assign selected the interface we use for the "control" network.

* Use !is_numeric() instead of is_string() to determine if the naming
  patter in alpha based instead of number based ("1" is a string).

  RobTransparentBase, just modified things to blink leds differently
(i.e.,
  toggle the yellow led on packet receive), and to
  dump original sender id, rssi, and AM type for any packet the mote
hears.
  There's an sflisten.c program that will decode and display these values.
  It requires several of the tinyos C sf header files and code.

RobTransparentBase, just modified things to blink leds differently (i.e.,
toggle the yellow led on packet receive), and to
dump original sender id, rssi, and AM type for any packet the mote hears.
There's an sflisten.c program that will decode and display these values.
It requires several of the tinyos C sf header files and code.

ISUP or else they leave off at SHUTDOWN, which later confuses swapmod
(tbswap) which waits for them to reach ISUP, but of course they never
do. This is arguably a misfeature of os_setup, which should probably
not wait for nodes it didn't reboot, but I want to ponder that change.
Besides, doing this causes the nodes not to say SHUTDOWN in the web
interface.

Another change to add there (web interface) is to not say "possibly
down" for elabinelab nodes.

their serial lines.  Useful for testing packet reception, power usage,
etc.

enough and seem to work.  Currently, the moving average window size is set
to 5 frames (in testbed/event/sched/event-sched.c); a window size of 10
produced too much position lag.

not been created yet. This happens during the bootstrap of the initial
groups. Not a big deal, it all works out in the end (the groups get
set later in a subsequent call to setgroups).

file if it does not exists, and then append to it. In our elabinelab
setup, there is always an existing root authkeys file, so we missed
this error.

negotiate:

# Divide the nodes up into used and unused based on the status of
# their WhOL experimental interface:
#
# enabled=yes     port in use
# enabled=no      not used
#
# If a port is "in use" we assume it has talked to the switch and
# no speed/duplex changes are needed.
#
# If the port is unused, we assume that the port will try to auto
# negotiate with the switch when enabled.  In this case we set
# auto-negotiation on the switch to maximize the chance that we will
# sucessfully communicate with the card.

Also, fix a small missing paren from Keith's contributed version.

need it.

trunks for convenient checking against.

generate month by month files, and then a little index to include into the
php script.

I know, this is really important stuff! But, I was reminded to do this by a
message that Christopher Johnson (the young one) sent on April 29th about
his project. His code was quaint, but I did not think we needed a new
python script when it was much easier just to roll it into the existing
perl script that imports the commitlog.

table, if elabinelab_nosetup is non-zero, boss and ops setup will do
just enough to get the nodes into a state that hopefully approximates
what a real installation might look like before installing our stuff.
I do install the packages cause there is no point in waiting for that
to finish interactively.

From this point, you can log into the console(s) and run the setup
instructions verbatim, although I have not actually tried that yet.

The nice thing is that if you manage to get things properly setup, it
can function as a real elabinelab since the outer environment has been
setup. This is quite a bit different then how we tested during the
last release frenzy.

Its not quite perfect of course, since the images are not "clean", but
I think this is okay for testing.

is not running, and there is no locpiper to connect to. Pop up a dialog
box telling the user.

experiments can be auto fired during swapin.

inner boss and ops:

	namespace eval TBCOMPAT {
	    set elabinelab_tarfiles("boss") "/usr/site /foo/silly.tar.gz"
	}

Ditto for "ops". You can specify multiple tarfiles of course in the
string, just as tb-set-node-tarfiles allows.

argument, treat it as a string and first split it apart. This is a
common error that many people make.

initial reverse file. Note that we still do not try to generate
multiple reverse files; that is up to the local site.

moving that robot!

new client connects, we can dump the current set to the applet. I'm
still holding off on putting them into the DB (really do not think
this is the right thing to do, but I can be convinced otherwise).

Change battery code in the locpiper so that if the data for a robot is
more then 10 minutes old, stop sending updates for that robot.

For the applet, add a little daemon thread that checks to see if
battery updates have stopped, and if so, change the color of the robot
to blue (cold and stale). This makes it more clear which robots are
working and which are turned off.

Fix collision detection code so that we test for the center of a robot
overlapping with an obstacle, rather then radius of the area it sweeps
(Tim said this was the correct thing to do).