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

Separate out state-specific subsampling #20

Closed
j23414 opened this issue Oct 8, 2024 · 1 comment · Fixed by #30
Closed

Separate out state-specific subsampling #20

j23414 opened this issue Oct 8, 2024 · 1 comment · Fixed by #30
Assignees
Labels
enhancement New feature or request

Comments

@j23414
Copy link
Collaborator

j23414 commented Oct 8, 2024

Context

Separate out Washington-specific subsampling into a separate config

Description

Ideally the default build will be a global view of WNV, and focused builds (e.g. state specific subsampling) have more fine tuned subsampling in separate config files.

Examples

# Global build
nextstrain build ingest
nextstrain build phylogenetic

# WA specific builds
nextstrain build ingest --configfile wa-specific-config.yaml
nextstrain build phylogenetic --configfile wa-specific-config.yaml

Possible solution

Possible places to put the focused build configs based on prior art:

@j23414
Copy link
Collaborator Author

j23414 commented Oct 18, 2024

After chatting with @DOH-LMT2303 about automating global and WA public facing trees, we're leaning towards the mpox style:

defaults/
  |_ global/
  | |_ auspice_config.json
  | |_ reference.gb
  | |_ include.txt
  |_ WA/
    |_ auspice_config.json
    |_ reference.gb
    |_ include.txt

Not necessarily as part of #30, since we may need to discuss some more design decisions and can reorganize the files in later PR(s).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants