Abstract: A media application receives an initial image, user input that selects one or more objects in the initial image, and a textual request to generate an output image that modifies the one or more selected objects in the initial image. The media application generates a user-selected mask that includes object pixels corresponding to the one or more selected objects. A diffusion model receives the textual request to generate the output image, a depth map, and the user-selected mask, where the diffusion model is trained to generate output pixels that are not associated with a human subject. The diffusion model outputs the output image that satisfies the textual request.

Abstract: A media application receives an input image that includes a subject. The media application segments the subject from the input image. The media application generates, based on segmenting the subject, a subject mask that includes subject pixels associated with the subject. The media application determines, based on the subject mask, whether a portion of the subject is cut off by one or more borders of the input image. Responsive to the portion of the subject not being cut off, the media application provides the input image and the subject mask as input to an inpainter machine-learning model. The media application generates, with the inpainter machine-learning model, an output image that extends one or more borders of the input image by adding inpainted pixels to the input image.

Abstract: A method for analyzing impact on binaries, software, and hardware of a planned software upgrade for a computer system. The method includes performing a configuration inventory for the computer system with profiles for the computer system of hardware, software including operating system software, middleware, applications, development tools, and third party software, application interfaces, and binaries. A set of upgrade rules, e.g., rules defining hardware and software requirements including interfaces, libraries, dependencies, and more, are accessed and the binary profiles are analyzed based on the upgrade rules to determine safe binaries and at-risk binaries. The at-risk binaries are further divided into subcategories based on risks of incompatibility with the planned software upgrade. The subcategories include failure, high risk, and low risk.

Abstract: A system and method for assessing binary compatibility between software modules permits software end users to register with a system, download software tools for testing binary compatibility between one or more ABIs and binary files resident on the end users' computer system(s). The testing generates a file including the results of the binary compatibility test for each binary file tested. A unique identifier of each binary file, e.g., the MD5 signature of the binary code, may be uploaded with the results of the compatibility test. The results of the compatibility test and the unique identifier may be further analyzed to determine a risk profile that the binary file(s) on the end user's computer system(s) is not binary compatible with a particular ABI. A report may be generated indicating the binary compatibility risk profile of the files resident on the user's computer system.

Abstract: A system and method for assessing binary compatibility between software modules permits software end users to register with a system, download software tools for testing binary compatibility between one or more ABIs and binary files resident on the end users' computer system(s). The testing generates a file including the results of the binary compatibility test for each binary file tested. A unique identifier of each binary file, e.g., the MD5 signature of the binary code, may be uploaded with the results of the compatibility test. The results of the compatibility test and the unique identifier may be further analyzed to determine a risk profile that the binary file(s) on the end user's computer system(s) is not binary compatible with a particular ABI. A report may be generated indicating the binary compatibility risk profile of the files resident on the user's computer system.

Abstract: A method for analyzing impact on binaries, software, and hardware of a planned software upgrade for a computer system. The method includes performing a configuration inventory for the computer system with profiles for the computer system of hardware, software including operating system software, middleware, applications, development tools, and third party software, application interfaces, and binaries. A set of upgrade rules, e.g., rules defining hardware and software requirements including interfaces, libraries, dependencies, and more, are accessed and the binary profiles are analyzed based on the upgrade rules to determine safe binaries and at-risk binaries. The at-risk binaries are further divided into subcategories based on risks of incompatibility with the planned software upgrade. The subcategories include failure, high risk, and low risk.

Abstract: A method for reporting computer system and network asset changes. The method includes receiving from a client node first and second comparison points, such as survey dates or user-entered dates. The method continues with retrieving from memory sets of asset data corresponding to each of the comparison points and then comparing the sets of asset data to identify asset deltas. An asset delta report is transmitted to the client node providing the sets of asset data for the two comparison points and change of status flags or other indications of which assets were determined to have changes at the two comparison points. Viewing parameters and filtering variables, such as particular monitored systems and asset subsets, are received and used to determine which asset data sets to compare and to include in the asset delta report. To reduce storage requirements, asset data is stored when changes occur between asset surveys.

Abstract: A method and associated system for providing customer-directed user administration within a system monitoring environment. The method includes assigning customer users differing privileges for user administration based on an assigned user class. A root administrator class has administration privileges to view gathered data for the entire monitored environment and administer users in the entire environment by adding or modifying users with less administration privileges, such as domain administrators and viewers. Users may be assigned as domain administrators and viewers of one or more domain within the environment. Domain administrators can view system data within the assigned domain and administer users within the domain, including viewers and domain administrators. Viewers can view system data within the assigned domain. Users being assigned to multiple domains filter the reported data by selecting a subset of the domains for monitoring.