Abstract: A method of classifying webpages using a data processing system includes generating a plurality of topic models from a first plurality of training documents. The method further includes performing inference using the plurality of topic models on a second plurality of training documents, to generate a first set of feature vectors and a second set of feature vectors. The method further includes performing supervised classification of a third plurality of training documents using the first set of feature vectors, to generate a plurality of candidate topic models. The method further includes evaluating the plurality of candidate topic models using the second set of feature vectors and storing, in a production model datastore, at least some of the plurality of candidate topic models as production topic models, responsive to the evaluation, wherein the first plurality of training documents comprise text obtained from an inventory of web pages.

Abstract: The various embodiments herein disclose a system and method for generating a delta code coverage information. The system for generating delta code coverage information comprises, a source control module configured for storing a plurality of software program code files to be processed and a plurality of code coverage data corresponding to the plurality of software program code files, a processor configured to generate a delta code coverage data for analysis for each of the plurality of software program code files on a line level or at a branch level by performing a time based delta code coverage process and a path based delta code coverage process.

Abstract: A method and system for a robotic device comprising a propulsion mechanism to move the robotic device, a sensor, a user interface for entering service area dimension information to establish a service area proximate the robotic device, and a processing facility comprising a processor and a memory, the processing facility configured to store a set of instructions that, when executed, cause the robotic device to receive service area dimension information for the service area through the user interface, wherein the service area is determined by the service area dimension information entered into the user interface, and utilize the propulsion mechanism to move the robotic device through the service area and to perform a service task in the service area.

Abstract: A method and system for a robotic device comprising a propulsion mechanism, a sensor for sensing objects, a localization and mapping system, a processing facility comprising a processor and a memory, the processing facility configured to store a set of instructions that, when executed, cause the robotic device to upon selection by a user, place the robotic device in a mapping mode, wherein the mapping mode causes the robotic device to move through the service area and create a digital map, and upon selection by the user, place the robotic device in a service task mode, wherein while in service task mode the robotic device performs a service task in the service area based on sensing the service area with the sensor and utilizing the created digital map.

Abstract: A method and system for a robotic device comprising a propulsion mechanism, an orientation sensor, a stored digital map of a service area, a sensor for sensing objects, a navigation and orientation system, and a processing facility comprising a processor and a memory, the processing facility causing the robotic device to determine and store a pose position of the robotic device at a plurality of sequential locations as the robotic device is guided by a user along a path from a start location to an end location through the service area, and as commanded by the user and utilizing the navigation and orientation system, re-trace the path from the start location to the end location replicating the stored pose position of the robotic device at the plurality of sequential locations.

Abstract: A method and system for a reconfigurable robotic platform through a plurality of interchangeable service modules and adapted to engage in both autonomous and interactive maintenance and monitoring of a service area, the robotic platform configured to sense objects in the service area utilizing the at least one sensor, derive a service plan for the service area comprising at least one service task based, at least in part, on real-time sensing of the service area and a stored digital map of the service area, wherein the navigation system utilizes the digital map and the real-time sensing to navigate within the service area during execution of the service plan, and operate the robotic device to provide a service task to a generally planar surface proximate the robotic device in accordance with the service plan.

Abstract: A method and system for a reconfigurable robotic platform through a plurality of interchangeable service modules and adapted to engage in both autonomous and interactive maintenance and monitoring of a service area, the robotic platform configured to execute a stored service plan for a service area, the service plan comprising a service plan sequence comprising a service treatment to a surface of the service area, identify a special treatment area utilizing the surface sensor, alter the service plan sequence based on identifying the special treatment area in the service area, wherein the altering of the service plan sequence includes providing an additional service to the special treatment area, and resume execution of the service plan.

Abstract: A method and system for a reconfigurable robotic platform through a plurality of interchangeable service modules and adapted to engage in both autonomous and interactive maintenance and monitoring of a service area, the robotic platform configured to execute a stored service plan for the service area, the service plan comprising a service plan sequence comprising a service treatment step, alter the service plan sequence based on detecting an object that is a treatment obstacle in the service area as detected by the sensor, the treatment obstacle preventing execution of the service treatment step at a service treatment location within the service area, wherein the altered service plan sequence comprises moving around the treatment obstacle and skipping the service treatment step, store the service treatment location for later treatment, and resume execution of the service plan.

Abstract: In one embodiment, an apparatus comprises an input output controller. The input output controller is configured to establish a connection between a host computing device and an external device. The input output controller is further configured to determine that the external device is operating using a slower data transmission speed than the input output controller. The input output controller is further configured to throttle data received from the external device.

Abstract: Pharmaceutical formulations that resist ethanol-induced dose dumping and methods of use thereof.

