Abstract: In example embodiments, techniques are described for using workspace databases to provide workspace resources to customize sessions of applications. File-based workspace databases are maintained in workspace files in a local file system. Cloud-based workspace databases are maintained in a cloud-based blob storage container of a storage account of a cloud storage system. Each cloud-based blob storage container may hold multiple cloud-based workspace databases, including multiple versions of the same database. To use a cloud-based workspace database, a backend module of an application may create an in-memory cloud container object that represents a connection to the cloud-based blob storage container. It may be attached to an in-memory object configured to manage a local cache of blocks of workspace databases. Access to the cloud-based blob storage container may be managed by access tokens provided by a container authority.

Abstract: In example embodiments, techniques are described for using workspace databases to provide workspace resources to customize sessions of applications. To write workspace resources a backend module of an application may obtain a write lock on a cloud-based blob storage container, and ensure a block of a workspace database to be modified is local in a cloud cache. It may execute one or more database commands to modify the block in the cloud cache, and change an identifier of the block in a local copy of a manifest that includes a list of the blocks of the cloud-based blob storage container. It may further upload the modified block and the local copy of the manifest to the cloud-based blob storage container, wherein the uploaded local copy of the manifest replaces the manifest in the cloud-based blob storage container.

Abstract: In example embodiments, techniques are described for using workspace databases to provide workspace resources to customize sessions of applications. File-based workspace databases are maintained in workspace files in a local file system. Cloud-based workspace databases are maintained in a cloud-based blob storage container of a storage account of a cloud storage system. Each cloud-based blob storage container may hold multiple cloud-based workspace databases, including multiple versions of the same database. To use a cloud-based workspace database, a backend module of an application may create an in-memory cloud container object that represents a connection to the cloud-based blob storage container. It may be attached to an in-memory object configured to manage a local cache of blocks of workspace databases. Access to the cloud-based blob storage container may be managed by access tokens provided by a container authority.

Abstract: In example embodiments, techniques are described for using workspace databases to provide workspace resources to customize sessions of applications. To write workspace resources a backend module of an application may obtain a write lock on a cloud-based blob storage container, and ensure a block of a workspace database to be modified is local in a cloud cache. It may execute one or more database commands to modify the block in the cloud cache, and change an identifier of the block in a local copy of a manifest that includes a list of the blocks of the cloud-based blob storage container. It may further upload the modified block and the local copy of the manifest to the cloud-based blob storage container, wherein the uploaded local copy of the manifest replaces the manifest in the cloud-based blob storage container.

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 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 one embodiment, techniques are provided for aligning source infrastructure data to be compatible with a conceptual schema (e.g., BIS) implemented through an underlying database schema (e.g., DgnDb). Data aligned according to the conceptual schema may serve as a “digital twin” of real-world infrastructure usable throughout various phases of an infrastructure project, with physical information serving as a “backbone”, and non-physical information maintained relative thereto, forming a cohesive whole, while avoiding unwanted data redundancies. Source-format-specific bridge software processes may be provided that that know how to read and interpret source data of a respective source format, and express it in terms of the conceptual schema.

Abstract: In one embodiment, techniques are provided for aligning source infrastructure data to be compatible with a conceptual schema (e.g., BIS) implemented through an underlying database schema (e.g., DgnDb). Data aligned according to the conceptual schema may serve as a “digital twin” of real-world infrastructure usable throughout various phases of an infrastructure project, with physical information serving as a “backbone”, and non-physical information maintained relative thereto, forming a cohesive whole, while avoiding unwanted data redundancies. Source-format-specific bridge software processes may be provided that that know how to read and interpret source data of a respective source format, and express it in terms of the conceptual schema.

Abstract: In example embodiments, techniques are provided to implement changeset conflict rebasing when performing conflict-detection and merging in an infrastructure modeling software architecture that uses an optimistic concurrency policy. Changeset conflict rebasing involves adjusting the pre-change values in a local changeset so they match post-change values of a remote version, rather an original base version, or removing changes from the local changeset entirely.

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: A system and method is described for detecting abnormal contacts and misalignment of end effector of a robot arm during robotic arm operation. A contact shock transients sensing unit detects signals on the robot arm and generates alarms, identifies the location of the contact shock transients in the robot arm operation, and controls robot arm operation to prevent further damage to the robot arm and articles handled by the robot arm.

Abstract: The present invention is directed to analytical methods for determining the concentration, and/or stereoisomeric excess, and/or absolute configuration of chiral analytes in a sample.

Abstract: In one embodiment, undo and redo operations of an application are implemented using patchsets or changesets. When changes are made by the application, a transaction is performed against a relational database including one or more changes to reflect the changes made by the application. The one or more changes are tracked to produce a set of tracked changes. In response to detecting the transaction is to be committed, the set of tracked changes is converted to a patchset or changeset. The patchset or changeset is stored to a transaction table and the transaction committed. In response to a request to undo the changes made by the application, the one or more changes of the patchset or changeset are inverted to produce an inverted patchset or changeset, that is then applied. In response to a request to redo the changes made by the application, the patchset or changeset is applied as is.

Abstract: In example embodiments, techniques are provided to implement changeset conflict rebasing when performing conflict-detection and merging in an infrastructure modeling software architecture that uses an optimistic concurrency policy. Changeset conflict rebasing involves adjusting the pre-change values in a local changeset so they match post-change values of a remote version, rather an original base version, or removing changes from the local changeset entirely.

Abstract: In one embodiment, techniques are provided for converting a CAD description maintained in a first storage format (e.g., a file-based storage format) of a source repository to a second storage format (e.g., a relational database-based storage format) of an output repository. The techniques may, generate a single, coherent representation from spatially ambiguous “fragments” by generating an acyclic model graph for each graphical view, and then storing models of the acyclic model graph in the second storage format (e.g., the relational database-based storage format). The techniques may further produce a post-conversion CAD description that preserves human-readable names and information relationships related to levels by examining attachment specific copies of level structures (i.e. levels and attached levels) referenced from attachments, and generating from these categories and subcategories in the second storage format (e.g., the relational database-based storage format).

Abstract: In one embodiment, techniques are provided for aligning source infrastructure data to be compatible with a conceptual schema (e.g., BIS) implemented through an underlying database schema (e.g., DgnDb). Data aligned according to the conceptual schema may serve as a “digital twin” of real-world infrastructure usable throughout various phases of an infrastructure project, with physical information serving as a “backbone”, and non-physical information maintained relative thereto, forming a cohesive whole, while avoiding unwanted data redundancies. Source-format-specific bridge software processes may be provided that that know how to read and interpret source data of a respective source format, and express it in terms of the conceptual schema.

Abstract: In one embodiment, techniques are provided for modeling infrastructure from a plurality of modeling perspectives using an intelligent model hierarchy. A repository model for the infrastructure is generated that serves as a root of the intelligent model hierarchy. The repository model includes a root subject and one or more child subjects. One or more information partitions are generated for each subject, each information partition being associated with a respective modeling perspective. One or more child models are associated with each information partition. The one or more child models each containing one or more infrastructure elements that express the modeling perspective of the information partition with which the child model is associated. The repository model and the one or more child models are maintained together in a repository, and infrastructure elements of a selected model may be displayed on demand in a user interface of a client.

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: The present invention is directed to analytical methods for determining the concentration, and/or stereoisomeric excess, and/or absolute configuration of chiral analytes in a sample.

Abstract: In one embodiment, techniques are provided for converting a CAD description maintained in a first storage format (e.g., a file-based storage format) of a source repository to a second storage format (e.g., a relational database-based storage format) of an output repository. The techniques may, generate a single, coherent representation from spatially ambiguous “fragments” by generating an acyclic model graph for each graphical view, and then storing models of the acyclic model graph in the second storage format (e.g., the relational database-based storage format). The techniques may further produce a post-conversion CAD description that preserves human-readable names and information relationships related to levels by examining attachment specific copies of level structures (i.e. levels and attached levels) referenced from attachments, and generating from these categories and subcategories in the second storage format (e.g., the relational database-based storage format).