Home

This is a public Wiki, no confidential information to go in here!

AAF Deployment 2015

A number of pages on strands_management (restricted access) describe the AAF scenario in greater detail:

• General Scenario description
  • Bellbot (lead by Yiannis)
  • Walking Group (lead by Christian D)
  • Info Terminal (lead by Michi)
• Setup Network etc. at AAF
• General task and Deliverables for yr2
• Overview of STRANDS packaging and releasing procedures

General structure

• The deployment shall be based on released packages on indigo amd64
• This aaf_deployment repository is meant solely for AAF-specific packages, anything that has a wider use outside the AAF deployment shall go in dedicated packages, e.g. in strands_apps.
• Contributions are via pull requests only and rigorous code review will take place, in particular after the feature freeze milestone.

Milestones

1. AAF 2015 Feature Freeze 2/4/15:

• All features implemented for the different task
• A "global" scheduling approach working
• Basic GUIs in place with functionality
• The system will be ran continuously at UoL and Vienna from this point onwards, with bug fixes being integrated as soon as they arrive.

2. AAF 2015 Pre-Deployment 13/4/15:

• Henry will perform 3 days at AAF, based on the released packages
• The pre-deployment will comprise a staff training session, to empower AAF members of staff to operate the robot and fill confident about using it
• The interfaces and tasks need to be completed by this milestone, as staff training will be based on these interfaces. Minor design tweaks allowed based on feedback from staff. No structural changes in program logic or code structure beyond this point. No new features to be added either.

3. AAF 2015 Deployment 11/5/15:

• Start of the actual deployment for 30 days (including weekends)

Henry@AAF

• For the deployment, Henry will be remotely administrated by the STRANDS team (check https://github.com/strands-project/strands_management/wiki/Y2-Integration-Scenarios for details to log in)
• On site, two laptops are provided for staff interactions and robot monitoring, one in Tobias' and Denise's AAF office, and one at the reception desk
  • The control interface (web service) shall be running on this:
    • scheduling bellbot tasks
    • displaying the robots current screen
    • seeing the robot on a map
    • scheduling other tasks
    • monitoring the robot's health (battery, disk space)
  • The laptop in the AAF office is also the control-PC, running mongodb replication and serving the websites for the control interfaces (see above)
• The docking station will be in the reception for Henry to approach whenever needed autonomously
• An additional charging opportunity is in the AAF office by cable, an non-interruptable "maintenance" task shall be implemented to call the robot into the office for maintenance and charging, where it will be explicitly released again for other jobs by clicking in the GUI
• (Video-)Recording will be disabled in the therapy wing (AAF to indicate the topological nodes that should be excluded)
• An additional web cam shall be place above the screen for recording interactions. This shall be continuously recording data (using data_compression node) whenever permitted at low framerate.
• Data will be uploaded during charging period to the control-PC