# Inferring pathogen.json from a nextclade.tsv results

**URL:** <https://nextstrain.discourse.group/t/inferring-pathogen-json-from-a-nextclade-tsv-results/1611>\
**Category:** Uncategorized\
**Created:** [April 16, 2024, 2:54pm UTC](https://nextstrain.discourse.group/t/inferring-pathogen-json-from-a-nextclade-tsv-results/1611 "2024-04-16T14:54:38Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![quietjen](https://yyz1.discourse-cdn.com/flex031/user_avatar/nextstrain.discourse.group/quietjen/32/713_2.png) [@quietjen](https://nextstrain.discourse.group/u/quietjen)\
**Post date:** [April 16, 2024, 2:54pm UTC](https://nextstrain.discourse.group/t/inferring-pathogen-json-from-a-nextclade-tsv-results/1611/1 "2024-04-16T14:54:38Z")

</div>

Posting for discussion:

While creating a Nextclade dataset, had wondered if there’s a method to [fine-tune reasonable attribute cutoffs in the pathogen.json](https://github.com/nextstrain/nextclade_data/blob/master/docs/dataset-creation-guide.md#preparing-a-minimal-pathogenjson-config-file-and-accompanying-files) file based on the [nextclade.tsv QC columns](https://docs.nextstrain.org/projects/nextclade/en/latest/user/algorithm/07-quality-control.html). Non-urgent question, just thinking.
