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

Training data in fasta format? #2

Closed
beef-broccoli opened this issue Oct 23, 2019 · 4 comments
Closed

Training data in fasta format? #2

beef-broccoli opened this issue Oct 23, 2019 · 4 comments

Comments

@beef-broccoli
Copy link

Hello,

Do you guys have the training data in FASTA format? Or is there a way I can convert the provided PSICOV-format data to FASTA? Thank you

Best,
Jason

@shaunmk
Copy link
Member

shaunmk commented Oct 24, 2019

Hi,
The PSICOV-formatted alignments can be converted to FASTA format by just inserting dummy sequence identifiers before each sequence. You can use something like:
awk 'BEGIN {count=1} {printf (">%s_%d\n", "seq", count); print; count++}' target.aln > target.afa

@beef-broccoli
Copy link
Author

Thank you for the reply. Yes dummy sequence identifiers probably work, but it will be much better to have PDB IDs for all the sequences. Is there a list somewhere with all the PDB IDs?

@shaunmk
Copy link
Member

shaunmk commented Oct 25, 2019

We didn't retain the true sequence identifiers for this set. The sequences in each alignment were retrieved from an HHblits database (uniprot20 at the time), so they would be UniProt IDs rather than PDB identifiers.

As for the PDB identifiers for each training example (the source of the query sequence used to make each alignment), these are in their filenames. For example 12asA0 is to be parsed as: PDB ID 12AS, chain A, domain 0.

@beef-broccoli
Copy link
Author

Thanks for the help!

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