 |
|
|
|
|
|
 |
|
|
|
Specific Goals |
|
|
|
To develop the architecture for the MMC in sufficient detail in order to: |
|
|
|
- Define the context of each element within the entire architecture. For example any individual element cannot be properly designed without reference to its interfaces with the rest of the system.
- List the functional requirements for each area.
- Allocate responsibilities for execution of each task and set time lines.
- Develop the mechanisms to proceed in a collaborative manner.
|
|
|
|
Food for Thought |
|
|
|
There seems to be general consensus that we want a common Web-based control interface for basic microscope functions (for example, the interface that Nestor now has). It also appears that we desire a more complex interface to provide higher level functionality that may or may not be practical to implement on the Web (for example, Timbuktu to existing interfaces). |
|
|
|
In that light, these are some of the questions that need to be discussed and answered during the discussions: |
|
|
|
- Discuss this overall plan
- Can the existing hardware (at our sites) be configured to use this architecture?
- Can the API be extensible? Most detectors have a unique interface.
- What is the role of integrators such as Gatan/Digital Micrograph (we don't want to usurp them)?
- What is the role of remote control apps. like Timbuktu?
- NT-based vs open architecture?
- Decide on a hardware API set
- Determine the time schedule for inputs from industry and test tools from MMC
|
|
|
|
Othe MMC Issues: MMC is not just about remote control! |
|
|
|
- How can diagnostic tools be integrated?
- How do we interact with DOE 2000, NGI,....
- Global file systems for data storage
- It is about collaboration. The whole must be bigger than the sum of its parts.
- Educational outreach
|
|
