Abstract: Methods and systems for performing robotically-assisted surgery in conjunction with intra-operative imaging. A method includes moving a robotic arm with respect to a patient and an imaging device to move an end effector of the robotic arm to a pre-determined position and orientation with respect to the patient based on imaging data of the patient obtained by the imaging device. The robotic arm maintains the end effector in the pre-determined position and orientation with respect to the patient and does not collide with the imaging device or with the patient when the imaging device moves with respect to the patient.

Abstract: A remote eye examination method includes initiating a remote chat session between a local computing device coupled to a phoropter, and a remote computer, and initializing the phoropter for remote control by the remote computer. Then, a multi-colored lamp is activated in a first color until a determination that a refractory examination utilizing the phoropter has commenced. Thereafter, responsive to a determination that the examination has commenced, the multi-colored lamp changes to a second color, and movement of portions of the phoropter are commanded as directed by the remote computer, data is recorded into a patient record and a progression of the examination monitored. Finally, on condition that a threshold period of time before a conclusion of the refractory examination is detected, the multi-colored lamp changes to a third color and upon conclusion of the examination, a message transmitted to a remote account indicating access to the patient record.

Abstract: A remote eye examination method includes initiating a remote chat session between a local computing device coupled to a phoropter, and a remote computer, and initializing the phoropter for remote control by the remote computer. Then, a multi-colored lamp is activated in a first color until a determination that a refractory examination utilizing the phoropter has commenced. Thereafter, responsive to a determination that the examination has commenced, the multi-colored lamp changes to a second color, and movement of portions of the phoropter are commanded as directed by the remote computer, data is recorded into a patient record and a progression of the examination monitored. Finally, on condition that a threshold period of time before a conclusion of the refractory examination is detected, the multi-colored lamp changes to a third color and upon conclusion of the examination, a message transmitted to a remote account indicating access to the patient record.

Abstract: A media display system includes a first display device configured to display a first graphic image. The media display system also includes a second display device including a transparent display configured to display a second graphic image. The first display device and the second display device are spaced apart from one another at a distance, such that the first graphic image overlaps with the second graphic image to collectively form a holographic-like presentation.

Abstract: A rotating machining device for machining a work piece includes a support housing adapted for mounting on the work piece and a headstock rotatably mounted on the support housing about an axis. The headstock including an internal gear. A drive module is arranged to drive rotation of the headstock about the axis and at least one gear connection is formed between the internal gear and the drive module. The at least one gear connection is positioned radially inside of an outer diameter of the support housing to protect an operator from a pinch point associated with the at least one gear connection.

Abstract: A rotating machining device for machining a work piece includes a support housing adapted for mounting on the work piece and a headstock rotatably mounted on the support housing about an axis. The headstock including an internal gear. A drive module is arranged to drive rotation of the headstock about the axis and at least one gear connection is formed between the internal gear and the drive module. The at least one gear connection is positioned radially inside of an outer diameter of the support housing to protect an operator from a pinch point associated with the at least one gear connection.

Abstract: The embodiments of the invention described herein employ sophisticated techniques for managing distributed processes in a process automation system. Specifically, one embodiment of the invention implements a general purpose property mechanism in which arbitrary data is attached to any object in the system (e.g., projects, procedures, jobs, job steps, resources, etc), thereby providing a convenient way to configure the system without modifying the underlying program code. In addition, in one embodiment, a three-tier hierarchy of data object is employed: “projects,” “procedures,” and “steps” (or “projects,” “jobs” and “job steps” during runtime). A property may be attached to any object on any tier of the hierarchy to configure that object and (potentially) all of the objects which reference the property. The properties and property sheets may be attached both statically (before runtime) and dynamically (during runtime).

Abstract: The embodiments of the invention described herein employ sophisticated techniques for managing distributed processes in a process automation system. Specifically, one embodiment of the invention implements a general purpose property mechanism in which arbitrary data is attached to any object in the system (e.g., projects, procedures, jobs, job steps, resources, etc), thereby providing a convenient way to configure the system without modifying the underlying program code. In addition, in one embodiment, a three-tier hierarchy of data object is employed: “projects,” “procedures,” and “steps” (or “projects,” “jobs” and “job steps” during runtime). A property may be attached to any object on any tier of the hierarchy to configure that object and (potentially) all of the objects which reference the property. The properties and property sheets may be attached both statically (before runtime) and dynamically (during runtime).

Abstract: A multi-tiered process automation system employing a novel property attachment mechanism is described.

Abstract: A method is described comprising: scheduling jobs for a program build to execute in parallel across a plurality of nodes; predicting the files required to complete each of the jobs; and preloading the files to each node prior to the execution of each job.

Abstract: A method implemented within a distributed build system is described comprising: transmitting a first source file from a program build file repository to a first node, the first node using the source file to generate a target file identified in the build process; receiving a request for the first source file from a second node; and redirecting the second node to retrieve the first source file from the first node rather than from the program build file repository.

Abstract: A method is described for executing program builds comprising: scheduling jobs for a program build based on dependencies between files used in the jobs; executing the jobs according to the schedule; collecting file usage information from each of the jobs, the file usage information indicating operations performed on the files in each of the jobs; and analyzing the file usage information to determine whether any one of the jobs resulted in a conflict.

Abstract: The embodiments of the invention described herein employ sophisticated techniques for managing distributed processes in a process automation system. Specifically, one embodiment of the invention implements a general purpose property mechanism in which arbitrary data is attached to any object in the system (e.g., projects, procedures, jobs, job steps, resources, etc), thereby providing a convenient way to configure the system without modifying the underlying program code. In addition, in one embodiment, a three-tier hierarchy of data object is employed: “projects,” “procedures,” and “steps” (or “projects,” “jobs” and “job steps” during runtime). A property may be attached to any object on any tier of the hierarchy to configure that object and (potentially) all of the objects which reference the property. The properties and property sheets may be attached both statically (before runtime) and dynamically (during runtime).

Abstract: The embodiments of the invention described herein employ sophisticated techniques for managing distributed processes in a process automation system. Specifically, one embodiment of the invention implements a general purpose property mechanism in which arbitrary data is attached to any object in the system (e.g., projects, procedures, jobs, job steps, resources, etc), thereby providing a convenient way to configure the system without modifying the underlying program code. In addition, in one embodiment, a three-tier hierarchy of data object is employed: “projects,” “procedures,” and “steps” (or “projects,” “jobs” and “job steps” during runtime). A property may be attached to any object on any tier of the hierarchy to configure that object and (potentially) all of the objects which reference the property. The properties and property sheets may be attached both statically (before runtime) and dynamically (during runtime).

Abstract: The embodiments of the invention described herein employ sophisticated techniques for managing distributed processes in a process automation system. Specifically, one embodiment of the invention implements a general purpose property mechanism in which arbitrary data is attached to any object in the system (e.g., projects, procedures, jobs, job steps, resources, etc), thereby providing a convenient way to configure the system without modifying the underlying program code. In addition, in one embodiment, a three-tier hierarchy of data object is employed: “projects,” “procedures,” and “steps” (or “projects,” “jobs” and “job steps” during runtime). A property may be attached to any object on any tier of the hierarchy to configure that object and (potentially) all of the objects which reference the property. The properties and property sheets may be attached both statically (before runtime) and dynamically (during runtime).

Abstract: A system and method for file management is comprised of hierarchical files systems, referred to as “areas.” There are three types of areas: work areas, staging areas, and edition areas. A work area is a modifiable file system, and, in a work area a user can create, edit, and delete files and directories. A staging area is a read-only file system that supports select versioning operations. Various users of work areas can integrate their work by submitting the contents of their work area to the staging area. In the staging area, developers can compare their work and see how their changes fit together. An edition is a read-only file system, and the contents of a staging area are virtually copied into an edition to create a frozen, read-only snapshot of the contents of the staging area. One use of the system and method for file management is as a website development tool.

Abstract: A method for executing program builds is described comprising: executing jobs for a program build in parallel according to a first job schedule; detecting a recursive build invocation in one of the jobs; analyzing dependency information associated with the recursive build invocation; and based on the analysis, supplementing the first job schedule with additional job schedule data.

Abstract: A method for executing program builds is described comprising: analyzing file dependency information contained within a first file; scheduling jobs for a program build based on the analysis of the dependency information; executing the jobs according to the schedule; collecting file usage information from each of the jobs; and supplementing the file dependency information with the file usage information.

Abstract: A method is described comprising: scheduling jobs for a program build to execute in parallel across a plurality of nodes; predicting the files required to complete each of the jobs; and preloading the files to each node prior to the execution of each job.

Abstract: A method for executing program builds is described comprising: analyzing file dependency information contained within a first file; scheduling jobs for a program build based on the analysis of the dependency information; executing the jobs according to the schedule; collecting file usage information from each of the jobs; and supplementing the file dependency information with the file usage information.