File

projects/web-mev/src/app/features/workspace-detail/components/metadata/dialogs/view-info-dialog/view-info-dialog.component.ts

Description

Feature/Observation Information Dialog Component

Modal dialog component which is used to view information about custom observation and feature sets

Implements

OnInit

Metadata

changeDetection ChangeDetectionStrategy.OnPush
selector mev-view-info-dialog
styleUrls ./view-info-dialog.component.scss
templateUrl ./view-info-dialog.component.html

Index

Properties
Methods

Constructor

constructor(dialogRef: MatDialogRef)
Parameters :
Name Type Optional
dialogRef MatDialogRef<ViewInfoDialogComponent> No

Methods

ngOnInit
ngOnInit()
Returns : void
onNoClick
onNoClick()

Function is triggered when user clicks the Close button

Returns : void

Properties

Public dialogRef
Type : MatDialogRef<ViewInfoDialogComponent>
import { Component, OnInit, ChangeDetectionStrategy } from '@angular/core';
import { MatDialogRef } from '@angular/material/dialog';

/**
 * Feature/Observation Information Dialog Component
 *
 * Modal dialog component which is used to view information
 * about custom observation and feature sets
 */
@Component({
  selector: 'mev-view-info-dialog',
  templateUrl: './view-info-dialog.component.html',
  styleUrls: ['./view-info-dialog.component.scss'],
  changeDetection: ChangeDetectionStrategy.OnPush
})
export class ViewInfoDialogComponent implements OnInit {
  constructor(public dialogRef: MatDialogRef<ViewInfoDialogComponent>) {}

  ngOnInit(): void {}

  /**
   * Function is triggered when user clicks the Close button
   *
   */
  onNoClick(): void {
    this.dialogRef.close();
  }
}
<header>Observations and features</header>
<main class="container">
<p>
    Within WebMEV, you will see references to "Observations" and "Features". 
    If you are working with "-omic" data as WebMEV is intended, an observation is a sample and a feature is a gene/transcript. 
    However, we use these more generic terms to allow flexibility in the types of data we work with. 
</p>
<p>
    Observations and features are directly linked. 
    An illustrative example is a count table (or matrix) generated in RNA-seq data. 
    Typically, these matrices are arranged so that each column corresponds to a single sample and each row corresponds to a gene. 
    If we examine a single column of the table, we see that this observation/sample is composed of many gene measurements, which we are calling features; collectively, we can refer to that column as a "feature vector" or "feature array". 
    In many "omic" analyses, we compare these arrays in an attempt to infer biological meaning. 
    For a more general example, we could imagine investigating a population of patients (observations); 
    each patient has some features (e.g. age, sex, smoking history) which may affect the measured outcome variable (e.g. blood pressure).
</p> 
<p>
    Within WebMEV, we can create sets of custom observations/samples and features/genes to allow stratification and comparisons between biologically meaningful groups. 
    These groups may already be known, as in the case of a designed experiment between "control" and "experimental" observations. 
    Alternatively, custom groups may be discovered and defined in the course of an analysis, perhaps originating from a clustering operation. 
    Similarly, we can create a group of genes/features that represent a biologically meaningful pathway. 
    Suggestively, these are referred to as <em>observation sets</em> and <em>feature sets</em>.
</p>   
</main>
<footer mat-dialog-actions class="btn-group">
    <button mat-button (click)="onNoClick()" mat-raised-button color="accent">Close</button>
</footer>

./view-info-dialog.component.scss

* {
  font-size: 14px;
}

header {
  font-weight: bold;
  text-transform: uppercase;
  text-align: center;
  margin-bottom: 15px;
}

.container {
  text-align: justify;
}
Legend
Html element
Component
Html element with directive

result-matching ""

    No results matching ""