Open KaiZhuPhD opened 4 years ago
Error messages from running ./testing/download-neon-data-metadataworkaround.Rmd
:
> source("./code/params.R")
Error in system2("which", args = "cutadapt", stdout = TRUE) :
'"which"' not found
> reorganized_files <- organizeRawSequenceData(fn, meta)
Error in organizeRawSequenceData(fn, meta) :
All sequencer run ID values are NA. Cannot proceed with reorganizing this download batch.
Try a different `fn` or `metadata`.
Also suggest better organized "data" folder.
Error messages from running ./testing/process-16s-sequences-to-seqtabs.Rmd
> source("./code/params.R")
Error in system2("which", args = "cutadapt", stdout = TRUE) :
'"which"' not found
The above error makes loading params.R
failed. Can't proceed with following steps.
Hi Kai,
Thanks for posting about this. It seems like a number of people have had a problem with the which
command via system2
. So I've removed it in the most recent commit. What this does mean, though, is that you will have to find the location of cutadapt
on your own file system, and enter it manually into the CUTADAPT_PATH
argument in params.R
.
Regarding this error:
> reorganized_files <- organizeRawSequenceData(fn, meta)
Error in organizeRawSequenceData(fn, meta) :
All sequencer run ID values are NA. Cannot proceed with reorganizing this download batch.
Try a different `fn` or `metadata`.
Could you please print head(fn)
and head(meta)
?
Also, regarding this:
Also suggest better organized "data" folder.
Which data folder are you referring to? The data
subdirectory shouldn't be relevant in the steps that are being tested.
Suggestions:
cutadapt
folder and fill in the path in params.R
, e.g., https://stackoverflow.com/questions/38291239/using-r-how-do-i-search-for-a-file-folder-on-all-drives-hard-drives-as-well-a
~/../AppData/Roaming/Python/Python39/site-packages/cutadapt
.fastq
files. Or simply, how many files have been downloaded vs. how many in total.
reorganized_files <- organizeRawSequenceData(fn, meta)
takes long time--suggest creating a progress bar.No other issues in ./testing/download-neon-data-metadataworkaround.Rmd
.
In testing process-its-sequences-to-seqtabs.Rmd
, I got the following error message:
trimPrimerITS: No files found at specified location(s) within C:/Users/kai.zhu/Documents/GitHub/NEON_soil_microbe_processing/NEON/raw_sequence/ITS/2_trimmed_mid. Check file path, or post_samplename_pattern argument(s).trimPrimerITS: No files found at specified location(s) within C:/Users/kai.zhu/Documents/GitHub/NEON_soil_microbe_processing/NEON/raw_sequence/ITS/2_trimmed. Check file path, or post_samplename_pattern argument(s).Error in rval[sapply(rval, is.character)] : invalid subscript type 'list'
Hi Kai,
> reorganized_files <- organizeRawSequenceData(fn, meta)
Error in organizeRawSequenceData(fn, meta) :
All sequencer run ID values are NA. Cannot proceed with reorganizing this download batch.
Try a different `fn` or `metadata`.
trimPrimerITS: No files found at specified location(s) within C:/Users/kai.zhu/Documents/GitHub/NEON_soil_microbe_processing/NEON/raw_sequence/ITS/2_trimmed_mid. Check file path, or post_samplename_pattern argument(s).trimPrimerITS: No files found at specified location(s) within C:/Users/kai.zhu/Documents/GitHub/NEON_soil_microbe_processing/NEON/raw_sequence/ITS/2_trimmed. Check file path, or post_samplename_pattern argument(s).Error in rval[sapply(rval, is.character)] : invalid subscript type 'list'
The most likely cause of this, I think, is that your R session wasn't able to find cutadapt
. Are you able to check the error logs to see if this error was preceded by "error in running commandsh: ~/.local/bin/cutadapt: No such file or directory"? (If so, you will need to update CUTADAPT_PATH
in params.R
.)
The main barrier to using Windows computers to run the processing pipeline was the lack of support for Cutadapt. This is only relevant for the ITS pipeline, and this may be addressed by the Docker container that @rbartelme will soon add to the repo.
I'm leaving this issue open in case any Windows users want to confirm that either (1) the 16S pipeline still works for them, or (2) the Docker container works for them.