Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nextclade v3 Support #139

Merged
merged 6 commits into from
Jan 26, 2024
Merged

Nextclade v3 Support #139

merged 6 commits into from
Jan 26, 2024

Conversation

jaleezyy
Copy link
Owner

@jaleezyy jaleezyy commented Jan 25, 2024

In response to error noted in #138 :

  • Added support for Nextclade v3 and associated datasets
  • Backwards compatibility maintained between v3 and v2 in both software and datasets
  • Includes fix where Nextclade version, when specified, would not update as requested
  • General performance update allowing mamba to be used when updating lineage assignment software
  • Cleaned up config.yaml for Nextclade parameters to be clearer (reflected in signalexe.py --config-only)
  • Updated dependencies for SIGNAL postprocessing

@jaleezyy jaleezyy marked this pull request as draft January 25, 2024 23:41
@jaleezyy jaleezyy self-assigned this Jan 25, 2024
@jaleezyy jaleezyy marked this pull request as ready for review January 26, 2024 04:20
@jaleezyy jaleezyy merged commit 2106195 into master Jan 26, 2024
1 check passed
@jaleezyy jaleezyy deleted the nextclade3 branch February 1, 2024 16:22
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.

1 participant