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

phylogenetic: Use inline root sequence #25

Merged
merged 1 commit into from
Apr 16, 2024
Merged

phylogenetic: Use inline root sequence #25

merged 1 commit into from
Apr 16, 2024

Commits on Apr 16, 2024

  1. phylogenetic: Use inline root sequence

    Based on feedback from @jameshadfield in
    nextstrain/zika#56 (comment)
    
    Looking at the existing dataset files on S3,
    the 8 KiB root-sequence.json is pretty negligible when the main
    Auspice JSON is only 163 KiB. Nextstrain datasets are limited by the
    500MB memory cap in Chrome,¹ so we'd be fine adding the
    root sequence inline.
    
    This ensures that our uploads will include the root sequence so that
    they don't get out-of-sync with the main Auspice JSON.
    
    ¹ nextstrain/auspice#1622
    joverlee521 committed Apr 16, 2024
    Configuration menu
    Copy the full SHA
    a9b3033 View commit details
    Browse the repository at this point in the history