Abstract: A method for a component of a gas turbine engine includes obtaining images of the component for a plurality of sequential inspection time periods, at least a portion of the images depicting degradation of the component. A first machine learning model (MLM) includes an input layer, an output layer, and a latent space therebetween. The latent space includes a plurality of clusters of nodes corresponding to respective image features. The method includes, for a plurality of the inspection time periods, utilizing the first MLM to determine which one or more of the clusters of the latent space the image most closely aligns with. The method also includes, for a plurality of the inspection time periods, utilizing a second MLM, which is a different type of MLM than the first MLM, to predict, based on the latent space of the first MLM, a degradation of the component that will occur prior to a subsequent one of the inspection time periods.

Abstract: Systems and methods are provided for correction and harmonization of data from multiple devices, such as scientific instruments. Embodiments of the present disclosure provide systems and methods to automate this process to increase data throughput while standardizing that data despite differences in instrument settings and the challenges of proprietary software. For example, embodiments of the present disclosure include a functioning workflow for acquiring and digesting in very large datasets generated by scientific instruments for the oceanic microbiome proteome which can harmonize data taken from instruments of multiple make, model, and settings and detect flawed data/malfunctioning instruments.

Abstract: Systems and methods are provided for correction and harmonization of data from multiple devices, such as scientific instruments. Embodiments of the present disclosure provide systems and methods to automate this process to increase data throughput while standardizing that data despite differences in instrument settings and the challenges of proprietary software. For example, embodiments of the present disclosure include a functioning workflow for acquiring and digesting in very large datasets generated by scientific instruments for the oceanic microbiome proteome which can harmonize data taken from instruments of multiple make, model, and settings and detect flawed data/malfunctioning instruments.

Abstract: Systems and methods are provided for correction and harmonization of data from multiple devices, such as scientific instruments. Embodiments of the present disclosure provide systems and methods to automate this process to increase data throughput while standardizing that data despite differences in instrument settings and the challenges of proprietary software. For example, embodiments of the present disclosure include a functioning workflow for acquiring and digesting in very large datasets generated by scientific instruments for the oceanic microbiome proteome which can harmonize data taken from instruments of multiple make, model, and settings and detect flawed data/malfunctioning instruments.

Abstract: Systems and methods are provided for correction and harmonization of data from multiple devices, such as scientific instruments. Embodiments of the present disclosure provide systems and methods to automate this process to increase data throughput while standardizing that data despite differences in instrument settings and the challenges of proprietary software. For example, embodiments of the present disclosure include a functioning workflow for acquiring and digesting in very large datasets generated by scientific instruments for the oceanic microbiome proteome which can harmonize data taken from instruments of multiple make, model, and settings and detect flawed data/malfunctioning instruments.

Abstract: A method for a component of a gas turbine engine includes obtaining images of the component for a plurality of sequential inspection time periods, at least a portion of the images depicting degradation of the component. A first machine learning model (MLM) includes an input layer, an output layer, and a latent space therebetween. The latent space includes a plurality of clusters of nodes corresponding to respective image features. The method includes, for a plurality of the inspection time periods, utilizing the first MLM to determine which one or more of the clusters of the latent space the image most closely aligns with. The method also includes, for a plurality of the inspection time periods, utilizing a second MLM, which is a different type of MLM than the first MLM, to predict, based on the latent space of the first MLM, a degradation of the component that will occur prior to a subsequent one of the inspection time periods.

Abstract: This invention provides a wireless transceiver device for retrofit conversion of non-wireless enabled electronic controllers and controlled host devices. This invention allows for the rotating of the wireless transceiver device allowing for the entire device to rotate around the connector axis. This functionality allows for the ability to rotate the wireless transceiver device 360 degrees or to any orientation that maximizes the available space around the host device or around the area of permanent or temporary installations of networks of single or multiple controllers and controlled devices. The inclusion of a stop pin washer plate may be combined with a rotation limiting washer to prevent the rotating assembly from moving freely around the 360 degrees of rotation.

Abstract: Systems and methods of the present invention provide for a user uploading a file and a customized metadata about the file to a file storage system. This information may be forwarded to an application, possibly an API, which may divide the file into a plurality of file chunks if the file is greater than a predetermined file size. One or more tracker servers may check a database to locate optimal file locations for the file or file chunks to be stored within the file storage system. These optimal locations may be returned from the tracker servers to the application/API which may perform an HTTP request to write the file to the file storage system. The file write may be validated and finalized, and the successful write may be displayed to the user on a user interface on a client.

Abstract: Systems and methods of the present invention provide for a user uploading a file and a customized metadata about the file to a file storage system. This information may be forwarded to an application, possibly an API, which may divide the file into a plurality of file chunks if the file is greater than a predetermined file size. One or more tracker servers may check a database to locate optimal file locations for the file or file chunks to be stored within the file storage system. These optimal locations may be returned from the tracker servers to the application/API which may perform an HTTP request to write the file to the file storage system. The file write may be validated and finalized, and the successful write may be displayed to the user on a user interface on a client.

