Abstract: A rules engine (RE) may operate in conjunction with a database providing functionality, such as transactional support in data access environments on behalf of tenants. The database may have a data repository accessible by multiple tenants, and tenants may have a private context. RE rules may be defined in the data repository having an extension point corresponding to an extension defined in the private context. Execution of database functionality may affect data defined in the database. Execution of RE rules corresponding to database functionality affects corresponding data associated with the RE. Various techniques, e.g., fact handles, event listeners, etc. may be used to coordinate tracking and synchronizing changes between RE data and/or the database. A flag or other indicator may signify state preservation between multiple calls to the database and/or the RE, e.g., to support analysis involving transactions having overlapping intermediary results such as results from performing data lookups.

Abstract: Implementation of a guided rules editor comprises displaying a view of a user interface (UI) of the guided rules editor to a user on the client device. Metadata of an organization to which the user belongs is fetched and used to identify which data of the organization is eligible for rule creation and attributes of the metadata are used to determine a layout of the one or more UI selection elements. One or more UI selection elements are rendered in one or more positions in the view on a display screen according to the layout and at least a portion of the one or more UI selection elements are populated with the data of the organization. Responsive to receiving user input of the one or more UI selection elements, an organization-specific rule is generated and saved to a data repository for execution by a rules engine after rule compilation.

Abstract: Implementation of a guided rules editor comprises displaying a view of a user interface (UI) of the guided rules editor to a user on the client device. Metadata of an organization to which the user belongs is fetched and used to identify which data of the organization is eligible for rule creation and attributes of the metadata are used to determine a layout of the one or more UI selection elements. One or more UI selection elements are rendered in one or more positions in the view on a display screen according to the layout and at least a portion of the one or more UI selection elements are populated with the data of the organization. Responsive to receiving user input of the one or more UI selection elements, an organization-specific rule is generated and saved to a data repository for execution by a rules engine after rule compilation.

Abstract: Implementation of a guided rules editor comprises displaying a view of a user interface (UI) of the guided rules editor to a user on the client device. Metadata of an organization to which the user belongs is fetched and used to identify which data of the organization is eligible for rule creation and attributes of the metadata are used to determine a layout of the one or more UI selection elements. One or more UI selection elements are rendered in one or more positions in the view on a display screen according to the layout and at least a portion of the one or more UI selection elements are populated with the data of the organization. Responsive to receiving user input of the one or more UI selection elements, an organization-specific rule is generated and saved to a data repository for execution by a rules engine after rule compilation.

Abstract: Implementation of a guided rules editor includes a rule compilation process comprising receiving, by an event handler, a compile rules event from a process external to the rule compiler. A set of rules is retrieved from a database and loading the set of rules into a memory by the event handler. Responsive to identifying any template rules, data is bound to the template rules. Both the template rules and any non-template rules are translated into a rules language specification. A rule compilation process is performed asynchronously from a rule execution process to translate the rule language specification into a knowledge base that is to be used as input by a rule execution process. A compile completion event is emitted at compile completion.

Abstract: A rules engine (RE) may operate in conjunction with a database providing functionality, such as transactional support in data access environments on behalf of tenants. The database may have a data repository accessible by multiple tenants, and tenants may have a private context. RE rules may be defined in the data repository having an extension point corresponding to an extension defined in the private context. Execution of database functionality may affect data defined in the database. Execution of RE rules corresponding to database functionality affects corresponding data associated with the RE. Various techniques, e.g., fact handles, event listeners, etc. may be used to coordinate tracking and synchronizing changes between RE data and/or the database. A flag or other indicator may signify state preservation between multiple calls to the database and/or the RE, e.g., to support analysis involving transactions having overlapping intermediary results such as results from performing data lookups.

Abstract: Implementation of a guided rules editor comprises displaying a view of a user interface (UI) of the guided rules editor to a user on the client device. Metadata of an organization to which the user belongs is fetched and used to identify which data of the organization is eligible for rule creation and attributes of the metadata are used to determine a layout of the one or more UI selection elements. One or more UI selection elements are rendered in one or more positions in the view on a display screen according to the layout and at least a portion of the one or more UI selection elements are populated with the data of the organization. Responsive to receiving user input of the one or more UI selection elements, an organization-specific rule is generated and saved to a data repository for execution by a rules engine after rule compilation.

Abstract: A rules engine (RE) may operate in conjunction with a database providing functionality, such as transactional support in data access environments on behalf of tenants. The database may have a data repository accessible by multiple tenants, and tenants may have a private context. RE rules may be defined in the data repository having an extension point corresponding to an extension defined in the private context. Execution of database functionality may affect data defined in the database. Execution of RE rules corresponding to database functionality affects corresponding data associated with the RE. Various techniques, e.g., fact handles, event listeners, etc. may be used to coordinate tracking and synchronizing changes between RE data and/or the database. A flag or other indicator may signify state preservation between multiple calls to the database and/or the RE, e.g., to support analysis involving transactions having overlapping intermediary results such as results from performing data lookups.

Abstract: Implementation of a guided rules editor comprises displaying a view of a user interface (UI) of the guided rules editor to a user on the client device. Metadata of an organization to which the user belongs is fetched and used to identify which data of the organization is eligible for rule creation and attributes of the metadata are used to determine a layout of the one or more UI selection elements. One or more UI selection elements are rendered in one or more positions in the view on a display screen according to the layout and at least a portion of the one or more UI selection elements are populated with the data of the organization. Responsive to receiving user input of the one or more UI selection elements, an organization-specific rule is generated and saved to a data repository for execution by a rules engine after rule compilation.

