Application to breast cancer data from the Cancer Genome Atlas Sample Clauses

Application to breast cancer data from the Cancer Genome Atlas. In the real data application, we use the High-quality INTeractomes (HINT) database for the biological network (Das and Yu, 2012). We apply our method to the TCGA breast cancer (BRCA) RNA-seq gene expression dataset with 762 subjects and 10, 792 genes in the network. The response variable we consider here is ER status - whether Method PMSE TP FP AUC CE TP FP AUC Linear regression Logistic regression true signal nodes are connected Lasso 21.7(0.6) 9.5(0.1) 54.4(3.8) 0.982(0.004) 43.3(1.6) 8.4(0.2) 29.6(3.4) 0.954(0.007) Elastic-net 23.2(0.7) 9.6(0.1) 69.0(3.9) 0.975(0.005) 57.9(2.4) 7.7(0.2) 22.4(3.2) 0.961(0.006) TGLG (ε = 10−5) 21.8(0.9) 9.3(0.1) 14.6(1.5) 0.968(0.006) 35.2(1.3) 8.0(0.2) 7.8(0.9) 0.902(0.011) TGLG (logε ∼ N (−5, 9)) 20.7(0.7) 9.1(0.1) 10.1(1.5) 0.957(0.006) 35.4(1.4) 7.9(0.3) 8.3(1.0) 0.893(0.011) TGLG (logε ∼ N (−5, 9)) misspecified 21.2(0.8) 9.1(0.1) 11.3(1.5) 0.952(0.007) 37.1(1.3) 7.8(0.2) 9.3(1.1) 0.892(0.012) T rue signal nodes are disconnected Lasso 20.8(0.6) 9.8(0.1) 55.0(3.7) 0.989(0.003) 43.4(1.2) 8.9(0.2) 26.8(3.0) 0.979(0.004) Elastic-net 22.2(0.7) 9.8(0.1) 68.6(3.9) 0.988(0.003) 55.7(1.9) 8.4(0.2) 27.3(4.0) 0.981(0.003) TGLG (ε = 10−5) 21.7(0.8) 9.4(0.1) 16.7(1.9) 0.971(0.006) 35.5(1.4) 8.4(0.2) 7.8(0.9) 0.922(0.010) TGLG (logε ∼ N (−5, 9)) 20.6(0.8) 9.6(0.1) 11.6(2.1) 0.980(0.004) 36.9(1.5) 8.5(0.2) 9.4(1.1) 0.925(0.009) TGLG (logε ∼ N (−5, 9)) misspecified 21.3(0.9) 9.4(0.1) 11.4(1.7) 0.969(0.005) 35.3(1.2) 8.5(0.2) 8.4(0.9) 0.928(0.008) Table 2.4: Simulation results for scale free network. True TP is 10. Sample size is 200 and dimension is 1,000. the cancer cells grow in response to the estrogen. The ER status is a molecular char- acteristic of the cancer which has important implications in prognosis. The purpose here is not focused on prediction. Rather we intend to find genes and functional modules that are associated with ER status, through which biological mechanisms differentiating the two subgroups of cancer can be further elucidated. We code ER-positive as 1 and ER-negative as 0. We remove subjects with un- known ER status. In total, there are 707 subjects with 544 ER-positive and 163 ER-negative. We remove 348 gene nodes with low count number, which leaves us with 10,444 nodes. To apply our methods, we first standardize the gene nodes and then apply a logistic regression model for network marker selection. For prior settings, we use σ2 ∼ IG(0.01, 0.01), σ2 ∼ IG(0.01, 0.01) and σ2 = 50. We fix λ at different grid val...
AutoNDA by SimpleDocs

Related to Application to breast cancer data from the Cancer Genome Atlas

  • Hepatitis B Vaccine Where the Hospital identifies high risk areas where employees are exposed to Hepatitis B, the Hospital will provide, at no cost to the employees, a Hepatitis B vaccine.

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • How Do I Get More Information? This Notice summarizes the Action, the terms of the Settlements, and your rights and options in connection with the Settlements. More details are in the Settlement Agreements, which are available for your review at xxx.XxxxxxxxxXxxXxxxxxxxxXxxxxxxxxx.xxx. The Settlement Website also has the Second Amended Complaint and other documents relating to the Settlements. You may also call toll-free 0-000-000-0000 or write the Claims Administrator at: Financial Aid Antitrust Settlements, c/o Claims Administrator, 0000 Xxxx Xxxxxx, Xxxxx 0000, Xxxxxxxxxxxx, XX 00000. To: Settlement Class Member Email Address From: Claims Administrator Subject: Notice of Proposed Class Action Settlement – Xxxxx, et al. x. Xxxxx University, et al. Please visit xxx.XxxxxxxxxXxxXxxxxxxxxXxxxxxxxxx.xxx for more information. • The Court has preliminarily approved proposed settlements (“Settlements”) with the following ten schools: Brown University, the University of Chicago, the Trustees of Columbia University in the City of New York, Trustees of Dartmouth College, Duke University, Emory University, Northwestern University, Xxxxxxx Xxxxx Xxxx University, Vanderbilt University, and Yale University (collectively the “Settling Universities”). • The Court has also preliminarily approved a class of students who attended one or more of the Settling Universities during certain time periods. This is referred to as the “Settlement Class,” which is defined in more detail below.

  • Volunteer Firefighting Leave Leave without pay will be granted when an employee who is a volunteer firefighter is called to duty to respond to a fire, natural disaster or medical emergency.

  • Release of Pre-Distribution Claims (a) Except (i) as provided in Section 6.1(c), (ii) as may be otherwise expressly provided in this Agreement or any Ancillary Agreement and (iii) for any matter for which any Horizon Indemnified Party is entitled to indemnification pursuant to this Article VI, effective as of the Distribution, Horizon does hereby, for itself and each other Horizon Entity and their respective Affiliates, Predecessors, successors and assigns, and, to the extent Horizon legally may, all Persons that at any time prior or subsequent to the Distribution have been stockholders, directors, officers, members, agents or employees of Horizon or any other Horizon Entity (in each case, in their respective capacities as such), release and forever discharge each TriMas Entity, their respective Affiliates, Predecessors, successors and assigns, and all Persons that at any time prior to the Distribution have been stockholders, directors, officers, members, agents or employees of TriMas or any other TriMas Entity (in each case, in their respective capacities as such), and their respective heirs, executors, administrators, successors and assigns, from any and all Liabilities whatsoever, whether at law or in equity, whether arising under any Contract, by operation of law or otherwise, existing or arising from or relating to any acts or events occurring or failing to occur or alleged to have occurred or to have failed to occur or any conditions existing or alleged to have existed on or before the Distribution Date, whether or not known as of the Distribution Date, including in connection with the transactions and all other activities to implement the Separation or the Distribution. (b) Except (i) as provided in Section 6.1(c), (ii) as may be otherwise provided in this Agreement or any Ancillary Agreement and (iii) for any matter for which any TriMas Indemnified Party is entitled to indemnification pursuant to this Article VI, effective as of the Distribution, TriMas does hereby, for itself and each other TriMas Entity and their respective Affiliates, Predecessors, successors and assigns, and, to the extent TriMas legally may, all Persons that at any time prior to the Distribution have been stockholders, directors, officers, members, agents or employees of TriMas or any other TriMas Entity (in each case, in their respective capacities as such), release and forever discharge each Horizon Entity, their respective Affiliates, successors and assigns, and all Persons that at any time prior to the Distribution have been stockholders, directors, officers, members, agents or employees of Horizon or any other Horizon Entity (in each case, in their respective capacities as such), and their respective heirs, executors, administrators, successors and assigns, from any and all Liabilities whatsoever, whether at law or in equity, whether arising under any Contract, by operation of law or otherwise, existing or arising from any acts or events occurring or failing to occur or alleged to have occurred or to have failed to occur or any conditions existing or alleged to have existed on or before the Distribution Date, whether or not known as of the Distribution Date, including in connection with the transactions and all other activities to implement the Separation or the Distribution. (c) Nothing contained in Sections 6.1(a) or 6.1(b) will impair any right of any Person to enforce this Agreement, any Ancillary Agreement, including the applicable Schedules hereto and thereto, or any arrangement that is not to terminate as of the Distribution, as specified in Section 2.3(b). In addition, nothing contained in Sections 6.1(a) or 6.1(b) will release any Person from: (i) any Liability provided in or resulting from any Contract among any TriMas Entities and any Horizon Entities that is not to terminate as of the Distribution, as specified in Section 2.3(b), or any other Liability that is not to terminate as of the Distribution, as specified in Section 2.3(b); (ii) any Liability assumed, transferred, assigned or allocated to the Group of which such Person is a member in accordance with, or any other Liability of any member of any Group under, this Agreement or any Ancillary Agreement; or (iii) any Liability the release of which would result in the release of any Person other than a Person released pursuant to this Section 6.1; provided that the Parties agree not to bring suit or permit any of their Subsidiaries to bring suit against any Person with respect to any Liability to the extent that such Person would be released with respect to such Liability by this Section 6.1 but for the provisions of this clause (iii). (d) Horizon will not make, and will not permit any other Horizon Entity to make, any claim or demand, or commence any Action asserting any claim or demand, including any claim for indemnification, against any TriMas Entity, or any other Person released pursuant to Section 6.1(a), with respect to any Liabilities released pursuant to Section 6.1(a). TriMas will not, and will not permit any other TriMas Entity to, make any claim or demand, or commence any Action asserting any claim or demand, including any claim for indemnification, against any Horizon Entity, or any other Person released pursuant to Section 6.1(b), with respect to any Liabilities released pursuant to Section 6.1(b).

  • Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Xxxx (e.g. hairpinning): 1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises. 2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated. 3. If capacity exists, provide "side-door" porting through the switch. 4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch). 2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases. 2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.

  • Required Confidentiality Claim Form This is a requirement of the TIPS Contract and is non-negotiable. TIPS provides the required TIPS Confidentiality Claim Form in the "Attachments" section of this solicitation. Vendor must execute this form by either signing and waiving any confidentiality claim, or designating portions of Vendor's proposal confidential. If Vendor considers any portion of Vendor's proposal to be confidential and not subject to public disclosure pursuant to Chapter 552 Texas Gov’t Code or other law(s) and orders, Vendor must have identified the claimed confidential materials through proper execution of the Confidentiality Claim Form. If TIPS receives a public information act or similar request, any responsive documentation not deemed confidential by you in this manner will be automatically released. For Vendor documents deemed confidential by you in this manner, TIPS will follow procedures of controlling statute(s) regarding any claim of confidentiality and shall not be liable for any release of information required by law, including Attorney General determination and opinion. Notwithstanding any other Vendor designation of Vendor's proposal as confidential or proprietary, Vendor’s submission of this proposal constitutes Vendor’s agreement that proper execution of the required TIPS Confidentiality Claim Form is the only way to assert any portion of Vendor's proposal as confidential.

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

  • COVID-19 Vaccine Passports Pursuant to Texas Health and Safety Code, Section 161.0085(c), Contractor certifies that it does not require its customers to provide any documentation certifying the customer’s COVID-19 vaccination or post-transmission recovery on entry to, to gain access to, or to receive service from the Contractor’s business. Contractor acknowledges that such a vaccine or recovery requirement would make Contractor ineligible for a state-funded contract.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!