Abstract: When a software component is starting, such as but not limited to a task or a subtask, the component pushes its identification (ID) onto a stack. The component executes its other instructions. If the component completes its instructions so that it can terminate normally, it pops the stack, which removes its ID from the stack. If the component fails, such as by not being able to complete its instructions, it will not be able to pop the stack so its ID will remain in the stack. Another software process can read the IDs in the stack to identify which components have failed and can automatically take a specified action, such as by sending an email message to, sending a text message to, or calling by telephone, a person or persons responsible for that software component.

Abstract: A method and system for a reconfigurable robotic platform through a plurality of interchangeable service modules and adapted to engage in both autonomous and interactive maintenance and monitoring of a service area, the robotic platform configured to perform a wide variety of tasks utilizing the plurality of interchangeable service modules, and navigating through the service area utilizing a plurality of sensors and guided through a stored service plan for the service area.

Abstract: The various embodiments herein disclose a system and method for generating a delta code coverage information. The system for generating delta code coverage information comprises, a source control module configured for storing a plurality of software program code files to be processed and a plurality of code coverage data corresponding to the plurality of software program code files, a processor configured to generate a delta code coverage data for analysis for each of the plurality of software program code files on a line level or at a branch level by performing a time based delta code coverage process and a path based delta code coverage process.

Abstract: The various embodiments herein provide a system and method for identifying, analyzing and integrating the risks associated with a source code. The system comprises a code coverage module for collecting and transforming the code coverage information by a file name, a source code analyzer module for collecting and transforming source code violations information by the file name, a software configuration management module for collecting and transforming the source code commit information by the file name, a risk analyzer processing module for receiving and relating the collected code coverage information, source code violations information and source code commit information with each other by the file name and a report generation module for publishing the processed result of the collected code coverage information, source code violations information and source code commit information in a report. The report is reviewed for identifying, analyzing and integrating risks associated with source code.

Abstract: When a software component is starting, such as but not limited to a task or a subtask, the component pushes its identification (ID) onto a stack. The component executes its other instructions. If the component completes its instructions so that it can terminate normally, it pops the stack, which removes its ID from the stack. If the component fails, such as by not being able to complete its instructions, it will not be able to pop the stack so its ID will remain in the stack. Another software process can read the IDs in the stack to identify which components have failed and can automatically take a specified action, such as by sending an email message to, sending a text message to, or calling by telephone, a person or persons responsible for that software component.

Abstract: The embodiments herein disclose a method for merging results from multiple runs based on run inputs in a source system. The method involves performing first run on a first input, to receive a first result and performing a second run on a second input to receive a second result. The first result and second result are aggregated based on a set of rules and a plurality of merge cases/conditions to obtain a final result. The first run is performed by carrying out a static analysis on the first inputs. The second run is performed by carrying out a static analysis on the second inputs. A method is also provided for merging cobertura coverage and a source code.

Abstract: When a software component is starting (305), such as but not limited to a task or a subtask, the component pushes (310) its identification (ID) onto a stack. The component then executes (315) its other instructions. If the component completes its instructions so that it can terminate normally (320), then it pops (325) the stack, which removes its ID from the stack. If the component fails, such as by not being able to complete its instructions, then it will not be able to pop the stack so its ID will remain in the stack. Another software process can then read the IDs in the stack to identify (330) which components have failed and can automatically take a specified action (335), such as by sending an email message to, sending a text message to, or calling by telephone, a person or persons responsible for that software component.

Abstract: The various embodiments herein provide a system and method for identifying, analyzing and integrating the risks associated with a source code. The system comprises a code coverage module for collecting and transforming the code coverage information by a file name, a source code analyzer module for collecting and transforming source code violations information by the file name, a software configuration management module for collecting and transforming the source code commit information by the file name, a risk analyzer processing module for receiving and relating the collected code coverage information, source code violations information and source code commit information with each other by the file name and a report generation module for publishing the processed result of the collected code coverage information, source code violations information and source code commit information in a report. The report is reviewed for identifying, analyzing and integrating risks associated with source code.

Abstract: There is provided a method for generating a quote of a first service provider, the quote being personalised to a particular customer. The method comprises: capturing (110, 120) from the particular customer a document (10) from a second service provider that is directed towards the particular customer; extracting information (130) on the particular customer from the document; generating (140, 150) the quote based upon the extracted information; and electronically communicating (160) the quote to the particular customer.

Abstract: When a software component is starting (305), such as but not limited to a task or a subtask, the component pushes (310) its identification (ID) onto a stack. The component then executes (315) its other instructions. If the component completes its instructions so that it can terminate normally (320), then it pops (325) the stack, which removes its ID from the stack. If the component fails, such as by not being able to complete its instructions, then it will not be able to pop the stack so its ID will remain in the stack. Another software process can then read the IDs in the stack to identify (330) which components have failed and can automatically take a specified action (335), such as by sending an email message to, sending a text message to, or calling by telephone, a person or persons responsible for that software component.