A streamlined workflow and GUI for real-time species identification and pathogen characterization via nanopore sequencing data. Engineered for precision, speed, and user-friendliness, with offline functionality post-initialization.
nanometa-gui and nanometa-backend work on their own. Maybe the default parameter of the path arg in the wrapper needs to somehow point to current folder?
Everything is merged and it seemed to be no problem.
When I install from source, the nanometa-live wrapper does not work:
2023-09-13 14:36:01,141 - INFO - Starting process: nanometa-backend --config config.yaml -p 2023-09-13 14:36:01,141 - INFO - Starting process: nanometa-gui --config config.yaml -p 2023-09-13 14:36:01,258 - INFO - nanometa_live backend started usage: nanometa-backend [-h] [--config CONFIG] [--version] [-p PATH] [--conda-frontend {mamba,conda}] nanometa-backend: error: argument -p/--path: expected one argument usage: nanometa-gui [-h] [--config CONFIG] [--version] [-p PATH] nanometa-gui: error: argument -p/--path: expected one argument ^C2023-09-13 14:36:14,514 - INFO - Terminating processes: <Popen: returncode: None args: 'nanometa-backend --config config.yaml -p '> 2023-09-13 14:36:14,514 - INFO - Terminating processes: <Popen: returncode: None args: 'nanometa-gui --config config.yaml -p '> 2023-09-13 14:36:14,514 - INFO - Processes terminated
nanometa-gui and nanometa-backend work on their own. Maybe the default parameter of the path arg in the wrapper needs to somehow point to current folder?