Abstract: A computer-implemented method for task management can include managing performance of a task on a message by a plurality of circuits. In some aspects, the task can comprise a sequence of processings to be performed on the message and each circuit of the plurality of circuits performing a processing of the sequence of processings. In some aspects, the method can include routing, based on the sequence, a first information regarding the task to a first circuit of the plurality of circuits to perform a first processing of the sequence of processings on the message; receiving, from the first circuit, an output of the first processing; and routing, based on the sequence of processings identified for the task, a second information regarding the task to a second circuit of the plurality of circuits to perform a second processing that follows the first processing in the sequence of processings.

Abstract: System and method are provided for automation of placing and transporting of parcels or packages in containers. Aspects of disclosure provide automation for filling and manipulation of containers, and closure of filled containers, in systems where materials, products, packages, and other items may require containerization. Other aspects of disclosure provide automation for transport of one or more empty and/or filled containers from/to various staging areas of such systems.

Abstract: A network interface device has an interface configured to interface with a network. The interface is configured to at least one of receive data from the network and put data onto the network. The network interface device has an application specific integrated device with a plurality of data processing pipelines to process at least one of data which has been received from the network and data which is to be put onto said network and an FPGA arranged in a path parallel to the data processing pipelines.

Abstract: The present invention relates to the synthesis of 3-[(1S,2S)-1-[5-[(4S)-2,2-dimethyloxan-4-yl]-2-[(4S)-2-(4-fluoro-3,5-dimethylphenyl)-3-[3-(4-fluoro-1-methylindazol-5-yl)-2-oxoimidazol-1-yl]-4-methyl-6,7-dihydro-4H-pyrazolo [4,3-c] pyridine-5-carbonyl] indol-1-yl]-2-methylcyclopropyl]-4H-1,2,4-oxadiazol-5-one, or a salt thereof, and related synthetic intermediate compounds.

Abstract: A two-stroke engine comprises a first oiling system and a second oiling system. The first oiling system includes a low-pressure pump that distributes oil from a first oil tank to the two-stroke engine. The second oiling system includes a pump mechanically coupled to a crankshaft of the two-stroke engine, wherein the pump distributes oil from a second oil tank to an accessory at a pressure greater than the first oil pressure, wherein oil distributed to the accessory is returned to the second oil tank.

Abstract: Disclosed are techniques for processing uncommitted writes in a store queue. In an aspect, an apparatus comprises a processor and a dual store queue having an in-order queue (IOQ) for storing uncommitted writes and an uncommitted data gather queue (UGQ) for gathering uncommitted data. The dual store queue receives, from a processor, a first write instruction for writing first data to at least a portion of memory at a first memory address, allocates an IOQ entry corresponding to the first write instruction, and allocates or updates a UGQ entry associated with the first memory address to contain the first data.

Abstract: A two-stroke engine comprises a first oiling system and a second oiling system. The first oiling system includes a low-pressure pump that distributes oil from a first oil tank to the two-stroke engine. The second oiling system includes a pump mechanically coupled to a crankshaft of the two-stroke engine, wherein the pump distributes oil from a second oil tank to an accessory at a pressure greater than the first oil pressure, wherein oil distributed to the accessory is returned to the second oil tank.

Abstract: Disclosed are techniques for processing uncommitted writes in a store queue. In an aspect, an apparatus comprises a processor and a dual store queue having an in-order queue (IOQ) for storing uncommitted writes and an uncommitted data gather queue (UGQ) for gathering uncommitted data. The dual store queue receives, from a processor, a first write instruction for writing first data to at least a portion of memory at a first memory address, allocates an IOQ entry corresponding to the first write instruction, and allocates or updates a UGQ entry associated with the first memory address to contain the first data.

Abstract: A two-stroke engine comprises a first oiling system and a second oiling system. The first oiling system includes a low-pressure pump that distributes oil from a first oil tank to the two-stroke engine. The second oiling system includes a pump mechanically coupled to a crankshaft of the two-stroke engine, wherein the pump distributes oil from a second oil tank to an accessory at a pressure greater than the first oil pressure, wherein oil distributed to the accessory is returned to the second oil tank.

Abstract: A protective cover (800) for a medical device includes a body (700) and a cap (100) that is selectively attachable to the body. The cap 100 includes an annulus 101 and a rounded vault (102) spanning an interior portion (118) of the annulus. The rounded vault defines a convex exterior (301). A plurality of partial arch trusses (103,104,105,106,107,108,109) extends from the annulus along the convex exterior toward an apex (601) of the convex exterior. Distal ends (613,614,615,616,617,618,619) of the plurality of partial arch trusses define an interstice (611) at the apex. The partial arch trusses provide longitudinal deflection of impact forces to protect the medical device.

Abstract: A two-stroke engine comprises a first oiling system and a second oiling system. The first oiling system includes a low-pressure pump that distributes oil from a first oil tank to the two-stroke engine. The second oiling system includes a pump mechanically coupled to a crankshaft of the two-stroke engine, wherein the pump distributes oil from a second oil tank to an accessory at a pressure greater than the first oil pressure, wherein oil distributed to the accessory is returned to the second oil tank.

Abstract: A network interface device comprises a programmable interface configured to provide a device interface with at least one bus between the network interface device and a host device. The programmable interface is programmable to support a plurality of different types of a device interface.

Abstract: A network interface device, said network interface device has a data transmission path configured to receive data for transmission. The data for transmission is to be sent over a network by the network interface device. A monitor is configured to monitor the data transmission path to determine if an underrun condition is associated with the data transmission path. If so, an indication is included in the transmitted data packet.

Abstract: A canister lid (101) for a canister (102) includes an annular perimeter (103) surrounding an interior portion (104). Rather than completely surrounding the interior portion, the annular perimeter is instead interrupted by a suction conduit (112) defined by a suction conduit (112) separating a first lobe (117) and a second lobe (118). The suction conduit (112) intersects the annular perimeter such that the first lobe is disposed interior of the annular perimeter while the second lobe is disposed exterior to the annular perimeter. The canister lid can further include one or more ports (110,111) extending from the interior portion. A canister (102) can include a valve (401) and can optionally be coupled to a hub mount vacuum source (1200) or a hub mount stand (1800).

Abstract: Roughly described: a network interface device has an interface. The interface is coupled to first network interface device circuitry, host interface circuitry and host offload circuitry. The host interface circuitry is configured to interface to a host device and has a scheduler configured to schedule providing and/or receiving of data to/from the host device. The interface is configured to allow at least one of: data to be provided to said host interface circuitry from at least one of said first network device interface circuitry and said host offload circuitry; and data to be provided from said host interface circuitry to at least one of said first network interface device circuitry and said host offload circuitry.

Abstract: A network interface device having an FPGA for providing an FPGA application. A first interface between a host computing device and the FPGA application is provided, allowing the FPGA application to make use of data-path operations provided by a transport engine on the network interface device, as well as communicate with the host. The FPGA application sends and receives data with the host via a memory that is memory mapped to a shared memory location in the host computing device, whilst the transport engine sends and receives data packets with the host via a second memory. A second interface is provided to interface the FPGA application and transport engine with the network, wherein the second interface is configured to back-pressure the transport engine.

Abstract: A vacuum-based end effector for engaging parcels includes a base plate, one or more vacuum cups of a first type, and one or more vacuum cups of a second type. Each vacuum cup of the vacuum-based end effector is configured to be placed in fluid communication with a vacuum source to provide the vacuum cup with a suction force which can be used to engage and grasp parcels. Each vacuum cup includes a bellows defining a pathway for a flow of air and a lip connected to the bellows. Each lip of the one or more vacuum cups of the first type comprises a foam lip, and each lip of the one or more vacuum cups of the second type comprises an elastomeric lip. The vacuum-based end effector can be combined with a robot to provide an improved system for engaging parcels.

Abstract: A rule engine receives data flows. The data flows are between a network and an application. The rule engine determines data flow information and in dependence on the information performs an action with respect to said flow. A controller provides control information to the rule engine to define one or more actions. The communications between said rule engine and said controller are secure.