Comments (9)
Hi @VaneMorales. Can you please provide example input files and commands you are using? I will take a look at it.
from phyx.
Hi, Many thanks for answering so quickly :) Here I am attaching the command line and the input files when I use pxrlt
pxrlt -t ./ITS/ITS_result.raxml.bestTree -c ./ITS/ITS_numbers_s_otites.txt -n ./ITS/ITS_names_s_otites.txt -o ./ITS/ITS_bestTree_renamed
from phyx.
Ok, I will look at this today. Sorry for the problems.
from phyx.
The problem is it is not matching the names in the file. You can use the verbose option (-v
) to get more information:
$ pxrlt -c ITS_numbers_s_otites.txt -n ITS_names_s_otites.txt -t ITS_result.raxml.bestTree -v
The following names to match were not found in the tree:
EF538363.1
GU818665.1
GU818666.1
GU818667.1
GU818668.1
GU818669.1
GU818670.1
Senecio_otites_V1_ITS_consensus_sequence
Senecio_otites_V2_ITS_consensus_sequence
Senecio_otites_V6_ITS_consensus_sequence
Senecio_otites_V7_ITS_consensus_sequence
(((GU818669.1:0.005328,GU818670.1:0.003992):0.000001,(EF538363.1:0.005434,((Senecio_otites_V7_ITS_consensus_sequence:0.000001,(Senecio_otites_V2_ITS_consensus_sequence:0.002144,Senecio_otites_V03:0.000001):0.002113):0.000001,Senecio_otites_V1_ITS_consensus_sequence:0.000001):0.000001):0.000001):0.000001,(GU818666.1:0.001328,(Senecio_otites_V6_ITS_consensus_sequence:0.000001,GU818665.1:0.00133):0.00133):0.000001,(GU818668.1:0.005327,GU818667.1:0.002661):0.000001);
But those names are in the tree, so I will have to track down what is going wrong with the matching.
from phyx.
Many thanks for looking at this. I was thinking it was because the software added a space after the name when the alignment is exported (*.phy) , but the space does not appear on the tree or in the input files (current and new names of the sequences). It's not about the length of the names used either.
from phyx.
Hey @VaneMorales. Sorry about the delay on this. I have a chunk of time later today when I'll tackle this... or die trying (^_-)≡☆
from phyx.
Sorry for the delay.
It turns out that the problem is that the input files have Windows line Carriage Returns (CR) rather than the expected unix Line Feeds (LF). The result is that all the names to match (except the last one!) each contain a line break in the name, which is why they were not matching.
Ideally we would handle all types of line endings, and hope to at some point, but for now the easiest thing to do is convert your files before running the commands. If you are working on linux you can use the program dos2unix
. On Ubuntu you would install it with:
sudo apt-get install dos2unix
When you are in a directory you can convert all of the files to unix with the command:
dos2unix *
If you want to keep the Windows-formatted files, either be careful where you run the command, or make backups of your files.
Once converted, the files run correctly:
$ pxrlt -c ITS_numbers_s_otites_unix.txt -n ITS_names_s_otites_unix.txt -t ITS_result.raxml.bestTree
(((Senecio_otites_C05:0.005328,Senecio_otites_C06:0.003992):0.000001,(Senecio_otites_Plowman_2627:0.005434,((Senecio_otites_V07:0.000001,(Senecio_otites_V02:0.002144,Senecio_otites_V03:0.000001):0.002113):0.000001,Senecio_otites_V01:0.000001):0.000001):0.000001):0.000001,(Senecio_otites_C02:0.001328,(Senecio_otites_V06:0.000001,Senecio_otites_C01:0.00133):0.00133):0.000001,(Senecio_otites_C04:0.005327,Senecio_otites_C03:0.002661):0.000001);
Sorry for the headache!
from phyx.
Thank god you are not dead!!! I was starting to be worried. Many thanks for looking into this and for pointing the solution to my problem (I have had several issues as I am running these analyses in Ubuntu but I had managed to fix them until now), so I am very grateful for your help :)
from phyx.
(>ᴗ•)
from phyx.
Related Issues (20)
- phylip gets corrupted when piped HOT 3
- a strange thing about pxrms program HOT 10
- pxtlate detects AA when DNA is present HOT 2
- duplicated species in clade groupings with pxbp
- How to install phyx on linux without root access ? HOT 5
- pxrlt and pxrmt doesn't output tip name with "-" correctly HOT 5
- pxaa2cdn -r not working as expected HOT 8
- strange behavior with pxbp on computing cluster HOT 7
- pxcomp outputs an enormous file, or rejects unaligned sequences. HOT 6
- phyx installed HOT 11
- pxaa2cdn -r (again) HOT 10
- infinite loop in superdouble implementation with gcc 13 HOT 3
- Unable to ./configure HOT 4
- Debian 12 install, pxseqgen HOT 3
- autoconf error in installation HOT 5
- pxssplit: command not found HOT 6
- pxrms .txt file using wildcard HOT 6
- Phyx errot: double free or corruption (!prev) HOT 4
- GHA failing for mac (armadillo) HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from phyx.