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

add creation of blast config (assemblies->tracks) #5

Open
scottcain opened this issue Mar 7, 2024 · 3 comments
Open

add creation of blast config (assemblies->tracks) #5

scottcain opened this issue Mar 7, 2024 · 3 comments

Comments

@scottcain
Copy link
Collaborator

For the blast server, it would be good to have a file that gives a two column file (assemblies\tcomma delimited track list). Need to get the list of tracks desired (from @adamjohnwright)

The place to do this list building isn't immediately obvious--it could happen here (which would be after the config.json is created for each assembly) or in website-genome-browsers/jbrowse2, where the list would be created as the config.json is constructed. I'm leading towards the latter (the script that builds config.json already has S3 access built in to it--so it could just put this blast config file somewhere in the s3 bucket when placing the config.json.

@scottcain
Copy link
Collaborator Author

scottcain commented Mar 7, 2024

Looking at https://github.com/alliance-genome/agr_blast_service_configuration/blob/main/conf/WB/databases.WB.WS292.json shows me that the tracks of interest are

          "tracks" : [
               "$ASSEMBLY_curated_genes",
               "$ASSEMBLY_protein_motifs",
               "$ASSEMBLY_classical_alleles"
            ],

@adamjohnwright : Do you have a preference for how these data a presented? I mentioned doing two tab delimited columns but I could also do json if you'd prefer, like:

{
   "bioproject" : "$BIOPROJECT",
    "tracks" : [
               "$ASSEMBLY_curated_genes",
               "$ASSEMBLY_protein_motifs",
               "$ASSEMBLY_classical_alleles"
      ]
}

@adamjohnwright
Copy link
Member

Probably both would work but I lean towards json

@scottcain
Copy link
Collaborator Author

I'm going to suggest adding genblastg_cds_predictions as a track to add as well since the C. elegans Hawaiian strain doesn't have any of the other three tracks.

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

No branches or pull requests

2 participants