Abstract: A method for timing aperture synthesis arrays comprising the steps of: (a) coupling a plurality of independent crystal oscillators, each of the plurality of independent crystal oscillators having a unique output frequency; (b) digitally synchronizing the plurality of independent crystal oscillators in phase; (c) combining the unique output frequencies; and (d) obtaining a stable digital reference signal for timing at least one remote radio device of the aperture synthesis array.

Abstract: An apparatus may comprise a first carrier tube having a first input end and a first output end and a second carrier tube disposed substantially parallel to the first carrier tube and having a second input end and a second output end. A cross tube may be coupled to the first carrier tube and the second carrier tube and may be disposed substantially perpendicularly between the carrier tubes. A plurality of burner holes may be disposed along the first carrier tube, the second carrier tube, and the cross tube. A plurality of flame sensors may be disposed at various locations of the first carrier tube and the second carrier tube. A first igniter assembly may further be coupled to the first carrier tube.

Abstract: Techniques are disclosed for digitizing a framework for clinical development. In one example, A computing device comprising a memory configured to store a regulatory database, and one or more processors may be configured to perform the techniques. The one or more processors may retrieve, from the regulatory database, a template based on a governance process, receive, via a user interface, input from a user, parameterize the template based on the governance process with the user input to create a parameterized template, and store the parameterized template in a database.

Abstract: Techniques are disclosed for digitizing a framework for clinical development. In one example, a computing device comprising a processor and a memory may be configured to perform the techniques. The processor may first define a data model comprising metadata that specifies a data standard representative of requirements for regulatory-compliant exchange of data between entities. The data model may include one or more client objects, where each client object specifying a sequence of a plurality of gates for a process of a clinical research study protocol. Moreover, each gate of the plurality of gates defines one or more conditions for completion of the gate. The processor may express the data model to define the clinical research study protocol. The memory may store the data model.

Abstract: An apparatus may comprise a first carrier tube having a first input end and a first output end and a second carrier tube disposed substantially parallel to the first carrier tube and having a second input end and a second output end. A cross tube may be coupled to the first carrier tube and the second carrier tube and may be disposed substantially perpendicularly between the carrier tubes. A plurality of burner holes may be disposed along the first carrier tube, the second carrier tube, and the cross tube. A plurality of flame sensors may be disposed at various locations of the first carrier tube and the second carrier tube. A first igniter assembly may further be coupled to the first carrier tube.

Abstract: The present method is directed in one embodiment to a non-soluble, substantially white granular salt substitute for dough-based products. In certain embodiments, the dough-based product comprises a filling sealed within a pocket while in other embodiments, the dough-based product is not filled. In certain embodiments, the dough-based product is heated by baking, deep-frying or microwaving. In certain embodiments, the salt substitute of the present invention may be used in place of other large-particulate salts such as kosher salt for use on dough-based products. Certain non-dough-based products such as salted caramel ice cream, confections, as well as products utilizing a reduced-salt blend are also improved using the present invention. In certain embodiments, the salt substitute comprises white tapioca.

Abstract: The present method is directed in one embodiment to a non-soluble, substantially white granular salt substitute for dough-based products. In certain embodiments, the dough-based product comprises a filling sealed within a pocket while in other embodiments, the dough-based product is not filled. In certain embodiments, the dough-based product is heated by baking, deep-frying or microwaving. In certain embodiments, the salt substitute of the present invention may be used in place of other large-particulate salts such as kosher salt for use on dough-based products. Certain non-dough-based products such as salted caramel ice cream, confections, as well as products utilizing a reduced-salt blend are also improved using the present invention. In certain embodiments, the salt substitute comprises white tapioca.

Abstract: The present method is directed in one embodiment to a non-soluble, substantially white granular salt substitute for dough-based products. In certain embodiments, the dough-based product comprises a filling sealed within a pocket while in other embodiments, the dough-based product is not filled. In certain embodiments, the dough-based product is heated by baking, deep-frying or microwaving. In certain embodiments, the salt substitute of the present invention may be used in place of other large-particulate salts such as kosher salt for use on dough-based products. Certain non-dough-based products such as salted caramel ice cream, confections, as well as products utilizing a reduced-salt blend are also improved using the present invention. In certain embodiments, the salt substitute comprises white tapioca.

Abstract: The present method is directed in one embodiment to a non-soluble, substantially white granular salt substitute for dough-based products. In certain embodiments, the dough-based product comprises a filling sealed within a pocket while in other embodiments, the dough-based product is not filled. In certain embodiments, the dough-based product is heated by baking, deep-frying or microwaving. In certain embodiments, the salt substitute of the present invention may be used in place of other large-particulate salts such as kosher salt for use on dough-based products. Certain non-dough-based products such as salted caramel ice cream, confections, as well as products utilizing a reduced-salt blend are also improved using the present invention. In certain embodiments, the salt substitute comprises white tapioca.

Abstract: In general, techniques are described that facilitate the reuse of software assets within an enterprise. A software asset, as used herein, refers to a set of one or more related artifacts that have been created or harvested for the purpose of applying that asset repeatedly in subsequent development environments. A system, for example, is described that includes a repository to store artifacts, and an asset source to generate a software asset based on the artifacts. The system further includes an asset management system to receive the software asset from the asset source and store the software asset within an asset library. The system may further include a model having one or more elements, and an asset retrieval module to selectively retrieve a subset of the software assets from the asset library based on input from a user identifying one or more of the elements.

Abstract: The present method is directed in one embodiment to a non-soluble, substantially white granular salt substitute for dough-based products. In certain embodiments, the dough-based product comprises a filling sealed within a pocket while in other embodiments, the dough-based product is not filled. In certain embodiments, the dough-based product is heated by baking, deep-frying or microwaving. In certain embodiments, the salt substitute of the present invention may be used in place of other large-particulate salts such as kosher salt for use on dough-based products. Certain non-dough-based products such as salted caramel ice cream, confections, as well as products utilizing a reduced-salt blend are also improved using the present invention. In certain embodiments, the salt substitute comprises white tapioca.

Abstract: In general, techniques are described that facilitate the reuse of software assets within an enterprise. A system, for example, is described that includes a repository to store artifacts, and an asset source to generate a software asset based on the artifacts. The system further includes an asset management system to receive the software asset from the asset source and store the software asset within an asset library. The system may further include a model having one or more elements, and an asset retrieval module to selectively retrieve a subset of the software assets from the asset library based on input from a user identifying one or more of the elements. The system may also include a subsystem that allows users to customize asset governance processes and tailor system behavior through an event-driven mechanism.

Abstract: In general, techniques are described that facilitate the reuse of software assets within an enterprise. A software asset, as used herein, refers to a set of one or more related artifacts that have been created or harvested for the purpose of applying that asset repeatedly in subsequent development environments. A system, for example, is described that includes a repository to store artifacts, and an asset source to generate a software asset based on the artifacts. The system further includes an asset management system to receive the software asset from the asset source and store the software asset within an asset library. The system may further include a model having one or more elements, and an asset retrieval module to selectively retrieve a subset of the software assets from the asset library based on input from a user identifying one or more of the elements.

Abstract: In general, techniques are described that facilitate the reuse of software assets within an enterprise. A software asset, as used herein, refers to a set of one or more related artifacts that have been created or harvested for the purpose of applying that asset repeatedly in subsequent development environments. A system, for example, is described that includes a repository to store artifacts, and an asset source to generate a software asset based on the artifacts. The system further includes an asset management system to receive the software asset from the asset source and store the software asset within an asset library. The system may further include a model having one or more elements, and an asset retrieval module to selectively retrieve a subset of the software assets from the asset library based on input from a user identifying one or more of the elements.

Abstract: In general, techniques are described that facilitate the reuse of software assets within an enterprise. A software asset, as used herein, refers to a set of one or more related artifacts that have been created or harvested for the purpose of applying that asset repeatedly in subsequent development environments. A system, for example, is described that includes a repository to store artifacts, and an asset source to generate a software asset based on the artifacts. The system further includes an asset management system to receive the software asset from the asset source and store the software asset within an asset library. The system may further include a model having one or more elements, and an asset retrieval module to selectively retrieve a subset of the software assets from the asset library based on input from a user identifying one or more of the elements.

Abstract: In general, techniques are described that facilitate the reuse of software assets within an enterprise. A software asset, as used herein, refers to a set of one or more related artifacts that have been created or harvested for the purpose of applying that asset repeatedly in subsequent development environments. A system, for example, is described that includes a repository to store artifacts, and an asset source to generate a software asset based on the artifacts. The system further includes an asset management system to receive the software asset from the asset source and store the software asset within an asset library. The system may further include a model having one or more elements, and an asset retrieval module to selectively retrieve a subset of the software assets from the asset library based on input from a user identifying one or more of the elements.

Abstract: In general, techniques are described for dynamically generating schema information for data description languages. The techniques include receiving a schema defining a class of elements that conform to a data description language, and receiving a constraint template that defines requirements for instances of the elements. The techniques further comprise dynamically generating schema information based on the schema and the constraint template, and validating a document in accordance with the schema information.

Abstract: In general, techniques are described that facilitate the reuse of software assets within an enterprise. A software asset, as used herein, refers to a set of one or more related artifacts that have been created or harvested for the purpose of applying that asset repeatedly in subsequent development environments. A system, for example, is described that includes a repository to store artifacts, and an asset source to generate a software asset based on the artifacts. The system further includes an asset management system to receive the software asset from the asset source and store the software asset within an asset library. The system may further include a model having one or more elements, and an asset retrieval module to selectively retrieve a subset of the software assets from the asset library based on input from a user identifying one or more of the elements.

Abstract: In general, techniques are described that facilitate the reuse of software assets within an enterprise. A software asset, as used herein, refers to a set of one or more related artifacts that have been created or harvested for the purpose of applying that asset repeatedly in subsequent development environments. A system, for example, is described that includes a repository to store artifacts, and an asset source to generate a software asset based on the artifacts. The system further includes an asset management system to receive the software asset from the asset source and store the software asset within an asset library. The system may further include a model having one or more elements, and an asset retrieval module to selectively retrieve a subset of the software assets from the asset library based on input from a user identifying one or more of the elements.

Abstract: In general, techniques are described that facilitate the reuse of software assets within an enterprise. A software asset, as used herein, refers to a set of one or more related artifacts that have been created or harvested for the purpose of applying that asset repeatedly in subsequent development environments. A system, for example, is described that includes a repository to store artifacts, and an asset source to generate a software asset based on the artifacts. The system further includes an asset management system to receive the software asset from the asset source and store the software asset within an asset library. The system may further include a model having one or more elements, and an asset retrieval module to selectively retrieve a subset of the software assets from the asset library based on input from a user identifying one or more of the elements.