-
Notifications
You must be signed in to change notification settings - Fork 51
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
Specify output folder name #11
Comments
AfterQC is designed to run in batch. So, normally AfterQC will create a You can change the name Then the dir tree will be like:
So, your requirement is not to include 'R1.fq' folder inside the report folder, and make the dir tree like:
Am I right? |
Yeah, so the user can specify "report" folder for each pair manually if running in -1 -2 mode, for example. |
I think, that it would be perfect I user can specify some prefix for reports, e.g.
|
@alezanalp do you agree with @serge2016 ? |
I have submitted a commit to implement @serge2016 's idea. You can pull or download the latest master to have a try. Now, you will get
And you can change folder name from |
@sfchen Yes, I agree with @serge2016 . Thank you for the prompt reply. Will try it |
There is one more "issue" or bag with this in v0.9.0:
But if I run
This error occurs if I set the -r dir equal to the dir, where I run AfterQC from. |
@serge2016 this issue is because of v0.9.0 need to create a folder same as the R1 fastq file name, so it will conflict with the fastq file name if I believe with last commit, this issue is gone. |
I just released v0.9.1. You can have a try with the new feature described above. |
Now previous behavior is changed to more predictable:) Thank you! I simply want to use your tool inside CWL environment, and it is easier to do if it is possible to specify output filenames independently from input filenames. |
Is it possible to make option for specifying output folder name with the report files rather than using input files names?
Yours faithfully,
Katerina
The text was updated successfully, but these errors were encountered: