-
Notifications
You must be signed in to change notification settings - Fork 1
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
Pipecraft v.1.0.0 NextITS workflow does not work: There's no process matching config selector #8
Comments
Hello Sam, Could you please provide more information about how you formatted your input files?
If you have multiple runs, it is important to use a consistent naming convention for the samples, like For the chimera removal step, please make sure to use the database in UDB format. The UNITE database in UDB format can be downloaded from here: UNITE database UDB format. While running the pipeline, you may encounter some We acknowledge that the documentation for the NextITS part is lacking at this point, and we are working on updating it to provide clearer guidance. We appreciate your patience and hope to resolve any confusion as soon as possible. If you have any further questions or require additional assistance, please don't hesitate to let us know. |
Hi Vlad, Thank you for the detailed instructions. Do the files need to be zipped? I have just one run, and input files look like this: Sample1.fastq Kind regards, |
You may use uncompressed files as well ( |
Ok great, good to know. If I understand the new features correctly, I should not include the |
I restructured my
but I still get the same error message. I tried both with zipped and unzipped fastq files. Any idea what else might be causing this? My sample names do contain single underscores, but I guess this should be fine and is why you use double underscores to link Run and Sample ID? |
That's an interesting question. So I would rather keep the 'unknown' sample and let it pass all pipeline steps. At the end, you may just remove it from the output table.
Which working directory do you specify in PipeCraft (the directory one level above the |
I missed that I actually need to create a directory called I included the 'unknown' sample, will report back once I have the results |
Is the tag-jumping also a concern if you only used 1 PCR step? We have a large primer-set where multiplexing indices/barcodes are already preattached to the primers (we order them with the indices/barcodes already in the primer sequences), so per sample we use a slightly different version of the primer (different index/barcode). After PCR we do a PCR-free library preparation step. I'm not entirely sure but this might reduce the chances of tag-jumping? |
Hi, I got the same issue that it gives error at the second step: I have a folder my_dir_ITS/ I selected as Workfolder, then the Input/ folder inside of it, then the Run1/ folder including demultiplexed PacBio ITS (single-end) amplicons *.fq inside of Run1/. Many thanks in advance! |
Hi! It seems that no reads were passing the primer check, i.e., none of your input sequences contained the specified primer strings. Please double-check your specified primers in the "STEP_1" and try re-running the pipe. |
Hi, Anslan, thanks for your reply. I double checked my primer with my fasta, they are matched. I put CTTGGTCATTTAGAGGAAGTAA as primer forward and TCCTCCGCTTATTGATATGC as primer reverse.
|
@Linlin-Xu , could you please show a log file for one of the samples? To do this, follow these steps:
In this example,
Please post the content of this log here. |
Hi, thank you very much for your help. The .command.log file for sample 1 is as below: `Input file: sample1.fq.gz Counting primers Looking for multiple primer occurrences Number of artefacts found: 28 Reorienting sequences === Summary === Total reads processed: 7,196 == Read fate breakdown == Total basepairs processed: 4,400,162 bp === Adapter 1 === Sequence: GTACACACCGCCCGTCG...GCATATHANTAAGSGSAGG; Type: linked; Length: 17+19; 5' trimmed: 0 times; 3' trimmed: 0 times; Reverse-complemented: 0 times All done Removing empty files |
From the log file, I see that primers are misspecified. |
Many thanks for your help, I did put CTTGGTCATTTAGAGGAAGTAA as primer forward and TCCTCCGCTTATTGATATGC as primer reverse in the pipecraft2 STEP_1. So, I'm confused. I just also checked the pipecraft2_last_run_configuration.json file. The primer was still correct in it.
|
Thanks for reporting this issue - we need to investigate it more thoroughly. |
Hi @Linlin-Xu, |
Thank you, I did only put in a single primer in Pipecraft v1.0.0. When I try with the NextITS alone, the Step1 stopped after pass the disambiguate step: |
@Linlin-Xu , could you please check the log file ( |
Thank you very much for your reply, it works with docker! |
Thanks. I think that input data (fastq) could be misspecified. |
Hi, thanks for your answer, I found I put all fastqs as input, should only put directory. I'm at the last step of Step1, but have error: I downloaded the R package in all my local Rs, but doesn't work. |
Please try to run NextITS with Docker or Singularity container engines enabled (add |
Hi, thanks for your reply. It works with docker. |
Thank you @slambrechts and @Linlin-Xu for shedding light on this issue, further investigation revealed that there was a coding error in the Linux release which led to improper primer passing to the NextITS workflow. The bug has been fixed and a new Linux installer has been uploaded for the 1.0.0 release (https://github.com/pipecraft2/pipecraft/releases/download/v1.0.0/pipecraft_1.0.0.deb). We were unable to reproduce this error on the Windows platform and thus we believe NextITS is working as intended on Windows. |
Hi,
When trying the Pipecraft v.1.0.0 NextITS workflow I get the following error messages:
It seems like Pipecraft does not recognize the processes that are defined in the full Pipecraft NextITS workflow, it runs like no processes or tools have been selected?
In any case, I selected my work directory containing demultiplexed PacBio ITS (single-end) amplicons (which have been demultiplexed using the previous version of pipecraft2 (v.0.1.4) using the
SELECT WORKDIR
button, after which I selected the NextITS pipeline using theSELECT PIPELINE
button in the top left corner. I only edited the reverse primer because it was missing the first two bases, and selected the UNITE_9_1_beta.fasta file as the chimera database for reference based chimera filtering. Other than that I did not change any of the other default parameters.The text was updated successfully, but these errors were encountered: