> For the complete documentation index, see [llms.txt](https://bandla-chai.gitbook.io/facets-preview/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bandla-chai.gitbook.io/facets-preview/reviewing-fits.md).

# Reviewing fits

## 1. Loading facets runs

There two ways to load fits into facets-preview. The first is "repo" mode where samples are input through a manifest file. This file contains at least three columns (and up to four). See[ manifest file requirements](/facets-preview/input-requirements.md#1-manifest-file). Second option is "sample" mode which simply accepts one or more sample-level facets output directories.

![](/files/-M1SHiNfabTj6zIja9cg)

## 2. Samples manifest

The samples manifest page gives a high-level overview of the QC status of the `default` fit as well as that of the reviewed fit (if it exists). 

![](/files/-M1SHmhALLWuJ74lAdEl)

## 3. Review fits

### *3.1 Submit refits*

* Refits require the watcher to be running. See [instructions for setting up watcher](/facets-preview/installation2.md#5-setup-refit-watcher). If there is a "red cross" it means the watcher is not running. 
* Pre-filled options for all the refit parameters are from the `default` fit (if there is no `default` fit, then options used to generate any of the fits are used). Note: the compatible facets versions can be configured in the [config file](/facets-preview/installation2.md#4-configuration-file).
* Note: It takes a few mins to generate the refits. Simply, go to the "Samples Manifest" page and click on the sample again to reload with newly generated fits.

![](/files/-M1SG4XM79IraWS4a1CS)

### *3.2  QC Summary*

The QC for each fit is generated by an `facets_qc.R` script in the `facets-preview` package ([https://github.com/taylor-lab/facets-preview/tree/master/facets\_qc/](https://github.com/taylor-lab/facets-preview/tree/version_2_preRelease/facets_qc/)) that is independently version tracked. The purpose is to enable faster evolution of the QC criteria. For more information on QC criteria, see [FACETS QC criteria](/facets-preview/facets-qc-criteria.md) section.

The "QC metrics" are simply the aggregation of `facetsSuite::check_fit` metrics as well as the `facets_qc` flags. All columns are also accessible in the sample-level `facets_qc.txt` file.

![](/files/-M1SICW02cQPT4h2U5lq)

### *3.3 Close Up*

![](/files/-M1SIYC9g9jDdajODjIx)

### *3.4 Segments*

Unedited segment output of the facets algoirthm

![](/files/-M1SLWqfcFDcGUp3ekR0)

### *3.5 Segments (editable)*

Same data as in 3.4 but allows editing the cncf.txt file. Useful for correcting TCN/LCN values for certain segments.

![](/files/-M1SL_YfkWDzJWjv1oFU)

### *3.6 Review notes*

`facets-preview` enables annotating samples at multiple levels.

* "Acceptable fit" and "Best fit" differ only by subjective assessment of analyst in degree of confidence in the fit. Currently, no distinction is made between the two in calculating [genomic annotations](/facets-preview/generate-ccfs-gene-level-calls.md#2-through-facets-preview). Therefore, it is up to the analyst to take this distinction in consideration in the downstream analysis.
* "Use purity run for CCF annotation". In some cases, a `hisens` run is undesirable (eg: too high fragmentation, etc) and a `purity` run is preferable for CCF calculations.
* "Use purity". In cases where purity is NA/0.3, this allows analyst to enter a purity value estimated from mutations (for example, MSI tumors are flat and therefore yield a purity of NA).
* **Note: In case of multiple manual reviews, the one that is most recent is used for genomic annotations.**

![](/files/-M1SLd-z1FM-f49lnnL6)