Abstract: A graft system may be provided. The graft system may include a graft, a hemostasis valve operably coupled to a proximal end of the graft, and a clamp disposed around the proximal end of the graft and configured to hold the hemostasis valve in place relative to the graft. The graft may include a woven or knitted fabric. The clamp may be removably, or permanently, attached to the graft. The hemostasis valve may include a slit membrane disposed within a housing. The hemostasis valve may include an introducer sheath coupled to the housing. The housing may include two portions coupled together along two axial seams, each axial seam extending from a proximal end to a distal end of the hemostasis valve. A grommet may be coupled to an end of the graft.

Abstract: A cooking system positionable on a support surface includes a housing having an internal cooking compartment and an opening formed in the housing for accessing said internal cooking compartment. At least one heating element is provided for heating said internal cooking compartment. The heating element is operable to heat the internal cooking compartment while the opening is at least partially exposed to an ambient environment to allow fluid transfer between the ambient environment and the internal cooking compartment. An output from said at least one heating element is variable across said internal cooking compartment during operation of the system.

Abstract: Mechanisms for sharing user-provided information from an original equipment manufacturer (OEM) application and a vendor application are provided, the mechanisms including: receiving the user-provided information at the OEM application; determining a system identifier of a system on which the OEM application is executing at the OEM application using a hardware processor; providing the user-provided information and the system identifier to a vendor cloud server from the OEM application; determining the system identifier at vendor application; providing the system identifier from the vendor application to the vendor cloud server; receiving the user-provided information at the vendor application from the vendor cloud server in response to providing the system identifier to the vendor cloud server; and using the user-provided information to configure the vendor application.

Abstract: Propeller control systems and methods for controlling the pitch of a plurality of propeller blades of a variable pitch propeller assembly operatively coupled with an engine is provided. In one exemplary aspect, the propeller control system includes features for combining overspeed and feathering protective functions in a protective control valve communicatively coupled with a controller. In such an event the controller controls the protective control valve to selectively allow a controlled amount of hydraulic fluid to flow to or from a pitch actuation assembly such that the pitch of the propeller blades can be adjusted based at least in part on the condition of the engine.

Abstract: This specification describes systems for the treatment and reuse of grey water and related processes. An exemplary system collects grey water from baths and showers and treats it for use in toilet flushing. Influent bathing water passes through a prefilter to remove larger particles and flows into a grey water collection tank. Collected grey water is filtered through a membrane designed to remove suspended solids. Membrane permeate passes through a sorbent media to remove soluble organics and then flows into a permeate tank. A chemical agent is used to disinfect water in one or more parts of the system and optionally to clean the membranes. A control system manages the operation of system. The system operates in a generally daily cycle with permeation dispersed over a material time, for example 4 or 8 hours or more.

Abstract: A watercraft is provided that includes a support platform having a bottom surface. The watercraft includes a hydrofoil disposed on a strut extending from the bottom surface of the support platform. The watercraft includes a propulsion system coupled to the bottom surface of the board such that a thrust generated by the propulsion system moves the board through a body of water. The watercraft includes a position sensor, a speed sensor, and an altitude controller. The position sensor is configured to output position data of the watercraft relative to a surface of water. The speed sensor is configured to output speed data of the watercraft. The altitude controller is configured to adjust the thrust generated by the propulsion system based at least in part on a ride height derived from the position data and a speed derived from the speed data to achieve a target ride height.

Abstract: Propeller control systems and methods for controlling the pitch of a plurality of propeller blades of a variable pitch propeller assembly operatively coupled with an engine is provided. In one exemplary aspect, the propeller control system includes features for combining overspeed and feathering protective functions in a protective control valve communicatively coupled with a controller. In such an event the controller controls the protective control valve to selectively allow a controlled amount of hydraulic fluid to flow to or from a pitch actuation assembly such that the pitch of the propeller blades can be adjusted based at least in part on the condition of the engine.

Abstract: Mechanisms for sharing user-provided information from an original equipment manufacturer (OEM) application and a vendor application are provided, the mechanisms including: receiving the user-provided information at the OEM application; determining a system identifier of a system on which the OEM application is executing at the OEM application using a hardware processor; providing the user-provided information and the system identifier to a vendor cloud server from the OEM application; determining the system identifier at vendor application; providing the system identifier from the vendor application to the vendor cloud server; receiving the user-provided information at the vendor application from the vendor cloud server in response to providing the system identifier to the vendor cloud server; and using the user-provided information to configure the vendor application.

Abstract: Techniques for recommending runbook operations during a runbook generation process are disclosed. A system recommends operations for including in the runbook based on attributes of a detected event. The system presents event attributes associated with the detected event to a user in a runbook generation interface. When the user selects an event attribute, the system presents a set of candidate runbook operations associated with the event attribute. Based on user selections of runbook operations to include in a runbook, the system generates and stores a template of the runbook in which the attribute values associated with the detected event are omitted. Upon execution of the runbook at a future time, the system, or a user, may populate the event attributes in the runbook with values that correspond to the future event of the same event type.

Abstract: Techniques for recommending runbook operations during a runbook generation process are disclosed. The system recommends operations for including in the runbook based on user activity. Generating operations of a runbook based on user activity generates a runbook that captures a user's behavior. The recommended operations may be different than any operations performed by the user. The recommended operations may be based in part on data sets accessed by the user frequently, periodically, or continuously.