Abstract: Systems and methods of the present invention provide for a user uploading a file and a customized metadata about the file to a file storage system. This information may be forwarded to an application, possibly an API, which may divide the file into a plurality of file chunks if the file is greater than a predetermined file size. One or more tracker servers may check a database to locate optimal file locations for the file or file chunks to be stored within the file storage system. These optimal locations may be returned from the tracker servers to the application/API which may perform an HTTP request to write the file to the file storage system. The file write may be validated and finalized, and the successful write may be displayed to the user on a user interface on a client.

Abstract: Systems and methods of the present invention provide for a user uploading a file and a customized metadata about the file to a file storage system, and reading the same back upon request. This information may be forwarded to an application, possibly an API, which may divide the file into a plurality of file chunks if the file is greater than a predetermined file size. One or more tracker servers may check a database to locate optimal or current file locations for the file or file chunks to be stored within the file storage system. These optimal or current locations may be returned from the tracker servers to the application/API which may perform an HTTP request to write the file to or read the file from the file storage system. The file write may be validated and finalized, and the successful write or read may be displayed to the user on a user interface on a client.

Abstract: Systems and methods of the present invention provide for a user uploading a file and a customized metadata about the file to a file storage system. This information may be forwarded to an application, possibly an API, which may divide the file into a plurality of file chunks if the file is greater than a predetermined file size. One or more tracker servers may check a database to locate optimal file locations for the file or file chunks to be stored within the file storage system. These optimal locations may be returned from the tracker servers to the application/API which may perform an HTTP request to write the file to the file storage system. The file write may be validated and finalized, and the successful write may be displayed to the user on a user interface on a client.

Abstract: Systems and methods provide for hosting one or more server computers comprising a project management software. The project management software may comprise a first story board comprising one or more stories for a first team. The first story board may be controlled by one or more first story board control panels. The project management software may also comprise a second story board comprising one or more stories for a second team. A sub-story may be created using the one or more first story board control panels. In one embodiment, this sub-story may be inserted into a backlog list for the second story board and an alert may be displayed on the second story board requesting the second team to implement the sub-story from the backlog list into the second story board. In another embodiment, the stories on the second story board may be about, but not used by, a second team.

Abstract: Systems and methods provide for hosting one or more server computers comprising a project management software. The project management software may comprise a first story board comprising one or more stories for a first team. The first story board may be controlled by one or more first story board control panels. The project management software may also comprise a second story board comprising one or more stories for a second team. A sub-story may be created using the one or more first story board control panels. In one embodiment, this sub-story may be inserted into a backlog list for the second story board and an alert may be displayed on the second story board requesting the second team to implement the sub-story from the backlog list into the second story board. In another embodiment, the stories on the second story board may be about, but not used by, a second team.

Abstract: Systems and methods provide for hosting one or more server computers comprising a project management software. The project management software may comprise a first story board comprising one or more stories for a first team. The first story board may be controlled by one or more first story board control panels. The project management software may also comprise a second story board comprising one or more stories for a second team. A sub-story may be created using the one or more first story board control panels. In one embodiment, this sub-story may be inserted into a backlog list for the second story board and an alert may be displayed on the second story board requesting the second team to implement the sub-story from the backlog list into the second story board. In another embodiment, the stories on the second story board may be about, but not used by, a second team.

Abstract: Systems and methods of the present invention provide for a user requesting a file or a plurality of file chunks stored in a file storage system, and a customized metadata stored in data storage. One or more tracker servers may determine file locations in the file system, and the location of the customized metadata in the data storage. These locations may be returned to an application, possibly an API, which may determine one or more URLs for the file locations and perform an HTTP request to read the file or file chunks from the locations or URLs in the file system. The file or file chunks, along with the customized metadata, may then be returned and displayed to the user that requested them.

Abstract: Systems and methods of the present invention provide for a user uploading a file and a customized metadata about the file to a file storage system. This information may be forwarded to an application, possibly an API, which may divide the file into a plurality of file chunks if the file is greater than a predetermined file size. One or more tracker servers may check a database to locate optimal file locations for the file or file chunks to be stored within the file storage system. These optimal locations may be returned from the tracker servers to the application/API which may perform an HTTP request to write the file to the file storage system. The file write may be validated and finalized, and the successful write may be displayed to the user on a user interface on a client.

Abstract: Systems and methods of the present invention provide for a user uploading a file and a customized metadata about the file to a file storage system. This information may be forwarded to an application, possibly an API, which may divide the file into a plurality of file chunks if the file is greater than a predetermined file size. One or more tracker servers may check a database to locate optimal file locations for the file or file chunks to be stored within the file storage system. These optimal locations may be returned from the tracker servers to the application/API which may perform an HTTP request to write the file to the file storage system. The file write may be validated and finalized, and the successful write may be displayed to the user on a user interface on a client.

Abstract: Systems and methods of the present invention provide for a user uploading a file and a customized metadata about the file to a file storage system, and reading the same back upon request. This information may be forwarded to an application, possibly an API, which may divide the file into a plurality of file chunks if the file is greater than a predetermined file size. One or more tracker servers may check a database to locate optimal or current file locations for the file or file chunks to be stored within the file storage system. These optimal or current locations may be returned from the tracker servers to the application/API which may perform an HTTP request to write the file to or read the file from the file storage system. The file write may be validated and finalized, and the successful write or read may be displayed to the user on a user interface on a client.