Abstract: Disclosed herein is Differential Subclone Eradication and Resistance Analysis (DSER), a method developed to identify molecular targets for improved therapy by direct comparison of genomic features of eradicated and resistant subclones in pre- and post-treatment samples from a patient with BRCA2-deficient metastatic prostate cancer. FANCI and EYA4 were identified as candidate DNA repair-related targets for converting subclones from resistant to eradicable, and RNAi-mediated depletion of FANCI confirmed it as a potential target. The EYA4 alteration was associated with adjacent L1 transposon insertion during cancer evolution upon treatment. L1 activation was inhibited by the antiretroviral drug azidothymidine. In conclusion DSER provides an informative intermediate step toward effective precision cancer medicine, especially in cases with dramatic but temporary metastatic tumor regression.

Abstract: A method for binder jetting a three-dimensional (3D) object includes receiving a geometry of the object to be printed and generating instructions for printing the object. Generating the instructions includes slicing the geometry of the object into a series of cross-sectional shapes corresponding to where a binder fluid will be deposited onto a powder bed to form the object, and including a plurality of negatively printed features within at least some of the series of cross-sectional shapes, wherein an amount of binder fluid to be deposited in the negatively printed features is less than an amount of binder fluid to be deposited in a remainder of the cross-sectional shape. The amount of binder fluid to be deposited in the negatively printed features and a size of the negatively printed features is configured to allow gas to escape from the powder bed.

Abstract: The invention features diagnostic and therapeutic methods and compositions featuring androgen receptor variant proteins and nucleic acid molecules whose expression is increased in androgen related diseases or disorders.

Abstract: Extract, Transform, Load (ETL) processing may be initiated by detected events. A trigger event may be associated with an ETL process apply one or more transformations to a source data object. The trigger event may be detected for the ETL process and evaluated with respect to one or more execution conditions for the ETL process. If the execution conditions for the ETL process are satisfied, then the ETL process may be executed. At least some of the source data object may be obtained, the one or more transformations of the ETL process may be applied, and one or more transformed data objects may be stored.

Abstract: Recognizing unknown data objects may be implemented for data objects stored in a data store. Data objects that are identified as unknown may be accessed to retrieve a portion of the data object. Different representations of the data object may be generated for recognizing different data schemas. An analysis of the representations may be performed to identify a data schema for the unknown data object. The data schema may be stored in a metadata store for the unknown data object.

Abstract: A metadata catalog may store metadata about data sources. The metadata may define table, column, partition and/or data formats, as well as title information, textual descriptions, modification information, data schemas and access information, such as location and connection information. A metadata catalog service may provide a shared, persistent, central repository for the metadata. The metadata of the catalog may be published via multiple access mechanisms and programmatically obtained and processed by other programs via the metadata catalog service. Metadata consumers may utilize the metadata catalog service to perform various metadata tasks, such as metadata retrieval, creation, addition, modification and/or deletion. The metadata catalog service may be directly integrated into existing data analytic tools as a persistent and durable metadata store allowing users to utilize the broad set of data processing tools.

Abstract: Code may be dynamically routed to computing resources for execution. Code may be received for execution on behalf of a client. Execution criteria for the code may be determined and computing resources that satisfy the execution criteria may be identified. The identified computing resources may then be procured for executing the code and then the code may be routed to the procured computing resources for execution. Permissions or authorization to execute the code may be shared to ensure that computing resources executing the code have the same permissions or authorization when executing the code.

Abstract: Data transformation workflows may be generated to transform data objects. A source data schema for a data object and a target data format or target data schema for a data object may be identified. A comparison of the source data schema and the target data format or schema may be made to determine what transformations can be performed to transform the data object into the target data format or schema. Code to execute the transformation operations may then be generated. The code may be stored for subsequent modification or execution.

Abstract: A conversion system for a tiltrotor aircraft may be configured to control tilting of a pylon assembly relative to a wing of the aircraft. The system may include a means for generating asymmetric thrust with a propulsion rotor carried by the pylon assembly to generate a first torque on the pylon assembly in a first direction. The system may include a brake mechanism to selectively resist the first torque on the pylon assembly by applying a second torque to the pylon assembly in a second direction opposite the first direction. The rotor (via asymmetric thrust generated by the rotor) and the brake mechanism are coordinated to work against each other to control the tilt rate and angle of the pylon assembly during conversion between flight modes of the tiltrotor aircraft. Other aspects of the present technology include methods of tilting rotors of tiltrotor aircraft using asymmetric thrust and brake mechanisms.

Abstract: Dynamic generation of data catalogs may be implemented for accessing data sets in different storage locations. Data sets may be accessed in order to extract portions of data. Structure recognition techniques may be applied to the extracted data in order to determine structural information for the data sets. The structural information may then be stored as part of a data catalog for the data sets. Requests to access the data catalog from different clients may be received and the requested structural data supplied so that the clients may access different data sets utilizing the supplied structural data. Data catalogs may be updated as changes to data sets are made.

Abstract: The present disclosure relates to an inhibitor of human TRPM3 for use in the treatment or prevention of migraine, including in subjects whose migraines are not responsive to CGRP inhibition or whose migraines are responsive to triptans. Combination therapies are also described. In other aspects, the present disclosure provides methods for identifying suitable patients, methods for identifying inhibitors of human TRPM3, cell lines and agonists for use in such methods and a method for measuring PACAP release.

Abstract: Code may be dynamically routed to computing resources for execution. Code may be received for execution on behalf of a client. Execution criteria for the code may be determined and computing resources that satisfy the execution criteria may be identified. The identified computing resources may then be procured for executing the code and then the code may be routed to the procured computing resources for execution. Permissions or authorization to execute the code may be shared to ensure that computing resources executing the code have the same permissions or authorization when executing the code.

Abstract: Extract, Transform, Load (ETL) processing may be initiated by detected events. A trigger event may be associated with an ETL process apply one or more transformations to a source data object. The trigger event may be detected for the ETL process and evaluated with respect to one or more execution conditions for the ETL process. If the execution conditions for the ETL process are satisfied, then the ETL process may be executed. At least some of the source data object may be obtained, the one or more transformations of the ETL process may be applied, and one or more transformed data objects may be stored.

Abstract: Disclosed herein is Differential Subclone Eradication and Resistance Analysis (DSER), a method developed to identify molecular targets for improved therapy by direct comparison of genomic features of eradicated and resistant subclones in pre- and post-treatment samples from a patient with BRCA2-deficient metastatic prostate cancer. FANCI and EYA4 were identified as candidate DNA repair-related targets for converting subclones from resistant to eradicable, and RNAi-mediated depletion of FANCI confirmed it as a potential target. The EYA4 alteration was associated with adjacent L1 transposon insertion during cancer evolution upon treatment. L1 activation was inhibited by the antiretroviral drug azidothymidine. In conclusion DSER provides an informative intermediate step toward effective precision cancer medicine, especially in cases with dramatic but temporary metastatic tumor regression.

Abstract: Extract, Transform, Load (ETL) processing may be initiated by detected events. A trigger event may be associated with an ETL process apply one or more transformations to a source data object. The trigger event may be detected for the ETL process and evaluated with respect to one or more execution conditions for the ETL process. If the execution conditions for the ETL process are satisfied, then the ETL process may be executed. At least some of the source data object may be obtained, the one or more transformations of the ETL process may be applied, and one or more transformed data objects may be stored.

Abstract: Code may be dynamically routed to computing resources for execution. Code may be received for execution on behalf of a client. Execution criteria for the code may be determined and computing resources that satisfy the execution criteria may be identified. The identified computing resources may then be procured for executing the code and then the code may be routed to the procured computing resources for execution. Permissions or authorization to execute the code may be shared to ensure that computing resources executing the code have the same permissions or authorization when executing the code.

Abstract: History for data objects may be maintained to detect data events. An indication of an Extract, Transform, Load (ETL) process applied to one or more source data objects to generate one or more transformed data objects may be received. History for the source data objects may be updated to include the transformed data objects and the ETL process that generated the transformed data objects. An evaluation of the update may be performed to determine whether an event associated with the data lineage is triggered. If the event is triggered, a notification of the event may be sent to one or more subscribers for the event.

Abstract: Data transformation workflows may be generated to transform data objects. A source data schema for a data object and a target data format or target data schema for a data object may be identified. A comparison of the source data schema and the target data format or schema may be made to determine what transformations can be performed to transform the data object into the target data format or schema. Code to execute the transformation operations may then be generated. The code may be stored for subsequent modification or execution.

Abstract: Code may be dynamically routed to computing resources for execution. Code may be received for execution on behalf of a client. Execution criteria for the code may be determined and computing resources that satisfy the execution criteria may be identified. The identified computing resources may then be procured for executing the code and then the code may be routed to the procured computing resources for execution. Permissions or authorization to execute the code may be shared to ensure that computing resources executing the code have the same permissions or authorization when executing the code.

Abstract: Data transformation workflows may be generated to transform data objects. A source data schema for a data object and a target data format or target data schema for a data object may be identified. A comparison of the source data schema and the target data format or schema may be made to determine what transformations can be performed to transform the data object into the target data format or schema. Code to execute the transformation operations may then be generated. The code may be stored for subsequent modification or execution.