Abstract: A system for contactless operation of an aircraft lavatory door comprises a controller operatively connected to control an actuator for opening and closing a lavatory door. A gesture sensing system is operatively connected to the controller for sending gesture data to the controller indicative of a user gesturing for the actuator to actuate. A mmWave radar sensing system is operatively connected to the controller to indicate user presence. The controller includes machine readable instructions configured to verify gesture input from the gesture sensing system using input from the mmWave radar sensing system before controlling the actuator to open or close the lavatory door.

Abstract: A system for contactless operation of an aircraft lavatory door comprises a controller operatively connected to control an actuator for opening and closing a lavatory door. A gesture sensing system is operatively connected to the controller for sending gesture data to the controller indicative of a user gesturing for the actuator to actuate. A mmWave radar sensing system is operatively connected to the controller to indicate user presence. The controller includes machine readable instructions configured to verify gesture input from the gesture sensing system using input from the mmWave radar sensing system before controlling the actuator to open or close the lavatory door.

Abstract: A touchless system for an aircraft cabin is disclosed. The system includes machine-readable codes placed on passenger seats and other aircraft surfaces that may be scanned and linked to cabin control systems through an application installed on personal portable electronic devices. The system also includes a communication system linked to the personal portable electronic devices via the application and linked to the cabin control systems that facilitates the control of one or more control systems by the personal portable electronic device. One of the cabin control systems is configured as an overhead storage container configured with a gesture sensing system, allowing the storage lid to be opened through specific gestures.

Abstract: Mechanisms to persist object relations are provided. A project is defined as a series of interrelated objects having dependencies and relationships with one another. The dependencies and relationships are maintained via a storage organization for files that define the objects within a project storage environment for the project. Thus, the dependencies and relationships are not maintained via hardcoded instructions or references that are included within the files.

Abstract: Techniques managing complex dependencies in a file-based team environment are provided. A software module is represented as an object. The object is defined via a file. The file includes relationships, and some of the relationships define dependencies to other objects. In some cases, attributes for the object are also included in the file and are defined via references to still other objects. The relationships and the attributes are carried with the object via the file.

Abstract: A computer system for detecting banking frauds in historical data and future transactions from a user supplied specimen set of fraudulent transactions can include: a user console that receives a type of fraud and a plurality of known fraudulent banking transactions associated with the type of fraud from the user; a first set of clue detectors operating on the plurality of known fraudulent banking transactions from the user; a clue detector archive that stores a second set of clue detectors, wherein each of the stored second set of clue detectors has a score that exceeds a threshold value for each clue detector; and a backpropagation neural network that calculates a weight for the stored second set of clue detectors using a learning scheme, wherein a fraud scenario is created based on the stored second set of clue detectors and corresponding weights.

Abstract: Mechanisms to persist object relations are provided. A project is defined as a series of interrelated objects having dependencies and relationships with one another. The dependencies and relationships are maintained via a storage organization for files that define the objects within a project storage environment for the project. Thus, the dependencies and relationships are not maintained via hardcoded instructions or references that are included within the files.

Abstract: Mechanisms to persist object relations are provided. A project is defined as a series of interrelated objects having dependencies and relationships with one another. The dependencies and relationships are maintained via a storage organization for files that define the objects within a project storage environment for the project. Thus, the dependencies and relationships are not maintained via hardcoded instructions or references that are included within the files.

Abstract: Mechanisms for sharing attributes between objects are provided. An object includes a special designation for at least one component, which is identified as a shared attribute. Data associated with the shared attribute is populated and managed from a central location within a processing environment. Multiple instances of a same object or of entirely different objects can reference, declare, and use the data from the central location.

Abstract: Mechanisms to support object-oriented version control operations are provided. A user manipulates and views a project from an object viewpoint and within an object module. The user performs version control operations using object handles. The object handles are resolved to specific file references and the specific file references are used to process legacy version control commands utilizing a legacy version control system in a manner that is transparent to the user.

Abstract: Mechanisms to support multiple name space aware projects are provided. Multiple roots of a project declare multiple namespacing mechanisms. Resources of the project can utilize each of the multiple namespacing mechanisms. In some cases, a particular resource of the project can override and use a foreign namespace that is associated with a different project hierarchy even while that particular resource resides within a project hierarchy associated with the original project and even while the project hierarchy does not declare, at the root, the foreign namespace.

Abstract: Mechanisms to support orphaned and partially configured objects are provided. A project includes a variety of objects. At least one object is designated as an orphaned object. The orphaned object lacks complete configuration details. Other objects of the project depend on the orphaned object and yet the other objects can load and process within the project as if the orphaned object was fully configured and available.

Abstract: Mechanisms to support fine-grain namespacing are provided. When an object is to be loaded within a processing environment, a specific namespace for that object is dynamically resolved during the load. That namespace can be dynamically resolved via object inheritance, via specific object-attribute declaration, and/or via consultation with a namespace object.

Abstract: Mechanisms to support orphaned and partially configured objects are provided. A project includes a variety of objects. At least one object is designated as an orphaned object. The orphaned object lacks complete configuration details. Other objects of the project depend on the orphaned object and yet the other objects can load and process within the project as if the orphaned object was fully configured and available.

Abstract: Mechanisms to support object-oriented version control operations are provided. A user manipulates and views a project from an object viewpoint and within an object module. The user performs version control operations using object handles. The object handles are resolved to specific file references and the specific file references are used to process legacy version control commands utilizing a legacy version control system in a manner that is transparent to the user.

Abstract: Mechanisms to persist object relations are provided. A project is defined as a series of interrelated objects having dependencies and relationships with one another. The dependencies and relationships are maintained via a storage organization for files that define the objects within a project storage environment for the project. Thus, the dependencies and relationships are not maintained via hardcoded instructions or references that are included within the files.

Abstract: Mechanisms to support object-oriented version control operations are provided. A user manipulates and views a project from an object viewpoint and within an object module. The user performs version control operations using object handles. The object handles are resolved to specific file references and the specific file references are used to process legacy version control commands utilizing a legacy version control system in a manner that is transparent to the user.

Abstract: Mechanisms to persist object relations are provided. A project is defined as a series of interrelated objects having dependencies and relationships with one another. The dependencies and relationships are maintained via a storage organization for files that define the objects within a project storage environment for the project. Thus, the dependencies and relationships are not maintained via hardcoded instructions or references that are included within the files.

Abstract: Techniques managing complex dependencies in a file-based team environment are provided. A software module is represented as an object. The object is defined via a file. The file includes relationships, and some of the relationships define dependencies to other objects. In some cases, attributes for the object are also included in the file and are defined via references to still other objects. The relationships and the attributes are carried with the object via the file.

Abstract: Mechanisms to support multiple name space aware projects are provided. Multiple roots of a project declare multiple namespacing mechanisms. Resources of the project can utilize each of the multiple namespacing mechanisms. In some cases, a particular resource of the project can override and use a foreign namespace that is associated with a different project hierarchy even while that particular resource resides within a project hierarchy associated with the original project and even while the project hierarchy does not declare, at the root, the foreign namespace.