{
"data_tables": {
"bowtie2_indexes": [
{
"dbkey": "phiX174",
"name": "phiX174",
"path": "phiX174",
"value": "phiX174"
}
],
"tophat2_indexes": [
{
"dbkey": "phiX174",
"name": "phiX174",
"path": "phiX174",
"value": "phiX174"
}
]
}
}so here you’d add additional items in the inntermost array
{
"data_tables": {
"bowtie2_indexes": [
{
"dbkey": "phiX174",
"name": "phiX174",
"path": "phiX174",
"value": "phiX174"
},
{
"dbkey": "phiX175",
"name": "phiX175",
"path": "phiX175",
"value": "phiX175"
},
],
}
}
--skip_client_build
<options from_data_table...> documented somewhere?
sort_by does not have an order attribute... pity... because I'd really like to specify descending order...
/opt/conda/bin/conda create -y --quiet --override-channels --channel conda-forge --channel bioconda --channel iuc --channel defaults --channel R --name mulled-v1-5b73db27209dd7e83d26bd4dedeadbcf356c9297c08644dec23df66a734a236c python=2.7 scipy matplotlib Pillow reportlab tk ConfigParser) succeed on the command line ?
conda_exec
conda_auto_init
/opt/conda
nextclade which has a bunch of optional file inputs (e.g. --input-qc-config). If I make these visible as <param type="data" optional="true"> it seems they are assigned an input even if the chooser shows "Nothing selected". Is there a way to have optional dataset inputs without guarding each one in a <conditional> to activate / deactive it?
If I make these visible as <param type="data" optional="true"> it seems they are assigned an input even if the chooser shows "Nothing selected".
This should be totally fine.
input-qc-config is type JSON input... it picks up a JSON from the history and adds that to the command line
conda_prefix: /home/galaxy/.conda
conda_exec: /opt/conda/bin/conda (I have a symbolic link: ln -s /opt/conda/bin /home/galaxy/.conda/)you should just set conda_prefix to /opt/conda/
conda_exec too please