Participation
Site.Participation History
Hide minor edits - Show changes to markup
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:
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:
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:
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:
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:
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:
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:
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:
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:
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:
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:
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:
admin@moos-dawg.org
moos-dawg@csail.mit.edu
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:
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:
submissions@moos-dawg.org
admin@moos-dawg.org
- 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.
- 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.
submissions@moos-dawg.org
submissions@moos-dawg.org
"submissions@moos-dawg.org"
submissions@moos-dawg.org
"submissions@moos-dawg.org"
"submissions@moos-dawg.org"
"submissions _at_ moos-dawg.org."
"submissions@moos-dawg.org"
- Post mission analysis: Tools for parsing, editing and analyzing mission log files.
- Post mission analysis: Tools for parsing, editing and analyzing mission log files.
- 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.
- 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.
- 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.
- 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.
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.
- Quality Control:
- MOOS/MOOS-IvP build system:
- Quality Control: Issues related to process of adopting and accepting testing new software releases.
- MOOS/MOOS-IvP build system: Issues related to maintaining a build system for third-party software using MOOS or MOOS-IvP trees.
- Mission monitoring: Tools for rendering vehicle operations and tools for
scoping on the MOOSDB.
- Mission monitoring: Tools for rendering vehicle operations and tools for scoping on the MOOSDB.
- Payload (backseat driver) interface: standards, best practices, source code availability.
- IvP Helm: Application experiences, behavior development.
- IvP Helm: Application experiences, behavior development.
- Payload (backseat driver) interface: standards, best practices, source code availability.
- Mission monitoring: Tools for rendering vehicle operations and tools for scoping on the MOOSDB.
- Mission monitoring: Tools for rendering vehicle operations and tools for
scoping on the MOOSDB.
- Mission planning / Mission configuration:
- Mission planning / Mission configuration: Tools for composing, visualizing or automated error checking of mission (or helm behavior) configuration files.
- Acoustic communications:
- Acoustic communications: Applications for interfacing with acoustic modems and defining and handling message sets.
- Simulation: Includes simulation of the platform, inter-node communications, and models of the ocean.
- Quality
- Simulation: Includes simulation of the platform, inter-node communications, and models of the ocean or environment.
- Quality Control:
- MOOS middleware:
- MOOS middleware: Issues related to MOOSDB performance and the interface of MOOS applications.
- MOOS on low-powered CPUs: Experiences in porting MOOS to the Gumstix, ARM9, or similar processor families.
- IvP Helm: Application experiences, behavior development
- IvP Helm: Application experiences, behavior development.
- IvP Helm: Application experiences, behavior development
- MOOS middleware:
- Acoustic communications:
- Mission planning / Mission configuration:
- Simulation: Includes simulation of the platform, inter-node communications, and models of the ocean.
- Quality
- MOOS/MOOS-IvP build system:
- Mission monitoring: Tools for rendering vehicle operations and tools for scoping on the MOOSDB.
- Post mission analysis: Tools for parsing, editing and analyzing mission log files.
- IvP Helm: Application experiences, behavior development
- MOOS middleware:
- Acoustic communications:
- Mission planning / Mission configuration:
- Simulation: Includes simulation of the platform, inter-node communications, and models of the ocean.
- Quality
- MOOS/MOOS-IvP build system:
- Mission monitoring: Tools for rendering vehicle operations and tools for scoping on the MOOSDB.
- Post mission analysis: Tools for parsing, editing and analyzing mission log files.
- Payload (backseat driver) interface: standards, best practices, source code availability.
- Payload (backseat driver) interface: standards, best practices, source code availability.
- Payload (backseat driver) interface: standards, best practices, source code availability
- Payload (backseat driver) interface: standards, best practices, source code availability.
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."
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."
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."
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."
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.
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."
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
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.
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
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
Topic areas:
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:
- Post mission analysis:
- Post mission analysis: Tools for parsing, editing and analyzing mission log files.
- Simulation: Includes simulation of the platform, inter-node communications, and models of the ocean.
- Simulation: Includes simulation of the platform, inter-node communications, and models of the ocean.
- Mission monitoring:
- Mission monitoring: Tools for rendering vehicle operations and tools for scoping on the MOOSDB.
- Simulation: Includes physical platform simulation, communications simulation and models and methods for simulating the ocean environment.
- Simulation: Includes simulation of the platform, inter-node communications, and models of the ocean.
(:notitle:) (:notitlegroup:)
- Payload (backseat driver) interface: standards, best practices, source code availability
- IvP Helm: Application experiences, behavior development
- MOOS middleware:
- Acoustic communications:
- Payload (backseat driver) interface: standards, best practices, source code availability
- IvP Helm: Application experiences, behavior development
- MOOS middleware:
- Acoustic communications:
- Mission monitoring
- Post mission analysis
- Quality
- MOOS/MOOS-IvP build system:
- Mission monitoring:
- Post mission analysis:
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