Abstract: A layer stack including a first bonding dielectric material layer, a dielectric metal oxide layer, and a second bonding dielectric material layer is formed over a top surface of a substrate including a substrate semiconductor layer. A conductive material layer is formed by depositing a conductive material over the second bonding dielectric material layer. The substrate semiconductor layer is thinned by removing portions of the substrate semiconductor layer that are distal from the layer stack, whereby a remaining portion of the substrate semiconductor layer includes a top semiconductor layer. A semiconductor device may be formed on the top semiconductor layer.

Abstract: A software developer proxy tool accesses microservice applications for a software development project by connecting the developer proxy tool to a common port on a computer network. The tool implements software and hardware to register a plurality of the microservice applications on connection ports that connect to the developer proxy tool at an address for the common port. Data requests among the microservices are handled by the developer proxy tool via the common port. The tool sequentially queries selected microservice applications on the respective connection ports to determine availability for completing a request. The tool receives responses back from microservices and directs the responses back to the requesting program. Failed requests trigger use of remote or third party microservice applications that may be available over an internet connection.

Abstract: Examples herein describe a self-test process where an integrated circuit includes a test controller responsible for testing a plurality of frames in the memory of an integrated circuit. The test controller can receive a test pattern which the controller duplicates and stores in each of the plurality of frames. However, frames may be non-uniform meaning the frames have varying sizes. As such, some of the frames may only store parts of the test pattern rather than all of it. In any case, the test controller reads out the stored data and generates a checksum which can then be compared to a baseline checksum generated from simulating the integrated circuit using design code to determine whether there is a manufacturing defect in the frames.

Abstract: The subject mater herein relates to database management and, more particularly, to non-equijoin metadata. Various embodiments described herein provide systems, methods, software, and data structures to facilitate non-equijoins of data. Some such embodiments include a data store to hold metadata describing relationships between database tables. The relationships between database tables may include one or more non-equijoins of tables in the form of one or more table-column pairs of a first table being non-equal to one or more table-column pairs of a second table. In some embodiments, the metadata may be used by a query generator to build query statements including one or more non-equijoin.

Abstract: A graphical user interface (GUI) tool is presented to a user for interacting with an underlying database. The GUI tool includes a field selection and attribute selections for the field. The user selects a field and an attribute for that field and is presented with a first list of values retrieved from the database for the selected attribute. Next, the user selects a filter for the attribute within the GUI tool and a second reduced list of values is presented to the user within the GUI tool representing the filtered first list of values acquired by applying the filter.

Abstract: Tools for defining and using custom analysis modules are presented. A generic graphical user interface (GUI) custom analysis tool is presented to a user. The generic GUI custom analysis tool is adapted to receive selections and inputs from the user that define many-to-many relationships in a data store and that include user-defined measures. The inputs are used to generate an instance of a custom analysis module that is capable of being processed against the data store. The instance of the custom analysis module may be stored, recalled, executed, and/or modified from the generic GUI custom analysis tool.

Abstract: Techniques for Product Affinity Analysis are presented. A user interacts with a tool to supply user-defined criteria. The criteria are used to automatically generate code that processes against a data store to collect results that conform to conditions defined by the criteria. The results are used to automatically populate a Product Affinity Analysis chart or grid for the user to view and in some cases dynamically interact with.

Abstract: Techniques for applying segment conditions to measure results are presented. Row and column segment data is acquired from a database according to row and column definitions. A measure calculation is applied against the intersecting row and column segment data. Next, one or more combinations or conditions derived from the row and column definitions are used as a filter to produce filtered results.

Abstract: The subject mater herein relates to database management and, more particularly, to non-equijoin metadata. Various embodiments described herein provide systems, methods, software, and data structures to facilitate non-equijoins of data. Some such embodiments include a data store to hold metadata describing relationships between database tables. The relationships between database tables may include one or more non-equijoins of tables in the form of one or more table-column pairs of a first table being non-equal to one or more table-column pairs of a second table. In some embodiments, the metadata may be used by a query generator to build query statements including one or more non-equijoin.

Abstract: Techniques for applying segment conditions to measure results are presented. Row and column segment data is acquired from a database according to row and column definitions. A measure calculation is applied against the intersecting row and column segment data. Next, one or more combinations or conditions derived from the row and column definitions are used as a filter to produce filtered results.

Abstract: Tools for defining and using custom analysis modules are presented. A generic graphical user interface (GUI) custom analysis tool is presented to a user. The generic GUI custom analysis tool is adapted to receive selections and inputs from the user that define many-to-many relationships in a data store and that include user-defined measures. The inputs are used to generate an instance of a custom analysis module that is capable of being processed against the data store. The instance of the custom analysis module may be stored, recalled, executed, and/or modified from the generic GUI custom analysis tool.

Abstract: Techniques are presented for reusing business measures within a data store. A measure is associated with a measure type. Each measure is associated with a particular data store schema or schema element and includes metadata for fields and calculations against those fields. Requestors can select existing measures, create new measures, delete existing measures, and/or modify existing measures. A measure, when processed against the data store, produces results from a data store that are associated with the data store schema or the schema element and which conform to the fields and calculations defined within the measure's metadata.

Abstract: Techniques are presented for reusable data query language statements. User-defined parameter variables with parameter types are interspersed in data query language statements to form a rule. The rule may execute as a standalone application or as part of another application or service. When the rule is executed, parameter values for the parameter variables are dynamically acquired and populated into the data query language statements.