Patent classifications
G06F11/0721
Systems and Methods for Predicting Power Converter Health
A method for predicting power converter health is provided. The method comprises receiving a plurality of parameter measurements associated with a power converter system comprising a power converter. The plurality of parameter measurements comprises a first set of system measurements and a second set of failure precursor measurements. The method further comprises inputting the first set of system measurements into a first machine learning algorithm to generate expected failure precursor measurement information and inputting the expected failure precursor measurement information and the second set of failure precursor measurements into a second machine learning algorithm to generate component failure prediction information. The method also comprises performing one or more actions based on the generated component failure prediction information.
INTELLIGENT LOG ANALYSIS AND RETENTION FOR MICROSERVICES APPLICATIONS
Embodiments for an intelligent log analysis and retention for microservices applications. Such log analysis is helpful in troubleshooting failure conditions that may occur intermittently or repeatedly within a microservices environment. Executed operations by microservices, applications, or components generate logs, and these logs are classified based on certain parameters. A default log retention period defines how long the logs are stored in the system, and a log analytical engine determines and assigns weights constituting additional retention time to keep logs for failed operations. These logs can then be analyzed to determine causes of the failure, and build failure models to predict future failure conditions. Logs for successful operations can be timely deleted to save storage space.
Automated application programming interface (API) route testing system
Various aspects of the disclosure relate to automated route testing for application programming interfaces (APIs). An API route testing systems is configured to use classes and methods to identify API routes called by APIs and routes made available by application services. The class methods are customizable based on a programming language, testing or development framework, and the application type. Instances of classes are provided to detect routes similarly to API functions incorporated into a client application. Classes also detect routes in use by client services. A separate class is provided to compare the lists of API called routes and routes used by client services to return a listing of duplicate routes, unused API routes and client calls to invalid API routes (e.g., missing routes). For found duplicate routes and missing routes, the API route testing system generates an indication of the error and lists routes causing the error.
Computer, Diagnosis System, and Generation Method
Provided is a computer capable of reducing a diagnosis load. For each predetermined diagnosis target node among a plurality of nodes in a neural network, a determination processing unit calculates an expected output value expected as a calculation result of a node calculation process corresponding to the predetermined diagnosis target node, which is obtained when the node calculation process is executed using a predetermined input value. For each diagnosis target node, a generation processing unit generates as a diagnosis program a program for comparing the calculation result of the node calculation process corresponding to the diagnosis target node, which is obtained when the node calculation process is executed by an NN calculation processor using the input value, with the expected output value.
Shift left model execution in software delivery
Disclosed herein a system, method, and computer program product for providing proactive guidance to users in order to execute a shift left model in software delivery. As disclosed, a processor may receive an issue resolution request. The processor may further access an issue resolution request repository where the issue resolution request repository may include details related to prior issue resolution requests. The processor may subsequently classify the issue resolution request based on the details related to the prior issue resolution requests. Accordingly, the processor may identify a root cause for the issue resolution request.
ROLL BACK OF DATA DELTA UPDATES
Disclosed embodiments relate to adjusting vehicle Electronic Control Unit (ECU) software versions. Operations may include receiving a prompt to adjust an ECU of a vehicle from executing a first version of ECU software to a second version of ECU software; configuring, in response to the prompt and based on a delta file corresponding to the second version of ECU software, the second version of ECU software on the ECU in the vehicle for execution; and configuring, in response to the prompt, the first version of ECU software on the ECU in the vehicle to become non-executable.
ERROR DETECTION AND CORRECTION METHOD AND CIRCUIT
An error detection and correction method is provided. The method includes: when a pipeline stage error is detected, correcting the pipeline stage error; when it is determined that a plurality of cascaded pipeline stage circuits have continuous pipeline stage errors, stopping all operations of all pipeline stage circuits; flushing the data of the pipeline stage circuits; and re-processing the data of the pipeline stage circuits at a downclocked frequency.
SYSTEM, METHOD, AND COMPUTER PROGRAM PRODUCT FOR LOCATION AWARE DEVICE FAULT DETECTION
A system, method, and computer program product for identifying location-specific faults are provided. Some embodiments may include receiving first device status data associated with a first computing device and the first device status data may comprise first location-indicative data indicative of a location. Some embodiments may include comparing the first device status data with second device status data associated with one or more second computing devices and the second device status data may comprise second location-indicative data indicative of the location. In some embodiments, based on the comparison of the first device status data and the second device status data, determining that the first computing device is affected by one or more of a device-specific fault or a location-specific fault. Some embodiments may include causing information regarding the device-specific fault or the location-specific fault to be displayed via a graphical user interface.
Execution circuits using discardable state
There is provided execution circuitry. Storage circuitry retains a stored state of the execution circuitry. Operation receiving circuitry receives, from issue circuitry, an operation signal corresponding to an operation to be performed that accesses the stored state of the execution circuitry from the storage circuitry. Functional circuitry seeks to perform the operation in response to the operation signal by accessing the stored state of the execution circuitry from the storage circuitry. Delete request receiving circuitry receives a deletion signal and in response to the deletion signal, deletes the stored state of the execution circuitry from the storage circuitry. State loss indicating circuitry responds to the operation signal when the stored state of the execution circuitry is not present and is required for the operation by indicating an error. In addition, there is provided a data processing apparatus comprising issue circuitry to issue an operation to execution circuitry. The execution circuitry stores a stored state that is accessed during performance of the operation and error detecting circuitry detects an indication of an error from the execution circuitry that the stored state is required for performance of the operation and that the stored state has been deleted.
System and Method for Handling Real-Time Transactional Events
A system, method, and memory for handling real-time transactional events is disclosed. The exemplary system a processor to detect and add an event to a queue and identify an associated event type. Event types can require downstream processing by at least one provider. The processor decomposes the event into tasks by comparison to event types which associate downstream provider requirements to tasks and routes. One or more routes are assigned to the tasks, each route defined by at least one processor of a plurality of processors. One or more routes are defined by transmitting a request for downstream processing to the at least one provider. The processor, upon detecting incomplete performance of the one or more routes, either updates the tasks associated with the incomplete route, or marks the event associated with the route as incomplete in the queue.