Requirements for Web Automation
Meeting notes 3-17-2004 (Babak Sapir, Anne Wright)
A web-based interface for downloading and running CLARAty software should provide the following functionality:
- Modularity: allow the user to select and download only packages he/she is interested in. System automatically computes the dependent modules.
- Architecture: ask user which architecture(s) they would be interested in running CLARAty on (hardware ix86, ppc, etc and OS: Linux, VxWorks, etc)
- Supporting libraries: create a shared space at an institution that mirrors an installation of all necessary 3rd party packages needed to run CLARAty on the desired architecture. Remember settings associated with each locality. Some localities (equivalent of "site" concept in YaM) may be:
- JPL Telerobotics
- ARC IC-AFS
- CMU Robotics Institute
- Laptop: users of the web automation system will be able to download and install everything they need to get started with claraty.
- The claraty development environment will include the “claraty staging area” and the “sandbox”
- Description of “claraty staging area”:
The “claraty staging area” provides the supporting code needed to run claraty. It consists of:- Packages
- Configuration files
- Scripts
- Selection of external modules (select architecture)
- Description of "sandbox":
The sandbox is unique to each individual. This is the area where development is done on claraty code. It includes the CLARAty source code.