Abstract: Techniques for generating supplemental information based on runbook operation results are disclosed. A system generates and displays supplemental information for a runbook execution interface based on one of a system component associated with an executable operation of a runbook, and a set of runbook operation results corresponding to the executable operation. The system receives a user input to execute an operation defined by a runbook presented to remediate an event. The system generates supplemental information for the runbook execution interface based on the results of the operation executed by the user. The system identifies characteristics associated with the runbook operation results and identifies sources for additional information. Source may include performance data from the same component over a different period of time, performance data of a similar component, and performance data of topologically-connected components.

Abstract: Theater designs including social media, and theater entrances configured to draw patrons into a main area of the theater including an entrance having a curved wall and curved walkway having a horizon drop-off for display of content related to a motion picture or other feature to be shown in the theater. The content may be interactive or otherwise linked to patrons passing a hallway including the curved wall. Spatialized sound corresponding to the video “moves” with objects in the video and with patrons as they traverse walkway.

Abstract: This specification describes an intake filter for use, for example, in a system that collects greywater from baths or showers for re-use in toilet flushing. The intake filter provides essentially dead-end filtration. An influent by-pass may be provided, but the filter is cleaned as required to reduce use of the by-pass. Cleaning is performed when permeability of the filter declines. An upstream sensor may be used to detect the permeability of the filter. In one cleaning method, flowing water, optionally with air, is used to backwash the filter. The impulse of the flowing water also moves one or more valves to direct backwash water to a sanitary drain. For example, pumped effluent may impinge against a first flap to close an effluent drain, the first flap being mechanically linked to open a flap covering the sanitary drain.

Abstract: A disclosed system, method and computer readable storage medium includes mechanism for controlling cascade price movements in an electronic trading system. Price limits control the prices at which traders can place orders. An upper price limit prevents traders from placing orders above the upper limit and a lower price limit prevents traders from placing orders below the lower limit. The gap between the upper limit and the indicative marked price as well as the gap between lower limit and the indicative market price is controlled so as to cause a breaking effect on very rapidly changing market price.

Abstract: A disclosed system, method and computer readable storage medium includes mechanism for controlling cascade price movements in an electronic trading system. Price limits control the prices at which traders can place orders. An upper price limit prevents traders from placing orders above the upper limit and a lower price limit prevents traders from placing orders below the lower limit. The gap between the upper limit and the indicative marked price as well as the gap between lower limit and the indicative market price is controlled so as to cause a breaking effect on very rapidly changing market price.

Abstract: Techniques for selecting a runbook to recommend for remediating a detected event are disclosed. When a system detects an event, the system obtains metadata associated with the event. The metadata provides information about the event and a system topology of the system in which the event occurred. The system generates a recommendation for a runbook to remediate the event based on one or both of characteristics of the event and characteristics of the topology in which the event occurred. The system compares a system topology to system topologies associated with previously-executed runbooks. The system recommends one of the previously-executed runbooks to remediate a detected event based on determining that the topology associated with the previously-executed runbook is similar to the topology of the system in which the event occurred.

Abstract: Techniques for selecting a runbook to as a recommendation to diagnose or remediate an event are disclosed. A system identifies an event, such as an anomaly in monitored metrics values. The system identifies runbooks associated with the event. The system analyzes the runbooks to determine which runbooks to recommend for remediating the event. The analysis includes previewing results of operations associated with steps of the runbooks to identify interesting results. The system performs a runbook operation prior to recommending the runbook for diagnosing or remediating the event. Based on the results of the operations, the system determines a relevance of a runbook to the diagnosis or remediation of the detected event. The system recommends a runbook for diagnosing or remediating the event based on the relevance of the set of results to the diagnosis or remediation of the event.

Abstract: Techniques for recommending runbook operations during a runbook generation process are disclosed. The system recommends operations for including in the runbook based on user activity. Generating operations of a runbook based on user activity generates a runbook that captures a user's behavior. The recommended operations may be different than any operations performed by the user. The recommended operations may be based in part on data sets accessed by the user frequently, periodically, or continuously.

Abstract: Techniques for generating supplemental information based on runbook operation results are disclosed. A system generates and displays supplemental information for a runbook execution interface based on one of a system component associated with an executable operation of a runbook, and a set of runbook operation results corresponding to the executable operation. The system receives a user input to execute an operation defined by a runbook presented to remediate an event. The system generates supplemental information for the runbook execution interface based on the results of the operation executed by the user. The system identifies characteristics associated with the runbook operation results and identifies sources for additional information. Source may include performance data from the same component over a different period of time, performance data of a similar component, and performance data of topologically-connected components.

Abstract: Techniques for collaboratively executing runbook sessions are disclosed. A system provides for collaborative completion of runbook operations by delegating runbook operations or by transferring ownership of a runbook from one user to another. A system identifies a first set of runbook operations capable of being completed by a first user. The system identifies a second set of runbook operations that are not capable of being completed by the first user. The system identifies a second user capable of completing the second set of runbook operations. Upon completion of the first set of runbook operations by the first user, the system determines whether to delegate the second set of runbook operations to the second user or to transfer ownership of the runbook session to the second user. The system determines that the runbook session is completed based on the combined results collaboratively generated by the initial user and the alternate user.