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

"invalid integer: everything" when trying to run BamToCov #10

Closed
leone93 opened this issue May 26, 2022 · 3 comments
Closed

"invalid integer: everything" when trying to run BamToCov #10

leone93 opened this issue May 26, 2022 · 3 comments
Labels
question Further information is requested

Comments

@leone93
Copy link

leone93 commented May 26, 2022

Hi guys I'm trying to use your tool but every option I try to put return this error. invalid integer: "everything"
I'm using the latest versione 2.7 isntalled with Conda.

First I tried with: bamtocov -w -o -T 24 sorted.bam > coverage.wig
and the error was invalid integer: -o
then I removed -o and I have the error invalid integer: -T
then I tried to write --threads instead of -T and invalid integer: --threads
then I left only the -w and the error was invalid integer: sorted.bam

So after some bestemmie I left only the basic command bamtocov sorted.bam > coverage.bed and it works.
Is it a common issue for you?

@telatin
Copy link
Owner

telatin commented May 26, 2022

Dear @leone93
thanks for sharing your experience.

Regarding your first attempt, the -w and -o flags are not a switch, but arguments requiring something. See the docs:

-w, --wig <SPAN>  
-o, --report <TXT>   

So try:

bamtocov -w 250 -o report.txt -T 24 sorted.bam > coverage.wig

@telatin telatin changed the title invalid integer: everything [BUG] "invalid integer: everything" when trying to run BamToCov May 26, 2022
@leone93
Copy link
Author

leone93 commented May 30, 2022

Hi @telatin in this ways work, thanks!
Do you know which is the best span value to select? Is 250 based on your experience?

@telatin
Copy link
Owner

telatin commented May 30, 2022

The window selections is based on the actual protocol, the goal and resolution needed. For some applications you might want a very high resolution, at the expense of a large file, in other circumstances you can opt for a large window to have a blurred representation of the coverage.

(The default output of BamToCov is “bedGraph”, that gives the highest resolution needed with the lowest redundancy, but sometimes a Wiggle file can be easier to parse…)

@telatin telatin added the question Further information is requested label Jun 1, 2022
@telatin telatin closed this as completed Jun 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants