You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having issues while starting zUMIs. I downloaded the PBMC data from the Smartseq3Express paper (https://www.nature.com/articles/s41587-022-01311-4) to test the zUMIs pipeline. I demultiplexed the files using the zUMIs demultiplex function. Afterwards I created the yaml file for the reads and indexes. However, when trying to run zUMIs I encounter the following error: "Using miniconda environment for zUMIs! note: internal executables will be used instead of those specified in the YAML file! YAML file has an error. Look at the zUMIs_YAMLerror.log or contact developers.". When I open the error.log file I get the following output: "1". Do you know what is wrong with my YAML file that could cause this error?
For zUMIs to work, you dont necessarily need to demultiplex the files first (and then merge them again) .
Other than that, try to modify as follows:
In file 3, you miss the key base_definition:
If I remember correctly, the random generated barcodes when merging previously demultiplexed fastq are 8 bp, so try BC(1-8)
Hi,
I'm having issues while starting zUMIs. I downloaded the PBMC data from the Smartseq3Express paper (https://www.nature.com/articles/s41587-022-01311-4) to test the zUMIs pipeline. I demultiplexed the files using the zUMIs demultiplex function. Afterwards I created the yaml file for the reads and indexes. However, when trying to run zUMIs I encounter the following error: "Using miniconda environment for zUMIs! note: internal executables will be used instead of those specified in the YAML file! YAML file has an error. Look at the zUMIs_YAMLerror.log or contact developers.". When I open the error.log file I get the following output: "1". Do you know what is wrong with my YAML file that could cause this error?
Thank you in advance!
Kind regards,
Thomas
SS3_test_zUMIs.txt
The text was updated successfully, but these errors were encountered: