Site
* %color=#BD614A%'''Payload (backseat driver) interface''':%% standards, best practices, source code availability.
* %color=#BD614A%'''IvP Helm''':%% Application experiences, behavior development.
* %color=#BD614A%'''Mission monitoring''':%% Tools for rendering vehicle operations and tools for
scoping on the MOOSDB.
Participation
Site.Participation History
Hide minor edits - Show changes to output
Changed line 6 from:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by Monday June 5th 2017, by email to:
to:
The MOOS-DAWG'17 meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by Monday June 5th 2017, by email to:
Changed line 6 from:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by June 5th 2015, by email to:
to:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by Monday June 5th 2017, by email to:
Changed line 6 from:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by the July 2015 deadline (exact dated TBD), by email to:
to:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by June 5th 2015, by email to:
Changed line 6 from:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by the TBD July 2015 deadline, by email to:
to:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by the July 2015 deadline (exact dated TBD), by email to:
Changed line 6 from:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by June 10th 2014, by email to:
to:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by the TBD July 2015 deadline, by email to:
Changed line 6 from:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by June 8th 2013, by email to:
to:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by June 10th 2014, by email to:
Changed line 6 from:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by June 1st 2013, by email to:
to:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by June 8th 2013, by email to:
Changed line 6 from:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by June 1st 2011, by email to:
to:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by June 1st 2013, by email to:
Changed line 8 from:
'''%color=#4144BD%admin@moos-dawg.org%%'''
to:
'''%color=#4144BD%moos-dawg@csail.mit.edu%%'''
Changed line 6 from:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by June 18th 2010, by email to:
to:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by June 1st 2011, by email to:
Changed line 8 from:
'''%color=#41A4BD%admin@moos-dawg.org%%'''
to:
'''%color=#4144BD%admin@moos-dawg.org%%'''
Changed line 8 from:
'''%color=#A1C4FD%admin@moos-dawg.org%%'''
to:
'''%color=#41A4BD%admin@moos-dawg.org%%'''
Changed line 8 from:
'''%color=#91C4CD%admin@moos-dawg.org%%'''
to:
'''%color=#A1C4FD%admin@moos-dawg.org%%'''
Changed line 8 from:
'''%color=#61B4CD%admin@moos-dawg.org%%'''
to:
'''%color=#91C4CD%admin@moos-dawg.org%%'''
Changed line 8 from:
'''%color=#61B4CD%submissions@moos-dawg.org%%'''
to:
'''%color=#61B4CD%admin@moos-dawg.org%%'''
Changed line 13 from:
* Practitioners - descriptions of projects using MOOS middleware and applications to field their autonomous systems. Although success stories are welcome, candid descriptions are sought regarding which aspects of the autonomy system are most challenging, and why.
to:
* Practitioners - descriptions of projects using MOOS middleware and applications in their fielded autonomous systems. Although success stories are welcome, candid descriptions are sought regarding which aspects of the autonomy system are most challenging, and why.
Changed line 8 from:
'''%color=#61B4AD%submissions@moos-dawg.org%%'''
to:
'''%color=#61B4CD%submissions@moos-dawg.org%%'''
Changed line 8 from:
'''%color=#61BD4A%"submissions@moos-dawg.org"%%'''
to:
'''%color=#61B4AD%submissions@moos-dawg.org%%'''
Changed line 8 from:
%color=#61BD4A%"submissions@moos-dawg.org"%%
to:
'''%color=#61BD4A%"submissions@moos-dawg.org"%%'''
Changed lines 8-10 from:
"submissions _at_ moos-dawg.org."
to:
%color=#61BD4A%"submissions@moos-dawg.org"%%
Changed line 42 from:
* %color=#BD614A%'''Post mission analysis''':%% Tools for parsing, editing and analyzing mission log files.
to:
* %color=#BD614A%'''Post mission analysis''':%% Tools for parsing, editing and analyzing mission log files.
Changed line 15 from:
* Developers - descriptions of tools or applications that may be tailor-developed for your own project that may be of general interest to other practitioners. Discussions on tools are in a beta (non-release) phase of development are more than welcome.
to:
* Developers - descriptions of tools or applications that may be of general interest to other practitioners, that were perhaps originally tailor-developed for your own project . Discussions on tools in a beta (non-release) phase of development are more than welcome.
Changed line 13 from:
* Practitioners - descriptions of projects using MOOS middleware and applications to field their autonomous systems. Although success stories are welcome, a candid descriptions are sought regarding which aspects of the autonomy system are most challenging, and why.
to:
* Practitioners - descriptions of projects using MOOS middleware and applications to field their autonomous systems. Although success stories are welcome, candid descriptions are sought regarding which aspects of the autonomy system are most challenging, and why.
Changed lines 11-18 from:
to:
Primarily we are seeking abstracts and presentations in one of two categories:
* Practitioners - descriptions of projects using MOOS middleware and applications to field their autonomous systems. Although success stories are welcome, a candid descriptions are sought regarding which aspects of the autonomy system are most challenging, and why.
* Developers - descriptions of tools or applications that may be tailor-developed for your own project that may be of general interest to other practitioners. Discussions on tools are in a beta (non-release) phase of development are more than welcome.
* Practitioners - descriptions of projects using MOOS middleware and applications to field their autonomous systems. Although success stories are welcome, a candid descriptions are sought regarding which aspects of the autonomy system are most challenging, and why.
* Developers - descriptions of tools or applications that may be tailor-developed for your own project that may be of general interest to other practitioners. Discussions on tools are in a beta (non-release) phase of development are more than welcome.
Added line 20:
Changed lines 28-30 from:
* %color=#BD614A%'''Quality Control''':%%
* %color=#BD614A%'''MOOS/MOOS-IvP build system
* %color=#BD614A%'''MOOS/MOOS-IvP build system
to:
* %color=#BD614A%'''Quality Control''':%% Issues related to process of adopting and accepting testing new software releases.
* %color=#BD614A%'''MOOS/MOOS-IvP build system''':%% Issues related to maintaining a build system for third-party software using MOOS or MOOS-IvP trees.
* %color=#BD614A%'''MOOS/MOOS-IvP build system''':%% Issues related to maintaining a build system for third-party software using MOOS or MOOS-IvP trees.
Changed lines 32-33 from:
* %color=#BD614A%'''Mission monitoring''':%% Tools for rendering vehicle operations and tools for
scoping on the MOOSDB.
scoping on the MOOSDB.
to:
* %color=#BD614A%'''Mission monitoring''':%% Tools for rendering vehicle operations and tools for scoping on the MOOSDB.
Deleted lines 13-14:
* %color=#BD614A%'''IvP Helm''':%% Application experiences, behavior development.
Added lines 16-19:
* %color=#BD614A%'''IvP Helm''':%% Application experiences, behavior development.
* %color=#BD614A%'''Payload (backseat driver) interface''':%% standards, best practices, source code availability.
* %color=#BD614A%'''Payload (backseat driver) interface''':%% standards, best practices, source code availability.
Added line 21:
Added line 23:
Added line 25:
Added line 27:
Added line 29:
Changed lines 31-34 from:
* %color=#BD614A%'''Mission monitoring''':%% Tools for rendering vehicle operations and tools for scoping on the MOOSDB.
to:
* %color=#BD614A%'''Mission monitoring''':%% Tools for rendering vehicle operations and tools for
scoping on the MOOSDB.
Changed line 20 from:
* %color=#BD614A%'''Mission planning / Mission configuration''':%%
to:
* %color=#BD614A%'''Mission planning / Mission configuration''':%% Tools for composing, visualizing or automated error checking of mission (or helm behavior) configuration files.
Changed line 18 from:
* %color=#BD614A%'''Acoustic communications''':%%
to:
* %color=#BD614A%'''Acoustic communications''':%% Applications for interfacing with acoustic modems and defining and handling message sets.
Changed lines 21-22 from:
* %color=#BD614A%'''Simulation''':%% Includes simulation of the platform, inter-node communications, and models of the ocean.
* %color=#BD614A%Quality
* %color=#BD614A%Quality
to:
* %color=#BD614A%'''Simulation''':%% Includes simulation of the platform, inter-node communications, and models of the ocean or environment.
* %color=#BD614A%'''Quality Control''':%%
* %color=#BD614A%'''Quality Control''':%%
Changed lines 16-17 from:
* %color=#BD614A%'''MOOS middleware''':%%
to:
* %color=#BD614A%'''MOOS middleware''':%% Issues related to MOOSDB performance and the interface of MOOS applications.
Added line 19:
* %color=#BD614A%'''MOOS on low-powered CPUs''':%% Experiences in porting MOOS to the Gumstix, ARM9, or similar processor families.
Changed line 15 from:
* %color=#BD614A%'''IvP Helm:%% Application experiences, behavior development'''
to:
* %color=#BD614A%'''IvP Helm''':%% Application experiences, behavior development.
Changed lines 15-23 from:
* '''IvP Helm: Application experiences, behavior development'''
* '''MOOS middleware''':
* '''Acoustic communications''':
* Quality
* '''Post mission analysis''': Tools for parsing, editing and analyzing mission log files.
* '''MOOS middleware''':
* '''Acoustic communications''':
* Quality
* '''Post mission analysis''': Tools for parsing, editing and analyzing mission log files.
to:
* %color=#BD614A%'''IvP Helm:%% Application experiences, behavior development'''
* %color=#BD614A%'''MOOS middleware''':%%
* %color=#BD614A%'''Acoustic communications''':%%
* %color=#BD614A%'''Mission planning / Mission configuration''':%%
* %color=#BD614A%'''Simulation''':%% Includes simulation of the platform, inter-node communications, and models of the ocean.
* %color=#BD614A%Quality %%
* %color=#BD614A%'''MOOS/MOOS-IvP build system''':%%
* %color=#BD614A%'''Mission monitoring''':%% Tools for rendering vehicle operations and tools for scoping on the MOOSDB.
* %color=#BD614A%'''Post mission analysis''':%% Tools for parsing, editing and analyzing mission log files.
* %color=#BD614A%'''MOOS middleware''':%%
* %color=#BD614A%'''Acoustic communications''':%%
* %color=#BD614A%'''Mission planning / Mission configuration''':%%
* %color=#BD614A%'''Simulation''':%% Includes simulation of the platform, inter-node communications, and models of the ocean.
* %color=#BD614A%Quality %%
* %color=#BD614A%'''MOOS/MOOS-IvP build system''':%%
* %color=#BD614A%'''Mission monitoring''':%% Tools for rendering vehicle operations and tools for scoping on the MOOSDB.
* %color=#BD614A%'''Post mission analysis''':%% Tools for parsing, editing and analyzing mission log files.
Changed line 14 from:
* '''Payload (backseat driver) interface''': standards, best practices, source code availability.
to:
* %color=#BD614A%'''Payload (backseat driver) interface''':%% standards, best practices, source code availability.
Changed line 14 from:
* '''Payload (backseat driver) interface: standards, best practices, source code availability'''
to:
* '''Payload (backseat driver) interface''': standards, best practices, source code availability.
Changed lines 6-8 from:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by June 18th 2010, by email to
to:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by June 18th 2010, by email to:
"submissions _at_ moos-dawg.org."
"submissions _at_ moos-dawg.org."
Changed lines 6-8 from:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by June 18th 2010, by email to "submissions _at_ moos-dawg.org."
to:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by June 18th 2010, by email to
"submissions _at_ moos-dawg.org."
"submissions _at_ moos-dawg.org."
Changed line 6 from:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by June 18th 2010, by email to submissions@moos-dawg.org.
to:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by June 18th 2010, by email to "submissions _at_ moos-dawg.org."
Changed line 6 from:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract
to:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract by June 18th 2010, by email to submissions@moos-dawg.org.
Changed line 6 from:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present will need to submit an abstract
to:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present should submit an abstract
Changed lines 6-10 from:
Topic areas:
to:
The MOOS-DAWG meeting will consist of 20-30 minute talks on material submitted by meeting participants. Those wishing to present will need to submit an abstract
!!!Topic areas:
!!!Topic areas:
Changed line 17 from:
* '''Post mission analysis''':
to:
* '''Post mission analysis''': Tools for parsing, editing and analyzing mission log files.
Changed line 13 from:
* Simulation: Includes simulation of the platform, inter-node communications, and models of the ocean.
to:
* '''Simulation''': Includes simulation of the platform, inter-node communications, and models of the ocean.
Changed line 16 from:
* '''Mission monitoring''':
to:
* '''Mission monitoring''': Tools for rendering vehicle operations and tools for scoping on the MOOSDB.
Changed line 13 from:
* Simulation: Includes physical platform simulation, communications simulation and models and methods for simulating the ocean environment.
to:
* Simulation: Includes simulation of the platform, inter-node communications, and models of the ocean.
Added lines 1-3:
(:notitle:)
(:notitlegroup:)
(:notitlegroup:)
Changed lines 8-11 from:
* Payload (backseat driver) interface: standards, best practices, source code availability
* Acoustic communications:
* Acoustic communications:
to:
* '''Payload (backseat driver) interface: standards, best practices, source code availability'''
* '''IvP Helm: Application experiences, behavior development'''
* '''MOOS middleware''':
* '''Acoustic communications''':
* '''IvP Helm: Application experiences, behavior development'''
* '''MOOS middleware''':
* '''Acoustic communications''':
Changed lines 14-15 from:
* Mission monitoring
* Post mission analysis
to:
* Quality
* '''MOOS/MOOS-IvP build system''':
* '''Mission monitoring''':
* '''Post mission analysis''':
* '''MOOS/MOOS-IvP build system''':
* '''Mission monitoring''':
* '''Post mission analysis''':
Added lines 1-12:
!! Participation Information
Topic areas:
* Payload (backseat driver) interface: standards, best practices, source code availability
* IvP Helm: Application experiences, behavior development
* MOOS middleware:
* Acoustic communications:
* '''Mission planning / Mission configuration''':
* Simulation: Includes physical platform simulation, communications simulation and models and methods for simulating the ocean environment.
* Mission monitoring
* Post mission analysis
Topic areas:
* Payload (backseat driver) interface: standards, best practices, source code availability
* IvP Helm: Application experiences, behavior development
* MOOS middleware:
* Acoustic communications:
* '''Mission planning / Mission configuration''':
* Simulation: Includes physical platform simulation, communications simulation and models and methods for simulating the ocean environment.
* Mission monitoring
* Post mission analysis