Abstract: Construct-modified tags conveying development-phase compiler requests are introduced into source code to facilitate communication between developers, identify areas that need developer attention, send directives to a compiler, and other development features in an integrated development environment, during the software development phase. A REQUESTREVIEW tag conveys a request to a compiler to notify a reviewer that source code is ready for review. A REVIEWED tag indicates a review has been performed and may signify code acceptance. Alternatively, a FIX or OPTIMIZE tag may be used to identify further code development requirement. These tags may incorporate properties, permissions, and generate notifications. Methods may facilitate code review and feedback in other aspects. Methods ensure that tags no longer remain in source code once the software development process enters the production phase.

Abstract: Enhanced search results are generated using multi-document summarization. A multi-document summarization system receives a search query from a user and retrieves a plurality of search result documents based on the search query. The summarization system generates a summary of each of the plurality of search result documents using distinct per-document summarization machine learning models, where the distinct per-document summarization machine learning models are trained on a training dataset. The summarization system synthesizes the summary of each of the plurality of search result documents into a single-consolidated answer responsive to the received search query. The multi-document summarization system formats the single-consolidated answer to include citations to the plurality of search result documents.

Abstract: A set of construct-modification tags conveying development-phase compiler requests are introduced into source code to facilitate communication between developers, identify areas that need developer attention, send directives to a compiler, and other development features in an integrated development environment, during the software development phase. Tags may incorporate properties, permissions, and generate notifications. Example tags include IGNORE, DEACTIVATE, OPTIMIZE, FIX, ALTERNATE, PROTOTYPE, REQUESTREVIEW, REVIEWED, CANDIDATE, and BESTCANDIDATE. Methods ensure that tags no longer remain in source code once the software development process enters the production phase.

Abstract: An interactive search method is disclosed, utilizing a browser-based interface and generative artificial intelligence to enhance user search experiences. The method involves receiving an initial search query from a user, generating a proposed search result via hardware processors, and displaying the result to the user. To refine search accuracy, the method recommends clarifying questions, soliciting additional search parameters. Upon receiving an updated search query, the system interactively refines the initial query and displays an updated search result. This process allows for dynamic query adjustment and improved search result relevance in real-time.

Abstract: Construct-modification tags conveying development-phase compiler requests are introduced into source code to facilitate communication between developers, identify areas that need developer attention, send directives to a compiler, and other development features in an integrated development environment, during the software development phase. A DEACTIVATE tag conveys a request to a compiler to deactivate an associated construct, as well as to find and deactivate dependencies of the construct. A DEACTIVATE tag may incorporate properties, permissions, and generate notifications, including a condition for evaluation, the deactivation conditionally responsive to the result of the condition evaluation. Methods ensure that tags no longer remain in source code once the software development process enters the production phase.

Abstract: Construct-modification tags conveying development-phase compiler requests are introduced into source code to facilitate communication between developers, identify areas that need developer attention, send directives to a compiler, and other development features in an integrated development environment, during the software development phase. A hierarchy of developers and associated permissions is maintained. A tag may be associated with one or more developers as well as one or more permissions. Notifications associated with tags may be issued to one or more developers in response to a conveyed compiler request. General messages to all the developers and personalized messages to one or more developers indicate the presence of tags and need to resolve issues before the software development process enters the production phase.

Abstract: A compile-time link type manager is defined to facilitate development of source code with disciplined link type object management at runtime. In one aspect, the link type manager ensures that all link type object management constructs have associated event handlers. Additionally, an event handler can be evaluated at compile time to ensure that it meets certain conditions for the particular link type, referred to as link-type criteria.

Abstract: An example apparatus includes a blockchain group data component structured to interpret a plurality of blockchain description values each corresponding to at least one of a plurality of blockchains, a blockchain group index component structured to provide a blockchain group index data structure in response to the plurality of blockchain description values, the blockchain group index data structure comprising an attribute association description. The attribute association description includes an identified attribute value, a first association of the identified attribute value to a first entity associated with a first blockchain of the plurality of blockchains, and a second association of the identified attribute value to a second entity associated with a second blockchain of the plurality of blockchains. The apparatus includes a cross-chain interaction component structured to perform a cross-chain interaction operation in response to the blockchain group index data structure.

Abstract: A compile-time link type manager is defined to facilitate development of source code with disciplined link type object management at run-time. In one aspect, when a compile-time link type manager encounters a link type object management construct in source code, it will emit code for a runtime object management engine that processes generic link type object management instructions at runtime. It will also compile type-specific instructions from the link type object management construct for accessing the generic instructions in the runtime object management engine for affecting a link type object at runtime. A runtime object management engine may perform various checks, referred to as link-type criteria, at runtime prior to executing a link type object management instruction. When defined link-type criteria are satisfied for a link type object management instruction for an object at runtime, the instruction is carried out.

Abstract: A method for forecasting part sales, including collecting sales data for a part over a series of sales time periods and collecting activity data for a plurality of activity types over a series of activity time periods for a plurality of machines including the part. A mean activity time can be calculated for each activity type for each time period in the series of activity time periods based on the collected activity data. An activity probability density function of the mean activity times for each activity type is created and a machine learning model is trained using an expectation of activity derived from the probability density functions for each activity type and the collected sales data. Machine activity data for a set of machines can be fed into the trained model to derive a part sales probability density function for the set of machines.

Abstract: A redriver system adapted for coupling to a first device and to a second device includes first and second transmitter drivers and a snoop circuit. The first transmitter driver has a first enable input. The second transmitter driver has a second enable input. The snoop circuit is coupled to the first and second enable inputs. The snoop circuit is configured to determine whether the first device and the second device are to operate according to a first protocol. Responsive to the snoop circuit determining that the first and second devices are to operate according to the first protocol, the snoop circuit enables the first transmitter driver and disables the second transmitter driver. Responsive to the snoop circuit determining that the first and second devices are not to operate according to the first protocol, the snoop circuit disables the first transmitter driver and enables the second transmitter driver.

Abstract: An example apparatus includes an account information circuit structured to interpret first identifying information for a first blockchain account and second identifying information for a second blockchain account, the first identifying information including a trust rating value, and the second identifying information including a transaction confirmation value corresponding to a transaction between the first blockchain account and the second blockchain account. An apparatus includes a trust value adjustment circuit structured to interpret a transaction rating value from a user associated with the second blockchain account, and to adjust the trust rating value in response to the transaction rating value and the transaction confirmation value. An apparatus includes an account trust matching execution circuit structured to perform an account trust operation in response to the adjusted trust rating value.

Abstract: An example apparatus includes a blockchain data circuit that interprets a blockchain description value, a blockchain index circuit that provides a blockchain index data structure in response to the blockchain description value, the blockchain index data structure including a number of attribute values for each of a number of entities associated with the blockchain description value, and a blockchain search circuit that exercises a user interface. The user interface allows for interpreting a user search value, and the blockchain search circuit provides a search description to the user interface in response to the user search value and the blockchain index data structure.

Abstract: An example apparatus includes a blockchain monitoring circuit structured to interpret a blockchain index data structure comprising a plurality of attribute values for each of a plurality of assets associated with a blockchain. An apparatus includes a blockchain asset ranking circuit structured to determine an asset rank value for each asset of the plurality of assets and includes a blockchain transaction assistant circuit structured to, in response to the asset rank value for each asset, perform at least one operation selected from: provide an asset ranking communication to a user interface for transactions associated with the blockchain; or store the asset rank value for each asset of the plurality of assets on the blockchain index data structure.

Abstract: An example apparatus includes an account information circuit structured to interpret identifying information for a seller blockchain account and for each one of at least one buyer blockchain account, the identifying information for each one of the at least one buyer blockchain account including an attribute interest value. An apparatus further includes an asset attribute circuit structured to interpret an asset attribute value for an asset associated with the seller blockchain account. An apparatus further includes a buyer interest circuit structured to determine a buyer interest value for each one of the at least one buyer blockchain account in response to each corresponding attribute interest value and the asset attribute value. An apparatus includes a buyer identification execution circuit structured to perform a buyer identification operation in response to the buyer interest value.

Abstract: A method for forecasting part sales, including collecting sales data for a part over a series of sales time periods and collecting activity data for a plurality of activity types over a series of activity time periods for a plurality of machines including the part. A mean activity time can be calculated for each activity type for each time period in the series of activity time periods based on the collected activity data. An activity probability density function of the mean activity times for each activity type is created and a machine learning model is trained using an expectation of activity derived from the probability density functions for each activity type and the collected sales data. Machine activity data for a set of machines can be fed into the trained model to derive a part sales probability density function for the set of machines.

Abstract: A redriver system adapted for coupling to a first device and to a second device includes first and second transmitter drivers and a snoop circuit. The first transmitter driver has a first enable input. The second transmitter driver has a second enable input. The snoop circuit is coupled to the first and second enable inputs. The snoop circuit is configured to determine whether the first device and the second device are to operate according to a first protocol. Responsive to the snoop circuit determining that the first and second devices are to operate according to the first protocol, the snoop circuit enables the first transmitter driver and disables the second transmitter driver. Responsive to the snoop circuit determining that the first and second devices are not to operate according to the first protocol, the snoop circuit disables the first transmitter driver and enables the second transmitter driver.

Abstract: The present invention provides methods of treatment of cancer patients having deficiency in at least one non-BRCA1/2 gene involved in the homologous recombination repair (HRR) pathway with a poly(ADP-ribose) polymerase (PARP) inhibitor such as niraparib. In particular, cancer patients having a deficiency in at least one gene selected from the group consisting of BRCA1, BRCA2, ATM, ATR, BAP1, BARD1, BLM, BRIP1, MRE11A, NBN, PALB2, RAD51, RAD51B, RAD51C, RAD51D, RAD52, RAD54L, XRCC2, TP53, or RBI can benefit from treatment with niraparib.

Abstract: Aspects of the disclosure relate to enabling independent storage and processing of data with centralized event control. An event control computing platform may receive an indicator of a processing task associated with processing a dataset. Subsequently, the event control computing platform may authenticate the indicator of the processing task. Then the event control computing platform may identify and allocate resources for executing the processing task and storing the dataset. Finally, the event control computing platform may generate and transmit a series of commands to cause the dataset to be accessed by the processing platform, cause the processing task associated with the dataset to be executed, and cause the processed dataset to be stored on the storage platform.

Abstract: Methods, systems, and apparatus include computer programs encoded on a computer-readable storage medium, including a system including a search engine server that provides a search user interface. The search user interface includes a search field that enables a user to submit a search request as well as a set of contextual labels that enable a user to specify, through interaction with one of multiple different presented contextual labels, a topical context for the search request. The search engine server identifies a set of search results using the search request and the topical context for the search request. The system also includes a content server that identifies additional content related to both the search request and the topical context and provides the identified additional content for presentation with the set of search results in the search user interface.