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

Paralogs added have the exact same name as ortholog #111

Closed
matiasWanntorp opened this issue Jan 8, 2024 · 5 comments
Closed

Paralogs added have the exact same name as ortholog #111

matiasWanntorp opened this issue Jan 8, 2024 · 5 comments

Comments

@matiasWanntorp
Copy link

matiasWanntorp commented Jan 8, 2024

Hello!

I've used "working_dataset_constructor.py" and have all of the multifastas with ortholog, paralogs plus the newly extracted sequences. I noticed that the paralog sequences in my .fas files have identical names to the corresponding ortholog sequences. I wondered whether this is intended or if perhaps something is wrong with my database (custom) or metadata?

Thank you ahead for any insight!

Edit: After looking at the "build_database.py" it seems like the paralogs should be renamed by adding ".." + a random 5 digit number however this doesn't seem to have happened when constructing the database. At least this is my interpretation of the function "paralog_name(abbrev, keys)" in "build_database.py". Could I perhaps do this post database construction and pre "working_dataset_constructor.py"?

@atice
Copy link
Collaborator

atice commented Jan 8, 2024

HI @matiasWanntorp ,

You are correct that build_database.py should add .." + a random 5 digit number to each sequence header in the paralog files you provide initially. Can you send me an example header or two from your initial fasta file of paralogs?

Alex

@matiasWanntorp
Copy link
Author

matiasWanntorp commented Jan 8, 2024

Yes of course!

Screenshot 2024-01-08 at 22 15 18

@atice
Copy link
Collaborator

atice commented Jan 8, 2024

Thanks. We will look into this and get back to you as soon as possible if we need to know anything else to trouble shoot or with debugged code if that is the case.

@matiasWanntorp
Copy link
Author

Okay, thank you!

@robert-ervin-jones
Copy link
Member

Hi @matiasWanntorp,

Sorry for just now getting back to you. We are beginning to work on PhyloFisher v2. In the newer version, this will be handled, but for the time being I am going to close this issue.

Thanks for using PhyloFisher!

Best,
Robert

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

3 participants