-
Notifications
You must be signed in to change notification settings - Fork 24
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
The problems encountered when using the command “smudgeplot.py all” #184
Comments
Hi @liuweiming1 , some of the images you intended to upload are not there... would you like to try that again? How does you It is hard to debug without these details. |
Sure, here is the error message: ![]() And here is the screenshot of the .smu file: ![]() |
Here is also a screenshot of the trial_run_smudgeplot.pdf: ![]() |
Hi @liuweiming1, I see what's probably happening here. I think you just simply don't have an adequate sequencing depth. Did you make a k-mer histogram too? You should plot it and figure out if you see distinct peaks. |
I updated https://github.com/KamilSJaron/smudgeplot/wiki/everything-about-input-data with the information about needed coverage and what patterns to expect when not met.... |
![]() |
Hi @liuweiming1 I am always happy to help, but you got to give me more than this...
|
I encountered some issues after using the command “smudgeplot.py all -o ./trial_run ./kmerpairs_text.smu -ylim 70”.
Why did this problem occur?
And some of the files generated in this step are problematic.
trial_run_smudge.sizes.txt
is an empty file. And the filetrial_run_smudgeplot.pdf
opens to look like the following image.So I reduced the value of the L parameter in the previous step:
smudgeplot.py hetmers -L 5 -t 4 -o ./data/kmerpairs --verbose ./data/Scer.ktab
.After I reduced the value of the L parameter in the previous step, I continued to use the command
smudgeplot.py all -o ./trial_run ./kmerpairs_text.smu -ylim 70
, but the same error still occurredSo what should I do now?
The text was updated successfully, but these errors were encountered: