Skip to content

fix(nextclade): correct excessBandwidth typo#52

Merged
rneher merged 1 commit intomainfrom
fix/nextclade-excess-bandwidth-typo
Mar 5, 2026
Merged

fix(nextclade): correct excessBandwidth typo#52
rneher merged 1 commit intomainfrom
fix/nextclade-excess-bandwidth-typo

Conversation

@ivan-aksamentov
Copy link
Copy Markdown
Member

@ivan-aksamentov ivan-aksamentov commented Mar 5, 2026

Fix typo excessBandwith (missing "d") to excessBandwidth in nextclade/defaults/nextclade-dataset/pathogen.json.

The misspelled key is silently ignored by Nextclade, causing the default value (9) to be used instead of the intended value (18). This affects alignment quality for divergent E1 sequences by using a narrower band than intended.

  • Fix excessBandwith -> excessBandwidth

⚠️ The existing dataset in nextclade_data is already patched in nextstrain/nextclade_data#423, so no immediate resubmission is needed. But without this upstream fix, the typo will reappear on the next dataset submission from this workflow.

ℹ️ See pathogen.json schema (AlignPairwiseParamsOptional definition) for the full list of recognized alignment parameters.

  1. Related to: fix(nextstrain/rubella/E1): correct excessBandwidth typo nextclade_data#423

@rneher rneher merged commit 2d06e5d into main Mar 5, 2026
6 checks passed
@rneher rneher deleted the fix/nextclade-excess-bandwidth-typo branch March 5, 2026 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants