Main
\\
There are two rooms reserved for the event should it make sense to split into two tracks.
!!!! (Material posted as speakers send in their briefs - check back later if a brief is missing.)
%center%%width=100px%Path:/moos-dawg10/moos-dawg-one.jpg
! %color=#4444BB% '''The MOOS-DAWG 2010 Agenda in PDF form: '''%% [[Path:/moos-dawg/moos-dawg-program.pdf | Click Here]]
----
[++ %color=#4444BB% [[FOOBAR | Click Here for MOOS-DAWG'11%% ++]
----
! %color=#4444BB% '''Update, Posted 10am Monday Aug 23rd:'''
The barbecue, sponsored by [[http://www.bluefinrobotics.com | Bluefin Robotics]], has been moved indoors to the Forbes Cafe, in the Stata Center. This is the same site as the MOOS-DAWG meeting, at 32 Vassar Street, on the MIT campus. Same time, 6-8pm. See you there!
!%color=#4444BB% '''The Final MOOS-DAWG 2010 Agenda has been posted!! '''%% [[Site.Schedule24 | Click Here]]
----
!%color=#4444BB% '''The MOOS-DAWG 2010 Agenda has been posted!! '''%% [[Site.Schedule24 | Click Here]]
----
!!!!A Working Group meeting for Developers of MOOS-based software and \\
MOOS-IvP (pronounced "moose i-v-p") is a set of Open Source C++ modules for controlling the full operation of an autonomous marine vehicle. MOOS modules are distinct processes running on the vehicle's CPU, communicating via a single database process in a publish-subscribe manner. The IvP Helm is a single MOOS process dedicated to autonomy decision making composed of distinct vehicle behavior modules. The ability to simply and freely interchange and improve upon modules is a primary objective of the architecture. MOOS ``modules'' refer to MOOS processes and IvP ``modules'' refer to IvP Helm behaviors.\\
\\
'''MOOS''' stands for "Mission Oriented Operating Suite", and '''IvP''' stands for "Interval Programming".
The 2010 Working Group Meeting for MOOS developers and practitioners will be held in Cambridge
Massachusetts, August 24-25th, on the campus of the Massachusetts Institute of Technology.
Home Page
Main.HomePage History
Hide minor edits - Show changes to output
Changed lines 28-29 from:
There are two rooms reserved for the event should it make sense to split into two tracks.
to:
Changed lines 16-22 from:
%center%%width=100px%Path:/moos-dawg10/moos-dawg-one.jpg
! %color=#4444BB% '''The MOOS-DAWG 2010 Agenda in PDF form: '''%% [[Path:/moos-dawg/moos-dawg-program.pdf | Click Here]]
----
to:
Changed line 5 from:
[++ %color=#4444BB% [[FOOBAR | Click Here for MOOS-DAWG'11]]%% ++]
to:
[++ %color=#4444BB% [[Path:/moos-dawg11 | '''Click Here for MOOS-DAWG'11''']]%% ++]
Changed line 5 from:
[++ %color=#4444BB% [[FOOBAR | Click Here for MOOS-DAWG'11%% ++]
to:
[++ %color=#4444BB% [[FOOBAR | Click Here for MOOS-DAWG'11]]%% ++]
Added lines 4-7:
[++ %color=#4444BB% [[FOOBAR | Click Here for MOOS-DAWG'11%% ++]
----
Changed line 14 from:
%center%%width=100px%Path:/moos-dawg/moos-dawg-one.jpg
to:
%center%%width=100px%Path:/moos-dawg10/moos-dawg-one.jpg
Changed line 16 from:
! %center%%color=#4444BB% '''The MOOS-DAWG 2010 Agenda in PDF form: '''%% [[Path:/moos-dawg/moos-dawg-program.pdf | Click Here]]
to:
! %color=#4444BB% '''The MOOS-DAWG 2010 Agenda in PDF form: '''%% [[Path:/moos-dawg/moos-dawg-program.pdf | Click Here]]
Changed lines 11-12 from:
! %color=#4444BB% '''Proceedings Material Available: '''%% [[Path:/moos-dawg/moos-dawg-program.pdf | Click Here]]
!!!! Material posted as speakers send in their briefs - check back later if a brief is missing.
!!!! Material posted as speakers send in their briefs - check back later if a brief is missing.
to:
! %color=#4444BB% '''Proceedings Material Available: '''%% [[Talk.Listing | Click Here]]
!!!! (Material posted as speakers send in their briefs - check back later if a brief is missing.)
!!!! (Material posted as speakers send in their briefs - check back later if a brief is missing.)
Added line 12:
!!!! Material posted as speakers send in their briefs - check back later if a brief is missing.
Changed line 11 from:
! %%color=#4444BB% '''Proceedings Material Available: '''%% [[Path:/moos-dawg/moos-dawg-program.pdf | Click Here]]
to:
! %color=#4444BB% '''Proceedings Material Available: '''%% [[Path:/moos-dawg/moos-dawg-program.pdf | Click Here]]
Changed line 11 from:
! %center%%color=#4444BB% '''Proceedings Material Available: '''%% [[Path:/moos-dawg/moos-dawg-program.pdf | Click Here]]
to:
! %%color=#4444BB% '''Proceedings Material Available: '''%% [[Path:/moos-dawg/moos-dawg-program.pdf | Click Here]]
Added lines 11-12:
! %center%%color=#4444BB% '''Proceedings Material Available: '''%% [[Path:/moos-dawg/moos-dawg-program.pdf | Click Here]]
Changed line 15 from:
! %center%%color=#4444BB% '''The Final MOOS-DAWG 2010 Agenda has been posted!! '''%% [[Path:/moos-dawg/moos-dawg-program.pdf | Click Here]]
to:
! %center%%color=#4444BB% '''The MOOS-DAWG 2010 Agenda in PDF form: '''%% [[Path:/moos-dawg/moos-dawg-program.pdf | Click Here]]
Deleted lines 10-13:
The barbecue, sponsored by [[http://www.bluefinrobotics.com | Bluefin Robotics]], has been moved indoors to the Forbes Cafe, in the Stata Center. This is the same site as the MOOS-DAWG meeting, at 32 Vassar Street, on the MIT campus. Same time, 6-8pm. See you there!
Changed line 13 from:
The barbecue, sponsored by [[www.bluefinrobotics.com|Bluefin Robotics]], has been moved indoors to the Forbes Cafe, in the Stata Center. This is the same site as the MOOS-DAWG meeting, at 32 Vassar Street, on the MIT campus. Same time, 6-8pm. See you there!
to:
The barbecue, sponsored by [[http://www.bluefinrobotics.com | Bluefin Robotics]], has been moved indoors to the Forbes Cafe, in the Stata Center. This is the same site as the MOOS-DAWG meeting, at 32 Vassar Street, on the MIT campus. Same time, 6-8pm. See you there!
Changed line 13 from:
The barbecue, sponsored by [[www.bluefinrobotics|Bluefin Robotics]], has been moved indoors to the Forbes Cafe, in the Stata Center. This is the same site as the MOOS-DAWG meeting, at 32 Vassar Street, on the MIT campus. Same time, 6-8pm. See you there!
to:
The barbecue, sponsored by [[www.bluefinrobotics.com|Bluefin Robotics]], has been moved indoors to the Forbes Cafe, in the Stata Center. This is the same site as the MOOS-DAWG meeting, at 32 Vassar Street, on the MIT campus. Same time, 6-8pm. See you there!
Changed lines 11-13 from:
! %color=#4444BB% '''Update, 10am Monday Aug 23rd:'''
The barbecuehas been moved indoors to the Forbes Cafe, in the Stata Center
The barbecue
to:
! %color=#4444BB% '''Update, Posted 10am Monday Aug 23rd:'''
The barbecue, sponsored by [[www.bluefinrobotics|Bluefin Robotics]], has been moved indoors to the Forbes Cafe, in the Stata Center. This is the same site as the MOOS-DAWG meeting, at 32 Vassar Street, on the MIT campus. Same time, 6-8pm. See you there!
The barbecue, sponsored by [[www.bluefinrobotics|Bluefin Robotics]], has been moved indoors to the Forbes Cafe, in the Stata Center. This is the same site as the MOOS-DAWG meeting, at 32 Vassar Street, on the MIT campus. Same time, 6-8pm. See you there!
Changed lines 11-13 from:
! %color=#4444BB% '''The barbecue has been moved indoors to the Forbes Cafe, in the Stata Center'''
to:
! %color=#4444BB% '''Update, 10am Monday Aug 23rd:'''
The barbecue has been moved indoors to the Forbes Cafe, in the Stata Center
The barbecue has been moved indoors to the Forbes Cafe, in the Stata Center
Added lines 11-12:
! %color=#4444BB% '''The barbecue has been moved indoors to the Forbes Cafe, in the Stata Center'''
Changed line 13 from:
! %center%%color=#4444BB% '''The Final MOOS-DAWG 2010 Agenda has been posted!! '''%% [[Site.Schedule24 | Click Here]]
to:
! %center%%color=#4444BB% '''The Final MOOS-DAWG 2010 Agenda has been posted!! '''%% [[Path:/moos-dawg/moos-dawg-program.pdf | Click Here]]
Changed lines 13-14 from:
%color=#4444BB% '''The Final MOOS-DAWG 2010 Agenda has been posted!! '''%% [[Site.Schedule24 | Click Here]]
to:
! %center%%color=#4444BB% '''The Final MOOS-DAWG 2010 Agenda has been posted!! '''%% [[Site.Schedule24 | Click Here]]
Changed line 13 from:
to:
%color=#4444BB% '''The Final MOOS-DAWG 2010 Agenda has been posted!! '''%% [[Site.Schedule24 | Click Here]]
Added lines 11-12:
%center%%width=100px%Path:/moos-dawg/moos-dawg-one.jpg
Changed line 11 from:
!%color=#4444BB% '''The MOOS-DAWG 2010 Agenda has been posted!! '''%% [[Site.Schedule24 | Click Here]]
to:
!%color=#4444BB% '''The Final MOOS-DAWG 2010 Agenda has been posted!! '''%% [[Site.Schedule24 | Click Here]]
Added lines 9-12:
----
!%color=#4444BB% '''The MOOS-DAWG 2010 Agenda has been posted!! '''%% [[Site.Schedule24 | Click Here]]
----
Changed line 5 from:
!Welcome to MOOS-DAWG 2010 Hi Joe !!\\
to:
!Welcome to MOOS-DAWG 2010 !!\\
Changed line 5 from:
!Welcome to MOOS-DAWG 2010 !!\\
to:
!Welcome to MOOS-DAWG 2010 Hi Joe !!\\
Changed lines 16-19 from:
* Fielded autonomous applications using MOOS
* Development of MOOS-based software applications
* Panel discussions on best-practices and roadmaps for improvement
* Tutorials
* Panel discussions on best-practices and roadmaps for improvement
* Tutorials
to:
* Fielded autonomous platforms using MOOS and/or MOOS-IvP.
* Development of MOOS-based software applications.
* Panel discussions on best-practices and roadmaps for improvement.
* Tutorials.
* Development of MOOS-based software applications.
* Panel discussions on best-practices and roadmaps for improvement.
* Tutorials.
Changed line 16 from:
* Field Autonomous applications using MOOS
to:
* Fielded autonomous applications using MOOS
Changed line 16 from:
* Field Applications using MOOS
to:
* Field Autonomous applications using MOOS
Changed line 12 from:
The objectives of the MOOS-DAWG 2010 meeting are to bring people together who have experience or an interest in using MOOS middleware and its substantial set of applications, toward the advancement of unmanned autonomous systems. \\
to:
The objectives of the MOOS-DAWG 2010 meeting are to bring people together who have experience or an interest in using MOOS autonomy middleware and its substantial set of applications, toward the advancement of unmanned autonomous systems. \\
Changed lines 25-26 from:
Although the software distributed under the MOOS and MOOS-IvP websites are in the public domain, there are a number of individuals and groups that are doing interesting things building on the publicly available code. Whether it be the lack of time or lack of a mechanism for formal sharing or
to:
Although the software distributed under the MOOS and MOOS-IvP websites are in the public domain, there are a number of individuals and groups that are doing interesting things building on the publicly available code. Often these field applications, development modules and tools, and
lessons-learned do not propagate beyond the host organization for whatever reason. This meeting aims to lower the bar for such information exchange by way of a friendly informal gathering.
lessons-learned do not propagate beyond the host organization for whatever reason. This meeting aims to lower the bar for such information exchange by way of a friendly informal gathering.
Changed line 25 from:
Although the software distributed under the MOOS and MOOS-IvP websites are in the public domain, there are
to:
Although the software distributed under the MOOS and MOOS-IvP websites are in the public domain, there are a number of individuals and groups that are doing interesting things building on the publicly available code. Whether it be the lack of time or lack of a mechanism for formal sharing or
Changed lines 20-21 from:
to:
\\
Added lines 23-25:
!!Why Hold this Working Group Meeting?
Although the software distributed under the MOOS and MOOS-IvP websites are in the public domain, there are
Although the software distributed under the MOOS and MOOS-IvP websites are in the public domain, there are
Changed line 12 from:
The objectives of the MOOS-DAWG 2010 meeting are to bring people together who have experience or an interest in using MOOS middleware and its substantial set of applications, toward the advancement unmanned autonomous systems. \\
to:
The objectives of the MOOS-DAWG 2010 meeting are to bring people together who have experience or an interest in using MOOS middleware and its substantial set of applications, toward the advancement of unmanned autonomous systems. \\
Changed line 5 from:
!Welcome to MOOS-DAWG 2010 \\
to:
!Welcome to MOOS-DAWG 2010 !!\\
Changed lines 15-22 from:
The format of the meeting will
to:
The format of the meeting will be mostly single-track discussions on
* Field Applications using MOOS
* Development of MOOS-based software applications
* Panel discussions on best-practices and roadmaps for improvement
* Tutorials
There are two rooms reserved for the event should it make sense to split into two tracks.
* Field Applications using MOOS
* Development of MOOS-based software applications
* Panel discussions on best-practices and roadmaps for improvement
* Tutorials
There are two rooms reserved for the event should it make sense to split into two tracks.
Changed lines 12-16 from:
The objectives of the MOOS-DAWG 2010 meeting are to bring people together who have experience or an interest in using MOOS middleware and its substantial set of applications.
to:
The objectives of the MOOS-DAWG 2010 meeting are to bring people together who have experience or an interest in using MOOS middleware and its substantial set of applications, toward the advancement unmanned autonomous systems. \\
\\
The format of the meeting will
\\
The format of the meeting will
Added lines 10-12:
!!Objectives and Format
The objectives of the MOOS-DAWG 2010 meeting are to bring people together who have experience or an interest in using MOOS middleware and its substantial set of applications.
The objectives of the MOOS-DAWG 2010 meeting are to bring people together who have experience or an interest in using MOOS middleware and its substantial set of applications.
Deleted lines 8-14:
MOOS-IvP (pronounced "moose i-v-p") is a set of Open Source C++ modules for controlling the full operation of an autonomous marine vehicle. MOOS modules are distinct processes running on the vehicle's CPU, communicating via a single database process in a publish-subscribe manner. The IvP Helm is a single MOOS process dedicated to autonomy decision making composed of distinct vehicle behavior modules. The ability to simply and freely interchange and improve upon modules is a primary objective of the architecture. MOOS ``modules'' refer to MOOS processes and IvP ``modules'' refer to IvP Helm behaviors.\\
\\
'''MOOS''' stands for "Mission Oriented Operating Suite", and '''IvP''' stands for "Interval Programming".
Added lines 5-7:
The 2010 Working Group Meeting for MOOS developers and practitioners will be held in Cambridge
Massachusetts, August 24-25th, on the campus of the Massachusetts Institute of Technology.
Changed lines 4-6 from:
!!Welcome to MOOS-DAWG 2010 \\
!!!A Working Group meeting for Developers of MOOS-based software and
\\
!!!A Working Group meeting for Developers of MOOS-based software and
\\
to:
!Welcome to MOOS-DAWG 2010 \\
!!!!A Working Group meeting for Developers of MOOS-based software and \\
!!!!A Working Group meeting for Developers of MOOS-based software and \\
Changed lines 4-5 from:
!!Welcome to the MOOS-IvP Home Page
to:
!!Welcome to MOOS-DAWG 2010 \\
!!!A Working Group meeting for Developers of MOOS-based software and
!!!A Working Group meeting for Developers of MOOS-based software and
Changed line 8 from:
MOOS stands for "Mission Oriented Operating Suite", and IvP stands for "Interval Programming".
to:
'''MOOS''' stands for "Mission Oriented Operating Suite", and '''IvP''' stands for "Interval Programming".
Changed line 4 from:
MOOS-IvP (pronounced "moose i-v-p") is a set of Open Source C++ modules for controlling the full operation of an autonomous marine vehicle. MOOS modules are distinct processes running on the vehicle's CPU, communicating via a single database process in a publish-subscribe manner. The IvP Helm is a single MOOS process dedicated to autonomy decision making composed of distinct vehicle behavior modules. The ability to simply and freely interchange and improve upon modules is a primary objective of the architecture. MOOS ``modules'' refer to MOOS processes and IvP ``modules'' refer to IvP Helm behaviors.
to:
MOOS-IvP (pronounced "moose i-v-p") is a set of Open Source C++ modules for controlling the full operation of an autonomous marine vehicle. MOOS modules are distinct processes running on the vehicle's CPU, communicating via a single database process in a publish-subscribe manner. The IvP Helm is a single MOOS process dedicated to autonomy decision making composed of distinct vehicle behavior modules. The ability to simply and freely interchange and improve upon modules is a primary objective of the architecture. MOOS ``modules'' refer to MOOS processes and IvP ``modules'' refer to IvP Helm behaviors.\\
Changed lines 1-12 from:
Welcome to PmWiki!
A local copy of PmWiki's
documentation has been installed along with the software,
and is available via the [[PmWiki/documentation index]].
To continue setting up PmWiki, see [[PmWiki/initial setup tasks]].
The [[PmWiki/basic editing]] page describes how to create pages
in PmWiki. You can practice editingin the [[wiki sandbox]].
More information about PmWikiavailable from http://www.pmwiki.org .
A local copy of PmWiki's
documentation has been installed along with the software,
and is available via the [[PmWiki/documentation index]].
To continue setting up PmWiki, see [[PmWiki/initial setup tasks]].
The [[PmWiki/basic editing]] page describes how to create pages
in PmWiki. You can practice editing
More information about PmWiki
to:
!!Welcome to the MOOS-IvP Home Page
MOOS-IvP (pronounced "moose i-v-p") is a set of Open Source C++ modules for controlling the full operation of an autonomous marine vehicle. MOOS modules are distinct processes running on the vehicle's CPU, communicating via a single database process in a publish-subscribe manner. The IvP Helm is a single MOOS process dedicated to autonomy decision making composed of distinct vehicle behavior modules. The ability to simply and freely interchange and improve upon modules is a primary objective of the architecture. MOOS ``modules'' refer to MOOS processes and IvP ``modules'' refer to IvP Helm behaviors.
MOOS stands for "Mission Oriented Operating Suite", and IvP stands for "Interval Programming".
MOOS-IvP (pronounced "moose i-v-p") is a set of Open Source C++ modules for controlling the full operation of an autonomous marine vehicle. MOOS modules are distinct processes running on the vehicle's CPU, communicating via a single database process in a publish-subscribe manner. The IvP Helm is a single MOOS process dedicated to autonomy decision making composed of distinct vehicle behavior modules. The ability to simply and freely interchange and improve upon modules is a primary objective of the architecture. MOOS ``modules'' refer to MOOS processes and IvP ``modules'' refer to IvP Helm behaviors.
MOOS stands for "Mission Oriented Operating Suite", and IvP stands for "Interval Programming".