Abstract: An apparatus 100 for conducting chemical reactions in a process fluid is provided, comprising a central shaft 1 with a number of axial-radial rotors 3 mounted thereon, a plurality of stationary vanes 2 disposed upstream the rotor and a mixing space 4 disposed downstream of the rotor, wherein the mixing space is configured to convert mechanical energy imparted to the process fluid by the rotor into internal energy of said process fluid and to establish conditions for an at least one chemical reaction in the process fluid to occur. Related arrangement, method and uses of the apparatus are further provided.

Abstract: An impeller wheel according to an embodiment includes a hub, a plurality of long blades disposed on a circumferential surface of the hub, the plurality of long blades extending from an inlet portion to an outlet portion of fluid and a plurality of short blades each disposed on the circumferential surface of the hub, the plurality of short blades extending from a downstream side of leading edges of the plurality of the long blades to the outlet portion in a flow passage formed between adjacent long blades of the plurality of long blades. In the impeller wheel, an expression ?2s,full<?2s,spl is satisfied, where ?2s,full and ?2s,spl are respectively blade angles on tip side edges of the plurality of long blades and the plurality of short blades at the outlet portion.

Abstract: A blade for a compressor having a pressure surface and a suction surface. The suction surface includes a discontinuity in the chord-wise curvature of an intermediate portion of the suction surface between the blade leading edge and blade trailing edge, and a slot arranged along at least a portion of the blade in a substantially span-wise direction. The slot being disposed at or near the change in curvature, such that when in use lower momentum fluid near the suction surface is aspirated into the slot.

Abstract: A blade (2) for a compressor comprising a pressure surface (6) and a suction surface (4), wherein the suction surface (4) comprises: a discontinuity in the chord-wise curvature of an intermediate portion of the suction surface between the blade leading edge and blade trailing edge; and a slot (20) arranged along at least a portion of the blade (2) in a substantially span-wise direction, the slot (2) being disposed at or near the said change in curvature, such that when in use lower momentum fluid near the suction surface (4) is aspirated into the slot (20).

Abstract: A flow control arrangement is provided for a gas turbine engine in which an inlet slot is positioned prior to a stationary structure such as a stator or pylon in order that air flow is bled or removed from a mainflow. The removed air passes through a passage duct and is re-injected through an outlet nozzle with an askew angle consistent with an angle of rotor blades of a turbine. In such circumstances, distortion in the flow due to the stationary structure is relieved such that there is less instability downstream from that structure.

Abstract: A user mode device driver interface (UMDDI) is disclosed. The UMDDI is preferably implemented in Windows® NT® version 5.0 and similar systems. The UMDDI allows a device driver to execute in user-mode while the graphics engine (GRE) remains in kernel-mode. The UMDDI exists as a layer between the user-mode driver and GRE; from the perspective of GRE, it encapsulates the user-mode driver and makes it appear to be a normal kernel-mode driver. The UMDDI layer handles the kernel-to-user and user-to-kernel transitions, parameter validation, and management of the kernel-mode and user-mode data and objects.

Abstract: A flow control arrangement (30; 50; 70) is described in which an inlet slot 35, 55, 85 is positioned prior to a stationary structure (33; 43; 53; 73; 83) such as a stator or pylon in order that air flow is bled or removed from a main flow 31, 51, 81. The removed air passes through a passage duct 36, 56 and is re-injected through an outlet nozzle 37, 57, 87 with an askew angle consistent with rotor blades 32, 52, 72, 82 of a turbine. In such circumstances, distortion in the flow due to the stationary structure 33, 43, 53, 83 is relieved such that there is less instability downstream from that structure 33, 43, 53, 83.

Abstract: A flow control arrangement (30; 50; 70) is described in which an inlet slot 35, 55, 85 is positioned prior to a stationary structure (33; 43; 53; 73; 83) such as a stator or pylon in order that air flow is bled or removed from a main flow 31, 51, 81. The removed air passes through a passage duct 36, 56 and is re-injected through an outlet nozzle 37, 57, 87 with an askew angle consistent with rotor blades 32, 52, 72, 82 of a turbine. In such circumstances, distortion in the flow due to the stationary structure 33, 43, 53, 83 is relieved such that there is less instability downstream from that structure 33, 43, 53, 83.

Abstract: A user mode device driver interface (UMDDI) is disclosed. The UMDDI is preferably implemented in Windows® NT® version 5.0 and similar systems. The UMDDI allows a device driver to execute in user-mode while the graphics engine (GRE) remains in kernel-mode. The UMDDI exists as a layer between the user-mode driver and GRE; from the perspective of GRE, it encapsulates the user-mode driver and makes it appear to be a normal kernel-mode driver. The UMDDI layer handles the kernel-to-user and user-to-kernel transitions, parameter validation, and management of the kernel-mode and user-mode data and objects.

Abstract: A user mode device driver interface (UMDDI) is disclosed. The UMDDI is preferably implemented in Windows® NT® version 5.0 and similar systems. The UMDDI allows a device driver to execute in user-mode while the graphics engine (GRE) remains in kernel-mode. The UMDDI exists as a layer between the user-mode driver and GRE; from the perspective of GRE, it encapsulates the user-mode driver and makes it appear to be a normal kernel-mode driver. The UMDDI layer handles the kernel-to-user and user-to-kernel transitions, parameter validation, and management of the kernel-mode and user-mode data and objects.

Abstract: A user mode device driver interface (UMDDI) is disclosed. The UMDDI is preferably implemented in Windows® NT® version 5.0 and similar systems. The UMDDI allows a device driver to execute in user-mode while the graphics engine (GRE) remains in kernel-mode. The UMDDI exists as a layer between the user-mode driver and GRE; from the perspective of GRE, it encapsulates the user-mode driver and makes it appear to be a normal kernel-mode driver. The UMDDI layer handles the kernel-to-user and user-to-kernel transitions, parameter validation, and management of the kernel-mode and user-mode data and objects.