Abstract: An article of manufacture for providing a self-installing hammer drill SDS-based grounding rod according to the present invention is disclosed. The grounding rod includes a shaft member having a top end and a lower end, an SDS-style slot about the top end for coupling within a chuck of a hammer drill, a set of flanges extending out from the shaft member about the lower end, and a case-hardened tip coupled to the lower end of the shaft member.

Abstract: The present invention relates to dihydro-cyclopenta-isoquinoline derivatives of formula (I): processes for preparing them, pharmaceutical compositions containing them and their use in treating disorders caused by IgE (such as allergic responses, non-allergic mast cell responses or certain autoimmune responses), and in particular, disorders caused by the interaction of IgE with the Fc?RI receptor.

Abstract: Conducting a feature game based on an active feature state includes displaying a plurality of feature game indicators that indicate respective ones of the current feature states and a feature game to which the respective ones of the current feature states correspond. A defined number of the current feature states to be active for a game instance of a spinning reel game is selected. The display is controlled to visually indicate in connection with the feature game indicators, which of the plurality of feature states were selected to be active feature states for the game instance. An outcome is determined in accordance with the selected symbols for the game instance. Upon a trigger condition for an active feature state being met by the outcome, the feature game is conducted in accordance with the feature state.

Abstract: A gaming device comprises a display, a random number generator, a processor, and a memory storing instructions. When the instructions are executed by the processor, they cause the processor to conduct a base game from which feature games and at least one composite feature game can be triggered, where the composite feature game comprises game play characteristics from a first feature game and a second feature game of the feature games, and the composite feature game comprises a combination of the different game play characteristics. The composite feature game is initiated in response to a composite feature trigger condition being met. The game instances are presented with one or more feature game icon, which are modified in presentation during the game instances in accordance with an associated game play characteristic for a particular instance.

Abstract: In example embodiments, techniques are provided for visualizing a 3D model in an interactive editing workflow. A user modifies one or more elements of a model of the 3D model, by inserting one or more new elements having geometry, changing the geometry of one or more existing elements and/or deleting one or more existing elements having geometry. An updated view of the 3D model is then rendered to reflect the modification to the one or more elements in part by obtaining, for each new element or changed existing element of the model visible in the view, a polygon mesh that represents geometry of the individual element, obtaining a set of tiles that each include a polygon mesh that represent collective geometry of a set of elements intersecting the tile's volume, displaying the polygon mesh for each new element or changed existing element, and displaying the set of tiles while hiding any deleted or changed existing elements therein.

Abstract: In example embodiments, techniques are provided for refining tiles of an HLOD tree representing a model in order to display a view. A frontend module selects a tile represented by a node of the HLOD sub-tree and obtains information describing geometry of the selected tile. It determines that the selected tile requires refinement to support the view of the model based on the information describing geometry of the selected tile. A tile refinement strategy is determined from a plurality of tile refinement strategies. The frontend module applies the determined tile refinement strategy to the selected tile to generate one or more child tiles that have a higher resolution than the selected tile, the one or more child tiles represented by child nodes added to the HLOD sub-tree. The frontend module displays the view of the model at least in part by showing tiles represented by nodes of the HLOD sub-tree.

Abstract: In example embodiments, techniques are provided for visualizing a 3D model in an interactive editing workflow. A user modifies one or more elements of a model of the 3D model, by inserting one or more new elements having geometry, changing the geometry of one or more existing elements and/or deleting one or more existing elements having geometry. An updated view of the 3D model is then rendered to reflect the modification to the one or more elements in part by obtaining, for each new element or changed existing element of the model visible in the view, a polygon mesh that represents geometry of the individual element, obtaining a set of tiles that each include a polygon mesh that represent collective geometry of a set of elements intersecting the tile's volume, displaying the polygon mesh for each new element or changed existing element, and displaying the set of tiles while hiding any deleted or changed existing elements therein.

