-
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
IndexError: list index out of range #40
Comments
Hi, thank you for reporting this. So, by default, ScanNeo2 will use the configuration file located at config/config.yml. I will cause this error when it hasn't been configured: Line 16 in 8812753
Alternatively you can also set the path via --configfile Could you set up your configfile and try it again? I will look into it how to exit ScanNeo2 more gracefully when it hasn't been configured... thanks |
Thanks for your reply! I believe I have successfully installed the ScanNeo2. However, when I followed the test config to set it up and run it, I encountered the following error: My ../config/config.yaml is like: ReferenceGeneral settingsreference: data: custom: My Snakefile is like: set minimum snakemake versionmin_version("8.0.0") setupconfigfile: "../config/config.yaml" rule all: load rulesinclude: "rules/prelim.smk" Could you please advise me on how to resolve this issue? I greatly appreciate your assistance and look forward to your response. |
Hi there, thank you for your reply. So, in principle, you have to call it with the
Have you included this option? This should get you started and you should see how the environments are getting downloaded. Just to be sure.. can you please check if the workflow runs when using some of the testconfigurations. Like this:
This should then generate an output in the |
You should also see how different rules are being executed:
|
Hi, when I install ScanNeo2 using: snakemake --cores all --software-deployment-method conda
I got this error:
<path/to/reads> is not a valid file
Traceback (most recent call last):
File "/hsfscqjf1/ST_CQ/P23Z32300N0005/software/miniconda3/envs/scanneo2/lib/python3.12/site-packages/snakemake/cli.py", line 1898, in args_to_api
dag_api = workflow_api.dag(
^^^^^^^^^^^^^^^^^
File "/hsfscqjf1/ST_CQ/P23Z32300N0005/software/miniconda3/envs/scanneo2/lib/python3.12/site-packages/snakemake/api.py", line 326, in dag
return DAGApi(
^^^^^^^
File "", line 6, in init
File "/hsfscqjf1/ST_CQ/P23Z32300N0005/software/miniconda3/envs/scanneo2/lib/python3.12/site-packages/snakemake/api.py", line 436, in post_init
self.workflow_api._workflow.dag_settings = self.dag_settings
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/hsfscqjf1/ST_CQ/P23Z32300N0005/software/miniconda3/envs/scanneo2/lib/python3.12/site-packages/snakemake/api.py", line 383, in _workflow
workflow.include(
File "/hsfscqjf1/ST_CQ/P23Z32300N0005/software/miniconda3/envs/scanneo2/lib/python3.12/site-packages/snakemake/workflow.py", line 1382, in include
exec(compile(code, snakefile.get_path_or_uri(), "exec"), self.globals)
File "/hsfscqjf1/ST_CQ/P23Z32300N0005/software/miniconda3/envs/scanneo2/soft/ScanNeo2/workflow/Snakefile", line 30, in
File "/hsfscqjf1/ST_CQ/P23Z32300N0005/software/miniconda3/envs/scanneo2/lib/python3.12/site-packages/snakemake/workflow.py", line 1382, in include
exec(compile(code, snakefile.get_path_or_uri(), "exec"), self.globals)
File "/hsfscqjf1/ST_CQ/P23Z32300N0005/software/miniconda3/envs/scanneo2/soft/ScanNeo2/workflow/rules/common.smk", line 126, in
config['data'] = data_structure(config['data'])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/hsfscqjf1/ST_CQ/P23Z32300N0005/software/miniconda3/envs/scanneo2/soft/ScanNeo2/workflow/rules/common.smk", line 8, in data_structure
config['data']['dnaseq'], filetype, readtype = handle_seqfiles(config['data']['dnaseq'])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/hsfscqjf1/ST_CQ/P23Z32300N0005/software/miniconda3/envs/scanneo2/soft/ScanNeo2/workflow/rules/common.smk", line 64, in handle_seqfiles
return mod_seqdata, filetype[0], readtype[0]
^^^^^^^^^^^^^^
IndexError: list index out of range
How can I solve this problem?
The text was updated successfully, but these errors were encountered: