Abstract: A disclosed example non-transitory machine readable storage medium includes instructions to cause programmable circuitry to at least determine, based on output from at least one sensor, (i) a first parameter corresponding to a first position in a casing of a gas turbine engine, the first position at or downstream of a volume at which flows from respective ones of bleed offtakes are combined, and (ii) a second parameter corresponding to a second position in a casing of a gas turbine engine, the second position upstream from the first position, determine a status of at least one of the bleed offtakes or the at least one sensor based on the first and second parameters, and provide or indicate the status in response to the status indicating improper operation of at least one of the bleed offtakes or the at least one sensor.

Abstract: Methods and apparatus to determine engine status with plenum measurements are disclosed. A disclosed example apparatus for use with a gas turbine engine having bleed offtakes includes at least one sensor on or within the gas turbine engine, the at least one sensor to measure at least one parameter corresponding to: a first plenum within a casing of the gas turbine engine, the first plenum positioned at or downstream of a volume at which flows from respective ones of the bleed offtakes are combined, and a second plenum within the casing, the second plenum positioned upstream of the first plenum, and an interface to communicatively couple the at least one sensor to a controller, the controller to determine a status of the bleed offtakes based on the at least one parameter.

Abstract: An apparatus includes a body, a shaft, a stapling head assembly, and an anvil. The body includes a motor, a first user input feature, and a second user input feature. The first user input feature is operable to activate the motor. The shaft extends distally from the body. The stapling head assembly is positioned at a distal end of the shaft. The stapling head assembly includes an anvil coupling feature, at least one annular array of staples, and a staple driver. The second user input feature is operable to drive the anvil coupling feature longitudinally. The staple driver is operable to drive the at least one annular array of staples. The motor is operable to drive the staple driver. The anvil is configured to couple with the anvil coupling feature. The anvil is further configured to deform the staples driven by the staple driver.

Abstract: A safety helmet includes an outer shell configured for surrounding a head of a user, and an infrared reflective layer disposed in an interior of the outer shell. The infrared reflective layer is configured for reflecting at a least a portion of incident infrared radiation transmitted through the outer shell. The infrared reflective layer has infrared reflectivity of at least 40%. The safety helmet further may have an evaporative cooling pad positioned within a cavity defined by the inner surface of the outer shell. A method of manufacturing a safety helmet is also disclosed.

Abstract: Disclosed is an improved motion planner that safely and proactively considers worst-case agent behavior by generating a worst-case homotopy for every nominal homotopy. In some embodiments, a method comprises: generating a first set of maneuvers to be performed by a vehicle in a scenario, the first set of maneuvers based on an expected behavior of at least one agent proximate to the vehicle; generating a second set of maneuvers to be performed by the vehicle, the second set of maneuvers based on worst case behavior of the at least one agent proximate to the vehicle; generating a set of candidate trajectories based on the first set of maneuvers and the second set of maneuvers; selecting a trajectory from the set of candidate trajectories; and generating, with the at least one processor, at least one control signal to operate the vehicle based on the selected trajectory.

Abstract: Systems and methods are described for modifying input and output (I/O) to an object storage service by implementing one or more owner-specified functions to I/O requests. A function can implement a data manipulation, such as filtering out sensitive data before reading or writing the data. The functions can be applied prior to implementing a request method (e.g., GET or PUT) specified within the I/O request, such that the data to which the method is applied may not match the object specified within the request. For example, a user may request to obtain (e.g., GET) a data set. The data set may be passed to a function that filters sensitive data to the data set, and the GET request method may then be applied to the output of the function. In this manner, owners of objects on an object storage service are provided with greater control of objects stored or retrieved from the service.

Abstract: Systems and methods are described for modifying input and output (I/O) to an object storage service by implementing any combination of and any number of owner-specified functions and native functions. A function can implement a data manipulation. The functions can be applied prior to implementing a request method (e.g., GET, PUT, LIST, etc.) specified within the I/O request, such that the data to which the method is applied may not match the object specified within the request. For example, a user may request to obtain a data set. The data set may be passed to a native function that filters sensitive data to the data set, the output of the native function may be passed to an owner-specified function that redacts data from the filtered data set, and the request method may then be applied to the output of the owner-specified function.

Abstract: Systems and methods are described for modifying input and output (I/O) to an object storage service by implementing one or more owner-specified functions to I/O requests. A function can implement a data manipulation, such as filtering out sensitive data before reading or writing the data. The functions can be applied prior to implementing a request method (e.g., GET or PUT) specified within the I/O request, such that the data to which the method is applied my not match the object specified within the request. For example, a user may request to obtain (e.g., GET) a data set. The data set may be passed to a function that filters sensitive data to the data set, and the GET request method may then be applied to the output of the function.

Abstract: Systems and methods are described for modifying input and output (I/O) to an object storage service by implementing one or more owner-specified functions to I/O requests. Such functions can include data access control functions, data manipulation functions, and the like. The owner of an object collection maintained by the object storage service can specify code execution environment rules that can give privileges to the execution of such functions such as by allowing the functions to access external services or the requesting user's private resources. In this manner, owners of the object collection are provided with greater control over how the object collection is accessed.

Abstract: Systems and methods are described for modifying input and output (I/O) to an object storage service by implementing one or more owner-specified functions to I/O requests. A function can implement a data manipulation, such as filtering out sensitive data before reading or writing the data. The functions can be applied prior to implementing a request method (e.g., GET or PUT) specified within the I/O request, such that the data to which the method is applied may not match the object specified within the request. For example, a user may request to obtain (e.g., GET) a data set. The data set may be passed to a function that filters sensitive data to the data set, and the GET request method may then be applied to the output of the function. In this manner, owners of objects on an object storage service are provided with greater control of objects stored or retrieved from the service.

Abstract: Systems and methods are described for modifying input and output (I/O) to an object storage service by implementing one or more owner-specified functions to I/O requests. Different data manipulation functions can be placed in different I/O paths depending on the request method or user access level. For example, a user having full access may be returned the unaltered version of the object, whereas a user having modified or reduced access may be returned a modified or redacted version of the object. In this manner, owners of the object collection are provided with greater control over how the object collection is accessed.

Abstract: Systems and methods are described for providing input data to and reading output data from one or more owner-specified functions. A function can implement a data manipulation, such as filtering out sensitive data before reading or writing the data. Input data can be provided to the function as an entire object, a stream of objects, or on-demand based on data or portions thereof that the function attempts to access. The function can provide output data as a single instance of output data or a stream of output data regardless of the manner in which input data is provided to the function. The input data can be stored in a staging area that is accessible to the function via a local file system. Similarly, the function can store the output data in a staging area that is accessible to the function via a local file system.

Abstract: Systems and methods are described for modifying input and output (I/O) to an object storage service by implementing one or more owner-specified functions to I/O requests. A function can implement a data manipulation, such as filtering out sensitive data before reading or writing the data. The functions can be applied prior to implementing a request method (e.g., GET or PUT) specified within the I/O request, such that the data to which the method is applied my not match the object specified within the request. For example, a user may request to obtain (e.g., GET) a data set. The data set may be passed to a function that filters sensitive data to the data set, and the GET request method may then be applied to the output of the function. In this manner, owners of objects on an object storage service are provided with greater control of objects stored or retrieved from the service.

Abstract: Systems and methods are described for modifying input and output (I/O) to an object storage service by implementing one or more owner-specified functions to I/O requests. A function can implement a data manipulation, such as filtering out sensitive data before reading or writing the data. The functions can be applied prior to implementing a request method (e.g., GET or PUT) specified within the I/O request, such that the data to which the method is applied my not match the object specified within the request. For example, a user may request to obtain (e.g., GET) a data set. The data set may be passed to a function that filters sensitive data to the data set, and the GET request method may then be applied to the output of the function. In this manner, owners of objects on an object storage service are provided with greater control of objects stored or retrieved from the service.

Abstract: Systems and methods are described for modifying input and output (I/O) to an object storage service by implementing one or more owner-specified functions to I/O requests. A function can implement a data manipulation, such as filtering out sensitive data before reading or writing the data. The functions can be applied prior to implementing a request method (e.g., GET or PUT) specified within the I/O request, such that the data to which the method is applied my not match the object specified within the request. For example, a user may request to obtain (e.g., GET) a data set. The data set may be passed to a function that filters sensitive data to the data set, and the GET request method may then be applied to the output of the function. In this manner, owners of objects on an object storage service are provided with greater control of objects stored or retrieved from the service.

Abstract: Systems and methods are provided for utilizing rules for placement of objects in storage in a manner that improves retrieval times relative to a default ordering utilized by an object storage system. For example, a request to store an object in a persistent storage of a data storage system may be received, metadata associated with the request may then be parsed to identify a signal for placement of the object within the persistent storage, and a rule may be identified for placement of objects associated with that signal, such as by indicating a desired grouping or ordering of objects associated with the signal. A particular storage location for the object may then be determined within the persistent storage based at least in part on the signal, the rule, and previously determined storage locations of one or more other data objects associated with the signal.

Abstract: Systems and methods are described for modifying input and output (I/O) to an object storage service by implementing one or more owner-specified functions to I/O requests. A function can implement a data manipulation, such as filtering out sensitive data before reading or writing the data. The functions can be applied prior to implementing a request method (e.g., GET or PUT) specified within the I/O request, such that the data to which the method is applied my not match the object specified within the request. For example, a user may request to obtain (e.g., GET) a data set. The data set may be passed to a function that filters sensitive data to the data set, and the GET request method may then be applied to the output of the function. In this manner, owners of objects on an object storage service are provided with greater control of objects stored or retrieved from the service.

Abstract: Systems and methods are described for modifying input and output (I/O) to an object storage service by implementing one or more owner-specified functions to I/O requests. A function can implement a data manipulation, such as filtering out sensitive data before reading or writing the data. The functions can be applied prior to implementing a request method (e.g., GET or PUT) specified within the I/O request, such that the data to which the method is applied my not match the object specified within the request. For example, a user may request to obtain (e.g., GET) a data set. The data set may be passed to a function that filters sensitive data to the data set, and the GET request method may then be applied to the output of the function. In this manner, owners of objects on an object storage service are provided with greater control of objects stored or retrieved from the service.

Abstract: Systems and methods are described for modifying input and output (I/O) to an object storage service by implementing one or more owner-specified functions to I/O requests. A function can implement a data manipulation, such as filtering out sensitive data before reading or writing the data. The functions can be applied prior to implementing a request method (e.g., GET or PUT) specified within the I/O request, such that the data to which the method is applied my not match the object specified within the request. For example, a user may request to obtain (e.g., GET) a data set. The data set may be passed to a function that filters sensitive data to the data set, and the GET request method may then be applied to the output of the function. In this manner, owners of objects on an object storage service are provided with greater control of objects stored or retrieved from the service.

Abstract: Systems and methods are described for modifying input and output (I/O) to an object storage service by implementing one or more owner-specified functions to I/O requests. A function can implement a data manipulation, such as filtering out sensitive data before reading or writing the data. The functions can be applied prior to implementing a request method (e.g., GET or PUT) specified within the I/O request, such that the data to which the method is applied my not match the object specified within the request. For example, a user may request to obtain (e.g., GET) a data set. The data set may be passed to a function that filters sensitive data to the data set, and the GET request method may then be applied to the output of the function. In this manner, owners of objects on an object storage service are provided with greater control of objects stored or retrieved from the service.