Abstract: In example embodiments, techniques are provided for visualizing a 3D model in an interactive editing workflow. A user modifies one or more elements of a model of the 3D model, by inserting one or more new elements having geometry, changing the geometry of one or more existing elements and/or deleting one or more existing elements having geometry. An updated view of the 3D model is then rendered to reflect the modification to the one or more elements in part by obtaining, for each new element or changed existing element of the model visible in the view, a polygon mesh that represents geometry of the individual element, obtaining a set of tiles that each include a polygon mesh that represent collective geometry of a set of elements intersecting the tile's volume, displaying the polygon mesh for each new element or changed existing element, and displaying the set of tiles while hiding any deleted or changed existing elements therein.

Abstract: In example embodiments, techniques are provided for refining tiles of an HLOD tree representing a model in order to display a view. A frontend module selects a tile represented by a node of the HLOD sub-tree and obtains information describing geometry of the selected tile. It determines that the selected tile requires refinement to support the view of the model based on the information describing geometry of the selected tile. A tile refinement strategy is determined from a plurality of tile refinement strategies. The frontend module applies the determined tile refinement strategy to the selected tile to generate one or more child tiles that have a higher resolution than the selected tile, the one or more child tiles represented by child nodes added to the HLOD sub-tree. The frontend module displays the view of the model at least in part by showing tiles represented by nodes of the HLOD sub-tree.

Abstract: In example embodiments, techniques are provided for visualizing a 3D model in an interactive editing workflow. A user modifies one or more elements of a model of the 3D model, by inserting one or more new elements having geometry, changing the geometry of one or more existing elements and/or deleting one or more existing elements having geometry. An updated view of the 3D model is then rendered to reflect the modification to the one or more elements in part by obtaining, for each new element or changed existing element of the model visible in the view, a polygon mesh that represents geometry of the individual element, obtaining a set of tiles that each include a polygon mesh that represent collective geometry of a set of elements intersecting the tile's volume, displaying the polygon mesh for each new element or changed existing element, and displaying the set of tiles while hiding any deleted or changed existing elements therein.

Abstract: In example embodiments, techniques are provided for decoupling user access to infrastructure models from proprietary software that maintains and updates the infrastructure models. A backend application may include an infrastructure modeling backend module that, among other functions, handles communication with an infrastructure modeling frontend module of a frontend application that provides user access to the infrastructure model, infrastructure modeling hub services that maintain repositories for the infrastructure model, and an infrastructure modeling native module that creates, performs operations upon, and updates local instances of a database that stores the infrastructure model.

Abstract: In various embodiments, techniques are provided for coordinating the assignment of codes to infrastructure elements in an infrastructure modeling software architecture. A chain of authority is provided from a code authority local to a client to a cloud-based code authority service. Further, a code is structured in three parts, including a code specification part identifying a code specification that indicates what information is encoded into the code and how it is encoded, a code scope part based on boundaries over which the code authority guarantees the code is unique, and a code value part with a unique value.

Abstract: In example embodiments, techniques are provided for converting geometry of an infrastructure model represented as high-level geometric primitives having a given symbology to low-level primitives, and encoding these low-level primitives into tile contents suited for transmission, and ultimately display upon, on a client device. An architectural split between frontend applications and backend applications may allow conversion of the high level primitives to be performed remote from the client devices by backend applications. Backend applications may be executed on robust hardware devices that execute software in a multi-threaded environment on powerful CPUs. By performing CPU-intensive operations on backend applications, frontend applications on client devices may be required to do little more than submit low-level primitives for rendering on their GPU.

Abstract: In example embodiments, techniques are provided for frontend-driven, incremental HLOD sub-tree creation and dynamic generation of tiles. An infrastructure modeling frontend module (e.g., a iModel.js Frontend module) of a frontend application may incrementally create a local HLOD sub-tree, beginning with an initial HLOD sub-tree based on initial metadata provided without tile contents, and refined based on metadata provided with tile contents, from an infrastructure modeling backend module (e.g., a iModel.js Backend module) of a backend application. The local HLOD sub-tree of each infrastructure modeling frontend module may differ based on the individual tiles requested and the tile refinement strategies employed. The infrastructure modeling backend module may not maintain an HLOD tree, and simply generates tiles upon request, serving them and storing them in a tile cache incase they are needed again.

Abstract: In example embodiments, techniques are provided for decoupling user access to infrastructure models from proprietary software that maintains and updates the infrastructure models. A backend application may include an infrastructure modeling backend module that, among other functions, handles communication with an infrastructure modeling frontend module of a frontend application that provides user access to the infrastructure model, infrastructure modeling hub services that maintain repositories for the infrastructure model, and an infrastructure modeling native module that creates, performs operations upon, and updates local instances of a database that stores the infrastructure model.

Abstract: In example embodiments, techniques are provided for frontend-driven, incremental HLOD sub-tree creation and dynamic generation of tiles. An infrastructure modeling frontend module (e.g., a iModel.js Frontend module) of a frontend application may incrementally create a local HLOD sub-tree, beginning with an initial HLOD sub-tree based on initial metadata provided without tile contents, and refined based on metadata provided with tile contents, from an infrastructure modeling backend module (e.g., a iModel.js Backend module) of a backend application. The local HLOD sub-tree of each infrastructure modeling frontend module may differ based on the individual tiles requested and the tile refinement strategies employed. The infrastructure modeling backend module may not maintain an HLOD tree, and simply generates tiles upon request, serving them and storing them in a tile cache incase they are needed again.

Abstract: In example embodiments, techniques are provided for converting geometry of an infrastructure model represented as high-level geometric primitives having a given symbology to low-level primitives, and encoding these low-level primitives into tile contents suited for transmission, and ultimately display upon, on a client device. An architectural split between frontend applications and backend applications may allow conversion of the high level primitives to be performed remote from the client devices by backend applications. Backend applications may be executed on robust hardware devices that execute software in a multi-threaded environment on powerful CPUs. By performing CPU-intensive operations on backend applications, frontend applications on client devices may be required to do little more than submit low-level primitives for rendering on their GPU.

Abstract: In various embodiments, techniques are provided for coordinating the assignment of codes to infrastructure elements in an infrastructure modeling software architecture. A chain of authority is provided from a code authority local to a client to a cloud-based code authority service. Further, a code is structured in three parts, including a code specification part identifying a code specification that indicates what information is encoded into the code and how it is encoded, a code scope part based on boundaries over which the code authority guarantees the code is unique, and a code value part with a unique value.

Abstract: An envelope stuffer has a carrousel with opposed first and second side walls and a plurality of envelope receivers. A pair of opposed abutments are supported inwardly of the first and second carrousel side walls and extend along an arc of the first and second carrousel side walls. An upstream end of at least one abutment of the pair of abutments flare outwardly away from the other abutment of the pair. An envelope flap folder has a plough and a pivoting plate upstream of the plough. The pivoting plate has a first position establishing a first flap feed path which bypasses the plough and a second position establishing a second flap feed path which incorporates the plough. An actuator is also provided for pivoting the plate between the first position and the second position.

Abstract: A smart card handling system is for handling a plurality of smart cards. It includes an infeed mechanism, a discharge mechanism, a rotary drum, an indexing mechanism, a motor and a control system. The rotary drum has a plurality of evenly spaced smart card read modules. The drum is mechanically connected to the infeed mechanism and the discharge mechanism. Each smart card read module is adapted to receive a smart card from the infeed mechanism and is adapted to read information from the smart card received therein. The discharge mechanism is adapted to receive smart card from the smart card read modules. The indexing mechanism is operably connected to the drum. The motor has a drive shaft mechanically connected to the indexing mechanism. The control system receives information from each of the plurality of read modules.