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

Why do you need your own copy of the reference genome? #3

Open
CreRecombinase opened this issue Jul 17, 2020 · 1 comment
Open

Why do you need your own copy of the reference genome? #3

CreRecombinase opened this issue Jul 17, 2020 · 1 comment

Comments

@CreRecombinase
Copy link

Hi, this is a nice piece of software. I was wondering if it would be possible to let the user control where the input data was coming from, instead of just using the ~/.motifscan directory. I already have several copies of hg19 scattered across my machine and it would be great if I didn't have to have to keep an (uncompressed) copy of the reference genome for every bioinformatics tool that I use.

Thanks again!

@hongduosun
Copy link
Member

hongduosun commented Jul 19, 2020

Hi, in the very earlier versions, MotifScan does provide command line parameters for users to specify the path of reference genome file, gene annotation file, motif matrix file... Some users were confused (some people use compressed but others may not, some use one single fasta file but some may prefer one fasta file for one chomosome) and complained about typing these whole paths repeatedly. So MotiScan now put all these files under ~/.motifscan by default and uses a config file ~/.motifscanrc to remember the paths.
But you don't have to put the reference genome under ~/.motifscan. You can move it to any location or merge the contents with an existing copy and then config the path in ~/.motifscanrc
Another workaround is to make a hardlink for the fasta file and this would cost no extra disk usage.
Hope it helps!

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

2 participants