Abstract: An automatic seismic facies identification method based on combination of Self-Attention mechanism and U-shape network architecture, including: obtaining and preprocessing post-stack seismic data to construct a sample training and validation dataset; building an encoder through an overlapped patch merging module with down-sampling function and a self-attention transformer module with global modeling function; building a decoder through a patch expanding module with linear upsampling function, the self-attention transformer module, and a skip connection module with multilayer feature fusion function; building a seismic facies identification model using the encoder, the decoder, and a Hypercolumn module, where the seismic facies identification model includes a Hypercolumns-U-Segformer (HUSeg); and building a hybrid loss function; iteratively training the seismic facies identification model with a training and validation set; and inputting test data into a trained identification model to obtain seismic facies co

Abstract: A development system comprises, in one example, a customization component configured to detect user development inputs to develop elements of a computing system, the elements comprising types modeled in the computing system, a display system configured to generate user interface displays, and a visualization system configured to identify a set of customized elements, a set of non-customized elements, and a customization type for each of the customized elements. The visualization system comprises a display system controller configured to control the display system to generate an integrated view user interface display that visually distinguishes the set of customized elements from the set of non-customized elements and indicates the customization types for the customized elements.

Abstract: A development system comprises, in one example, a customization component configured to detect user development inputs to develop elements of a computing system, the elements comprising types modeled in the computing system, a display system configured to generate user interface displays, and a visualization system configured to identify a set of customized elements, a set of non-customized elements, and a customization type for each of the customized elements. The visualization system comprises a display system controller configured to control the display system to generate an integrated view user interface display that visually distinguishes the set of customized elements from the set of non-customized elements and indicates the customization types for the customized elements.

Abstract: Customization of software source code is enabled by adding the event handlers to be invoked in metadata instead of as coding artifacts. The fact that classes offer delegates that can be assigned handlers is described as part of metadata, in other words, as descriptions of the event itself. By defining eventing in metadata, adding and/or removing handlers for specific events is enabled without programming or modification of the source code.

Abstract: Concepts and technologies are described herein for providing metadata-based eventing supporting operations on data. Application data such as classes and events can be stored in a table and can be associated with and/or described by application metadata. The application metadata also can specify one or more event handlers that reference one or more methods on a class. The event handlers can be invoked via various delegates linked to the one or more application metadata tables. When a create, update, or delete operation on the application data is received, the application metadata can be queried to determine if the application metadata describes event handlers associated with the application data. If event handlers associated with the application data exist, the event handlers can be invoked.

Abstract: Customization of software source code is enabled by adding the event handlers to be invoked in metadata instead of as coding artifacts. The fact that classes offer delegates that can be assigned handlers is described as part of metadata, in other words, as descriptions of the event itself. By defining eventing in metadata, adding and/or removing handlers for specific events is enabled without programming or modification of the source code.

Abstract: Concepts and technologies are described herein for providing metadata-based eventing supporting operations on data. Application data such as classes and events can be stored in a table and can be associated with and/or described by application metadata. The application metadata also can specify one or more event handlers that reference one or more methods on a class. The event handlers can be invoked via various delegates linked to the one or more application metadata tables. When a create, update, or delete operation on the application data is received, the application metadata can be queried to determine if the application metadata describes event handlers associated with the application data. If event handlers associated with the application data exist, the event handlers can be invoked.