We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I prepared a sample input folder:
input\ osativa.emx.colnames.txt osativa.emx.npy osativa.emx.rownames.txt osativa.labels.txt
Using the gene-oracle nextflow workflow (with the conda image) I get the following (abbreviated) error:
taskset -c 0-1 phase1-evaluate.py --dataset osativa.labels.txt --labels osativa.emx.colnames.txt osativa.emx.npy osativa.emx.rownames.txt --model-config /home/tyler/.nextflow/assets/systemsgenetics/gene-oracle/example/models.json --model lr --random --random-range $START $STOP $STEP --random-iters 10 --outfile $(printf "%04d" 6).log usage: phase1-evaluate.py [-h] --dataset DATASET --labels LABELS --model-config MODEL_CONFIG [--model MODEL] [--outfile OUTFILE] [--gene-sets GENE_SETS] [--full] [--random] [--random-range START STOP STEP] [--random-iters RANDOM_ITERS] [--n-jobs N_JOBS] [--cv CV] phase1-evaluate.py: error: unrecognized arguments: osativa.emx.npy osativa.emx.rownames.txt
It seems the filenames are not quite getting assigned to their correct place in this instance.
Edit:
Perhaps I need the geneset.txt file. I may have misunderstood what running the pipeline without that file would do.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I prepared a sample input folder:
Using the gene-oracle nextflow workflow (with the conda image) I get the following (abbreviated) error:
It seems the filenames are not quite getting assigned to their correct place in this instance.
Edit:
Perhaps I need the geneset.txt file. I may have misunderstood what running the pipeline without that file would do.
The text was updated successfully, but these errors were encountered: