<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0"
 xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
 xmlns:dc="http://purl.org/dc/elements/1.1/"
 xmlns:admin="http://webns.net/mvcb/"
>
<channel>
<title>Kurt's Weblog</title>
<link>http://schwehr.org/blog/rss.xml</link>
<description>electronic work log</description>
<dc:language>en-us</dc:language>
<dc:creator>Kurt</dc:creator>
<dc:date>2010-03-09T14:27:18-05:00</dc:date>
<admin:generatorAgent rdf:resource="http://nanoblogger.sourceforge.net" />
<item>
<link>http://schwehr.org/blog/archives/2010-03.html#e2010-03-09T13_57_15.txt</link>
<title>ABE lost over the weekend</title>
<dc:date>2010-03-09T13:57:15-05:00</dc:date>
<dc:creator>Kurt</dc:creator>

<description><![CDATA[Art just sent me an email about the loss of a WHOI AUV:  <a href="http://www.whoi.edu/sbl/liteSite.do?litesiteid=4050">ABE</a> will be missed.  But with all AUVs, the risk of loss is a part of the process.  If you don't use them, then you will not loose `em.
<a href="http://www.whoi.edu/page.do?pid=7545&tid=282&cid=70487&ct=162">News Release : Pioneering Deep-Sea Robot Lost at Sea</a> [WHOI.edu]
<pre>The Autonomous Benthic Explorer, ABE, was lost at sea over the weekend,
during a research cruise off the coast of Chile.  ABE was a pioneering
deep-sea exploration robot—one of the first successful submersible
vehicles that was both unmanned and untethered to surface ships.
...</pre>
It's rough loosing an underwater vehicle, but we get over it and move on 
to the next great project with many lessons learned.]]></description>
</item>
<item>
<link>http://schwehr.org/blog/archives/2010-03.html#e2010-03-09T09_48_56.txt</link>
<title>Unknown vessels are a pain</title>
<dc:date>2010-03-09T09:48:56-05:00</dc:date>
<dc:creator>Kurt</dc:creator>

<description><![CDATA[Vessels like this are a real pain.  Someone was out off of Boston for
a whole day in 2008 with a miss-configured Class A AIS unit.  Type 30
is a fishing vessel.  This vessel is not listed in the FCC register.  This
mmsi is still floating around with a report on 2009-10-10 based on <a href="http://mmsispace.com">MMSIspace</a>.  However, this vessel still has no name, IMO or callsign. 
<br /><br />
<table  border="1" cellspacing="0" cellpadding="6" rules="all" frame="all">
<caption></caption>
<colgroup><col align="left" /><col align="left" /><col align="left" /><col align="left" /><col align="left" /><col align="left" /><col align="left" /><col align="left" /><col align="left" /><col align="left" /><col align="left" /><col align="left" /><col align="left" />
</colgroup>
<thead>
<tr border="2"><th scope="col">MMSI</th><th scope="col">IMOnum</th><th scope="col">callsign</th><th scope="col">name</th><th scope="col">shiptype</th><th scope="col">dimA</th><th scope="col">dimB</th><th scope="col">dimC</th><th scope="col">dimD</th><th scope="col">draught</th><th scope="col">dest</th><th scope="col">cg_r</th><th scope="col">cg_timestamp</th></tr>
</thead>
<tbody>
<tr><td>338078447</td><td>0</td><td>@@@@@</td><td>@@@@@</td><td>30</td><td>6</td><td>3</td><td>3</td><td>3</td><td>0</td><td>@@@@</td><td>r003669946</td><td>2008-10-15 01:41:39</td></tr>
</tbody>
</table>]]></description>
</item>
<item>
<link>http://schwehr.org/blog/archives/2010-03.html#e2010-03-05T17_16_18.txt</link>
<title>Panoram display on the cheap</title>
<dc:date>2010-03-05T17:16:18-05:00</dc:date>
<dc:creator>Kurt</dc:creator>

<description><![CDATA[Roland and Colin setup the panoram display in the vislab using 4 projectors.  Roland got the display up using static panoramas, GigaPan, and <a href="http://www.flightgear.org/">FlightGear</a>.
<br /><br />
<img title="Roland showing off the 4 projectors" withgrayborder="True" src="http://schwehr.org/blog/attachments/2010-03/panoram-roland.jpg"/>
<br /><br />
<img title="Roland at the controls" withgrayborder="True" src="http://schwehr.org/blog/attachments/2010-03/panoram-operating.jpg"/>
<br /><br />
Being that flight gear is based on open source toolkits, there is a
good chance that we can hook our AIS feed to this and drive the ships
around to match actual traffic.
<br /><br />
<img title="" withgrayborder="True" src="http://schwehr.org/blog/attachments/2010-03/panoram-flightsim-ship.jpg"/>]]></description>
</item>
<item>
<link>http://schwehr.org/blog/archives/2010-03.html#e2010-03-05T09_37_29.txt</link>
<title>Flash back to MER</title>
<dc:date>2010-03-05T09:37:29-05:00</dc:date>
<dc:creator>Kurt</dc:creator>

<description><![CDATA[Accidentially ran into a great blog by <a href="http://marsandme.blogspot.com/">Scott Maxwell</a> who has posted
about his experiences work on the Mars Exploration Rovers.  Extra
bonus that I appear in at least one of his posts.  I was working so
many hours during MER, that I barely remember any of it.  12-16 hour
days were typical.  Being able to read Scott's adventure through MER
is a real treat for people who just like planetary exploration or
robots and for those working on research for robots and planetary
exploration.
<br /><br />
<a href="http://marsandme.blogspot.com/2009/01/spirit-sol-13.html">Spirit Sol 13</a>
<pre>...
Just as I arrive, I meet Kurt Schwehr, who asks if RSVP can produce
animations. Boy, do I have great timing. It turns out that Kurt
intends to record RSVP simulating the pre-egress turn, so that they
can show it at the press conference. At the moment, he doesn't need
our new feature where we write our animation to a file -- he's under
time pressure and just wants to use the existing animation features,
and just needs a little help figuring them out -- but he's interested
in the new stuff and wants to hear more about it. Score!
...</pre>
I spent a lot of time with RSVP on MER and even more on Phoenix.]]></description>
</item>
<item>
<link>http://schwehr.org/blog/archives/2010-03.html#e2010-03-01T21_41_35.txt</link>
<title>IODP Expedition 318 - Antarctica week 5</title>
<dc:date>2010-03-01T21:41:35-05:00</dc:date>
<dc:creator>Kurt</dc:creator>

