+
+ Some fields were autopopulated based on the selected experiment and should be inspected to ensure they
+ are still relevant to this score set.
+
+
+
+
+
+
+
+ Examples: CBS low-B6 imputed and refined, NUDT15 protein stability assay, Arrestin-1 binding,
+ SpCas9 positive selection
+
+
+
+
+
+
+
+ {{ validationErrors.title }}
+
+
+
+
+
+
+ Example: A Deep Mutational Scan of the human cystathionine-beta-synthase (CBS) using functional
+ complementation in yeast via DMS-TileSeq at low levels of Vitamin B6.
+
+ May be formatted using Markdown.
+ It is common for a score set to have the same abstract text as the experiment that it belongs to.
+ The focus should be on the MAVE data, rather than the full research contribution, so use your judgement
+ when deciding what details are relevant.
+
+ For more on data licensing in MaveDB, see the
+ documentation.
+
+
+
+
+
+
+
+
+ Choosing a license with these restrictions may cause your score set to be excluded from data federation
+ and aggregation by MaveDB collaborators.
+
+
+
+
+
+
+
+ This may assert, for example, the original author's right to publish the data first.
+
+ Example searches: https://doi.org/10.1038/s41467-023-43041-4 (DOI as link), 10.1038/s41467-023-43041-4 (DOI),
+ 38057330 (a Pubmed ID), 2022.06.10.22276179 (a bioRxiv or medRxiv ID)
+
+
+ When defining variants against multiple targets, uploaded variant coordinates should be fully
+ qualified with respect to target names or target accessions.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
{{ formatInt(item.numVariants) }} variants are included in this score set.
+
To replace the variants, choose a new scores file and optional counts file:
+
+
+ Load a scores file and an optional counts file:
+
-
- Choosing a license with these restrictions may cause your dataset to be excluded from data federation
- and aggregation by MaveDB collaborators.
-
-
+
+ Choosing a license with these restrictions may cause your dataset to be excluded from data federation
+ and aggregation by MaveDB collaborators.
+
+
-
- When defining variants against multiple targets, uploaded variant coordinates should be fully
- qualified with respect to target names or target accessions.
-
-
-
-
-
- Variant scores
-
-
-
{{ formatInt(item.numVariants) }} variants are included in this score set.
-
To replace the variants, choose a new scores file and optional counts file:
-
-
- Load a scores file and an optional counts file:
-
+
+ When defining variants against multiple targets, uploaded variant coordinates should be fully
+ qualified with respect to target names or target accessions.
+
+
+
+
+
+ Variant scores
+
+
+
{{ formatInt(item.numVariants) }} variants are included in this score set.
+
To replace the variants, choose a new scores file and optional counts file:
+
+
+ Load a scores file and an optional counts file:
+