Abstract: Testable, redundant pneumatic control assemblies and related systems and methods are described herein. An example pneumatic control assembly described herein includes first, second, and third parallel supply channels between a compressed air supply and valve header, first, second, and third parallel vent channels between a vent and the valve header, and first, second, third, fourth, fifth, and sixth logic valves. The first and sixth logic valves are disposed in the first parallel supply channel and the first parallel vent channel, the second and third logic valves are disposed in the second parallel supply channel and second parallel vent channel, and the fourth and fifth logic valves are disposed in the third parallel supply channel and third parallel vent channel. The pneumatic control assembly also includes a first, second, and third solenoid valves to control certain ones of the logic valves.

Abstract: Testable, redundant pneumatic control assemblies and related systems and methods are described herein. An example pneumatic control assembly described herein includes first, second, and third parallel supply channels between a compressed air supply and valve header, first, second, and third parallel vent channels between a vent and the valve header, and first, second, third, fourth, fifth, and sixth logic valves. The first and sixth logic valves are disposed in the first parallel supply channel and the first parallel vent channel, the second and third logic valves are disposed in the second parallel supply channel and second parallel vent channel, and the fourth and fifth logic valves are disposed in the third parallel supply channel and third parallel vent channel. The pneumatic control assembly also includes a first, second, and third solenoid valves to control certain ones of the logic valves.

Abstract: A distributed database transaction coordination manager's outcome store may be unavailable to resolve in-doubt transactions locally, e.g., after an unclean detach, during an outcomes store restore, or during a logical database restore. To facilitate transactional consistency, AGEs and values based on them are used. Some code avoids reformatting any closed physical portion for reuse based on the segment's most recently received minimum of persisted AGEs. Some code commits any in-doubt transactions that appear on an aggregate list and aborts any not on the aggregate list. Some code writes each segment's transaction commit records to persistent storage until the segment's persisted-AGE is not less than a common-restore-AGE, and some code resolves any in-doubt transactions based on a harvested outcomes list. Outcomes may reside in a log or a persisted transactions table. A restore checkpoint may include harvested outcomes. Segments may reside on cloud nodes and/or in a shared nothing database system.

Abstract: A distributed database transaction coordination manager's outcome store may be unavailable to resolve in-doubt transactions locally, e.g., after an unclean detach, during an outcomes store restore, or during a logical database restore. To facilitate transactional consistency, AGEs and values based on them are used. Some code avoids reformatting any closed physical portion for reuse based on the segment's most recently received minimum of persisted AGEs. Some code commits any in-doubt transactions that appear on an aggregate list and aborts any not on the aggregate list. Some code writes each segment's transaction commit records to persistent storage until the segment's persisted-AGE is not less than a common-restore-AGE, and some code resolves any in-doubt transactions based on a harvested outcomes list. Outcomes may reside in a log or a persisted transactions table. A restore checkpoint may include harvested outcomes. Segments may reside on cloud nodes and/or in a shared nothing database system.

Abstract: The atomicity of a transaction is extended to a filesystem as well as a database, meaning that, when the transaction is complete, all changes within the transaction to both the database and the filesystem will be either committed or not committed. Interactions may be coordinated among a client, a database resource manager, a filesystem resource manager, and a transaction manager.

Abstract: An event based test system having an improved characterization tool for semiconductor device testing. The characterization map provides multi-dimensional views of device performance for debug of the design, and identification of performance weaknesses. The characterization map tool exploits the capabilities of the event based test system. The multi-dimensional views include a checkerboard map such as displaying pins versus time, a shmoo plot showing pass-fail boundary points relative to predetermined parameters, or a margin map showing a pass/fail range for pins corresponding with timing changes in one or more events.