<description><![CDATA[<object width="640" height="385"><param name="movie" value="http://www.youtube.com/v/uvzrK24YJyQ&hl=en_US&fs=1&color1=0x006699&color2=0x54abd6"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/uvzrK24YJyQ&hl=en_US&fs=1&color1=0x006699&color2=0x54abd6" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="640" height="385"></embed></object>]]></description>
</item>
<item>
<link>http://schwehr.org/blog/archives/2010-02.html#e2010-02-22T08_51_40.txt</link>
<title>AMQP messaging in fink</title>
<dc:date>2010-02-22T08:51:40-05:00</dc:date>
<dc:creator>Kurt</dc:creator>

<description><![CDATA[I need a solid messaging framework for one of my projects.  I've used
NDDS (now DDS), RTC (an CMU thing), <a
href="http://pyro.sourceforge.net/">Pyro</a>, and a few others in the
past.  I want something simple, but that buys me more than just
managing TCP or UDP myself.  I looked at Jabber/XMPP a bit, but then 
started reading about AMQP, which sounds attractive, especially with
the option to allow for keeping messages through a system crash.  
<br /><br />
I spent some time with various implementations of AMQP with not much
success.  I avoided RabbitMQ because it is based on Erlang which is
not something I am used to.  I tried these two, but got frustrated
with the code bases.  I don't have time to get them to build
reasonably on the Mac with fink.
<ul>
<li><a href="http://qpid.apache.org/">qpid</a></li>
<li><a href="http://www.openamq.org/">OpenMQ</a></li>
</ul>
I ended up packaging these into fink:
<ul>
<li><a href="http://www.rabbitmq.com/">RabbitMQ</a> - Once I realized
that I don't to know Erlang</li>
<li><a href="http://pypi.python.org/pypi/amqplib/">amqplib</a> - basic
python library</li>
<li><a href="http://pypi.python.org/pypi/carrot/">carrot</a></li>
<li><a href="http://pypi.python.org/pypi/celery/">celery</a></li>
</ul>
I did some simple tests and have the basics working.  I now need to
figure out how to use carrot and celery.
<br /><br />
For general background, I read <a
href="http://blogs.digitar.com/jjww/2009/01/rabbits-and-warrens/">Rabbits
and Warrens</a> and watched this video, but is not the best for seeing
the figures, but it does give a kickstart.  The slides get better
about 20 minutes in.
<br /><br />
<object width="640" height="505"><param name="movie" value="http://www.youtube.com/v/ZQogoEVXBSA&hl=en_US&fs=1&"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/ZQogoEVXBSA&hl=en_US&fs=1&" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="640" height="505"></embed></object>]]></description>
</item>
<item>
<link>http://schwehr.org/blog/archives/2010-02.html#e2010-02-18T09_54_14.txt</link>
<title>Automatically updating charts in ECDIS</title>
<dc:date>2010-02-18T09:54:14-05:00</dc:date>
<dc:creator>Kurt</dc:creator>

<description><![CDATA[Internet chart updates are a critical capability, but
I have two concerns with internet chart updates.  The first is that
all of the bridge crew needs to be aware that the charts have been
updated.  There does not appear to be a good way to tell what has
changed between chart updates and if the updates happen without some
of the bridge crew being aware, they may get a surprise at an
inopportune moment.  The second concert is with ECDIS systems running
on MS Windows - internet updating should be an issue with respect to
viruses, but the track record of the Windows community is that this
should be a concern.  I still can't believe that large ships run with
windows as the OS for life critical operations.  I've run linux boxes
for as long as 2 years without a need for a reboot or update for as
much as 2 years... right on a bare internet connection with no viruses
or troubles with hackers.
<br /><br />
From Digital Ship, Mar 2010:
<pre>...
IMO's push for e-Navigation and the introduction of a mandatory
carriage requirement for ECDIS (electronic chart display and
information system) from 2012 could help to reduce the possibility of
vessels sailing with charts that do not represent the most accurate
and up-to- date representation of their navigational environment.
<!-- -->
The transmission of digital chart data, whether by satellite or using
other broad- cast systems, is quite obviously the fastest way of
getting the latest corrections on to a vessel bridge. 
...</pre>]]></description>
</item>
<item>
<link>http://schwehr.org/blog/archives/2010-02.html#e2010-02-17T16_21_06.txt</link>
<title>ais-areanotice-py 0.2</title>
<dc:date>2010-02-17T16:21:06-05:00</dc:date>
<dc:creator>Kurt</dc:creator>

<description><![CDATA[I've been working on improving the <a href="http://vislab-ccom.unh.edu/~schwehr/software/ais-areanotice-py/">ais-areanotice-py</a> reference
implementation of the NAV55 proposed AIS Binary Message for Area
Notices.  Version 0.1 was seriously buggy.  Thanks to Brad for being
the first to submit bug reports.  He pointed out all sorts of
unpleasant things.  I bit the bullet and started <a
href="http://en.wikipedia.org/wiki/Eating_one%27s_own_dog_food">dog
fooding</a> what I produce.  I've implemented decoders for everything
but the polylines and polygons that span more than one sub-area.  There
are lots of changes and at this point, I think this is the beginnings
of a reasonable test data set.  Please try this!  I really need testing and feedback.
<br /><br />
Software is available under <a href="http://vislab-ccom.unh.edu/~schwehr/software/ais-areanotice-py/downloads/">downloads</a> and the test data under <a href="http://vislab-ccom.unh.edu/~schwehr/software/ais-areanotice-py/samples/">samples</a>.
<br /><br />
<img title="Updated KML with merged FreeText" withgrayborder="True" src="http://schwehr.org/blog/attachments/2010-02/ais-areanotice-try2.png"/>]]></description>
</item>
<item>
<link>http://schwehr.org/blog/archives/2010-02.html#e2010-02-16T17_41_54.txt</link>
<title>NAIS data release RFC</title>
<dc:date>2010-02-16T17:41:54-05:00</dc:date>
<dc:creator>Kurt</dc:creator>

<description><![CDATA[I submitted my comments for the USCG RFC about NAIS data release.  I
hope many other people did to.  It's important to engage the
government in these types of discussions.  So far, I know one other
person who has submitted comments:
<br /><br />
ESR: <a href="http://esr.ibiblio.org/?p=1616">Comment to USCG on NAIS policy</a>
<br /><br />
Let me know if there are others.  I've put mine up in a place that has
comments.  Feel free to agree, disagree, etc.  This topic is really
worthy of a whole series of papers, but this is all I can muster right
now.
<br /><br />
<a href="http://schwehr.blogspot.com/2010/02/uscg-request-for-comment-on-nais-data.html">USCG Request For Comment on NAIS data release</a>
<br /><br />
The summary:
<pre>My overall opinion is that the only increased risk from releasing raw
AIS data comes from the economic impact to those who are trying to
sell AIS feeds. Outside of the 3 or 4 groups doing Satellite based
AIS, I don't think these companies should get protection. There is
already stiff competition, e.g. AIS Hub will give you AIS data for
free if you contribute back at least a little bit of data. AIS
receivers start from about $190. The real value comes from
interpretation - analysis and display of these feeds. More access to
AIS data means to me that we will get more people involved in analysis
and it will speed the uptake of AIS binary messages. As for security,
if the USCG needs to keep this data restricted as sensitive, then it
should not have been broadcast in the clear to start with. Hiding
addressed messages is strange when anyone with a receiver and gpsd can
see most of these addressed messages anyway.</pre>]]></description>
</item>
<item>
<link>http://schwehr.org/blog/archives/2010-02.html#e2010-02-16T08_07_18.txt</link>
<title>Open Street Map (OSM) Haiti edits</title>
<dc:date>2010-02-16T08:07:18-05:00</dc:date>
<dc:creator>Kurt</dc:creator>

<description><![CDATA[This shows the power of an open system doing what it is supposed to do
in the event of an emergency.  Hats off to all who contributed.
<br /><br />
<object width="400" height="225"><param name="allowfullscreen" value="true" /><param name="allowscriptaccess" value="always" /><param name="movie" value="http://vimeo.com/moogaloop.swf?clip_id=9182869&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=1&amp;color=&amp;fullscreen=1" /><embed src="http://vimeo.com/moogaloop.swf?clip_id=9182869&amp;server=vimeo.com&amp;show_title=1&amp;show_byline=1&amp;show_portrait=1&amp;color=&amp;fullscreen=1" type="application/x-shockwave-flash" allowfullscreen="true" allowscriptaccess="always" width="400" height="225"></embed></object><p><a href="http://vimeo.com/9182869">OpenStreetMap - Project Haiti</a> from <a href="http://vimeo.com/itoworld">ItoWorld</a> on <a href="http://vimeo.com">Vimeo</a>.</p>]]></description>
</item>
</channel>
</rss>