Abstract: A rules engine (RE) may operate in conjunction with a database providing functionality, such as transactional support in data access environments on behalf of tenants. The database may have a data repository accessible by multiple tenants, and tenants may have a private context. RE rules may be defined in the data repository having an extension point corresponding to an extension defined in the private context. Execution of database functionality may affect data defined in the database. Execution of RE rules corresponding to database functionality affects corresponding data associated with the RE. Various techniques, e.g., fact handles, event listeners, etc. may be used to coordinate tracking and synchronizing changes between RE data and/or the database. A flag or other indicator may signify state preservation between multiple calls to the database and/or the RE, e.g., to support analysis involving transactions having overlapping intermediary results such as results from performing data lookups.

Abstract: Implementation of a guided rules editor comprises displaying a view of a user interface (UI) of the guided rules editor to a user on the client device. Metadata of an organization to which the user belongs is fetched and used to identify which data of the organization is eligible for rule creation and attributes of the metadata are used to determine a layout of the one or more UI selection elements. One or more UI selection elements are rendered in one or more positions in the view on a display screen according to the layout and at least a portion of the one or more UI selection elements are populated with the data of the organization. Responsive to receiving user input of the one or more UI selection elements, an organization-specific rule is generated and saved to a data repository for execution by a rules engine after rule compilation.

Abstract: Apparatuses and methods for calibrating a 3D printer are disclosed. A 3D printer toolhead may include mechanisms for detecting when a portion of the toolhead comes into contact with a build surface. A process for detecting the distance from the toolhead to the build surface is disclosed using these mechanisms. A further method of calibrating a 3D printer by measuring a plurality of points on a build surface is also disclosed.

Abstract: Search query result set count estimation is described. A system parses data set query that includes first query attribute and second query attribute. The system identifies first hierarchy of connected nodes including a first node representing a first query attribute, and a second hierarchy of other connected nodes including a second node representing a second query attribute. The system identifies a directed arc connecting first correlated node in first hierarchy to second correlated node in second hierarchy. The system identifies cross-hierarchy probabilities of correlations between values of a first attribute represented by the first correlated node and values of a second attribute represented by the second correlated node.

Abstract: Apparatuses and methods for calibrating a 3D printer are disclosed. A 3D printer toolhead may include mechanisms for detecting when a portion of the toolhead comes into contact with a build surface. A process for detecting the distance from the toolhead to the build surface is disclosed using these mechanisms. A further method of calibrating a 3D printer by measuring a plurality of points on a build surface is also disclosed.

Abstract: The present invention is a small, highly efficient, Low Power-Light Emitting Diode (LP-LED) that operates at low power, currents, and voltages. The LP-LED has a first and second cladding layer with a narrow emissions layer disposed between. A valence quantum well and a conduction quantum well form within the emissions layer. Materials are chosen so that either the valence quantum well or the conduction quantum well has a potential depth much larger than the other quantum well. In some preferred embodiments, the cladding material is chosen to have a low non-radiative recombination rate.

Abstract: The present invention is a small, highly efficient, Low Power-Light Emitting Diode (LP-LED) that operates at low power, currents, and voltages. The LP-LED has a first and second cladding layer with a narrow emissions layer disposed between. A valence quantum well and a conduction quantum well form within the emissions layer. Materials are chosen so that either the valence quantum well or the conduction quantum well has a potential depth much larger than the other quantum well. In some preferred embodiments, the cladding material is chosen to have a low non-radiative recombination rate.

Abstract: Disclosed is an earphone for a hearing device, wherein the earphone is configured to be worn at the ear of a user, the earphone comprising: a speaker housing comprising an output transducer for reproduction of audio signals, wherein the speaker housing has a first side configured to face towards the ear of the user when the earphone is worn by the user, and a second side opposite the first side; an earphone housing configured to retain the speaker housing such that the second side of the speaker housing faces a first side of the earphone housing, wherein the earphone housing has as a second side opposite the first side; a battery compartment for accommodating a replaceable battery, such that the replaceable battery is located at least partly between the second side of the speaker housing and at least a portion of the earphone housing; wherein the earphone comprises a retaining mechanism configured to retain the speaker housing and the earphone housing in a mechanical relationship with each other; wherein the

Abstract: A semiconductor structure for optical power conversion and a method of forming the semiconductor structure are provided. In an aspect, the method may include removing a first portion of the semiconductor structure from a first region, wherein the semiconductor structure comprises a layered photovoltaic structure on a silicon-on-insulator structure. A second portion of the semiconductor structure may be removed from a second region, wherein the second region is located adjacent to the first region, and wherein an insulator layer of the silicon-on-insulator structure is exposed by the removed second portion. A passivation layer pattern may be formed over the semiconductor structure. Electrodes may be formed on portions of the surfaces of the semiconductor structure that are uncovered by the passivation layer.

Abstract: Search query result set count estimation is described. A system parses data set query that includes first query attribute and second query attribute. The system identifies first hierarchy of connected nodes including a first node representing a first query attribute, and a second hierarchy of other connected nodes including a second node representing a second query attribute. The system identifies a directed arc connecting first correlated node in first hierarchy to second correlated node in second hierarchy. The system identifies cross-hierarchy probabilities of correlations between values of a first attribute represented by the first correlated node and values of a second attribute represented by the second correlated node.

Abstract: An engineered ecosystem, moderating eight primary systems—thermal management, atmospheric optimization, radiation controls, hydrological systems, energy systems, material flows, systems management, and built systems—to provide homeostatic regulation of cascading flows of matter and energy.