-
Notifications
You must be signed in to change notification settings - Fork 38
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
Failure to plot secondary clustering plots #202
Comments
Hi Eric, Intersting. I think this bug has to do with an incompatibility with those plots and "run_tertiary_clustering". To be sure, would you mind uploading the Cdb.csv file from the run that failed to make the plot? Best, |
Hi Matt, Best, |
OK- it is definitely the case that the tertiary_clustering is causing this problem. I will fix it in the next dRep update. If you'd like to make the plots now, a hack to do this would be to edit Cdb.csv and rename all secondary clusters with points in them (e.g. 2_19.21) to remove the points (e.g. 2_1921). Thanks for bringing this to my attention! MO |
Thanks for the help Matt! I would like to make the plots but I don't understand how. If I edit the Cdb.csv and run:
It overwrites the file again and the points are already there. Am I missing something? Is there an option to just make the plots? Thanks! Eric |
My apologies Eric! In pervious versions of dRep it was possible to run the plots on already-completed data. I forgot that I removed that functionality a few updates ago. For now, the only way to make these plots is to remove the Sorry about the hacky solution while I work on a real update -MO |
Thanks Matt! Don't worry, the hacky solution is fine. Also the |
Dear developers,
When I run
dRep
with the-nc
parameter set to0.6
, the program generates most output correctly but the PDF files of the secondary clustering dendrograms and MDS cannot be opened. In the log file it says:The exact command is:
Strangely, when I set the parameter to 0.5 (or leave it at the default value), all plots are correctly generated. Could this be a bug? Or am I missing something?
I am running dRep version 3.4.3 on Ubuntu 18.04.
Thanks in advance!
Eric
The text was updated successfully, but these errors were encountered: