-
Notifications
You must be signed in to change notification settings - Fork 441
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
Normalize paths for genome fetch and some of the genome indexer data managers, plus additional moderinzation #6489
Changes from all commits
79d1f68
51a8277
df4acc3
1b57490
027ce9f
de1f26a
bd4a775
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
This file was deleted.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,6 +1,5 @@ | ||
<?xml version="1.0"?> | ||
<data_managers> | ||
|
||
<data_manager tool_file="data_manager/bowtie2_index_builder.xml" id="bowtie2_index_builder"> | ||
<data_table name="bowtie2_indexes"> | ||
<output> | ||
|
@@ -10,9 +9,9 @@ | |
<column name="path" output_ref="out_file" > | ||
<move type="directory" relativize_symlinks="True"> | ||
<!-- <source>${path}</source>--> <!-- out_file.extra_files_path is used as base by default --> <!-- if no source, eg for type=directory, then refers to base --> | ||
<target base="${GALAXY_DATA_MANAGER_DATA_PATH}">${dbkey}/bowtie2_index/${value}</target> | ||
<target base="${GALAXY_DATA_MANAGER_DATA_PATH}">genomes/${dbkey}/bowtie_index/v2/${value}</target> | ||
</move> | ||
<value_translation>${GALAXY_DATA_MANAGER_DATA_PATH}/${dbkey}/bowtie2_index/${value}/${path}</value_translation> | ||
<value_translation>${GALAXY_DATA_MANAGER_DATA_PATH}/genomes/${dbkey}/bowtie_index/v2/${value}/${path}</value_translation> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I do not understand why this is done? It will require all admins to restucture reference data, or? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. They don't have to - if you update to the new DMs and run them, they will just place data in a new folder, but the old loc with the old data at the old paths will continue to be loaded. That said, in the proposal I suggested that we recommend admins to specify a new |
||
<value_translation type="function">abspath</value_translation> | ||
</column> | ||
</output> | ||
|
@@ -25,11 +24,10 @@ | |
<column name="name" /> | ||
<column name="path" output_ref="out_file" > | ||
<!-- no move, always happens as part of bowtie2 and uses that path --> | ||
<value_translation>${GALAXY_DATA_MANAGER_DATA_PATH}/${dbkey}/bowtie2_index/${value}/${path}</value_translation> | ||
<value_translation>${GALAXY_DATA_MANAGER_DATA_PATH}/genomes/${dbkey}/bowtie_index/v2/${value}/${path}</value_translation> | ||
<value_translation type="function">abspath</value_translation> | ||
</column> | ||
</output> | ||
</data_table> | ||
</data_manager> | ||
|
||
</data_managers> |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
{ | ||
"data_tables":{ | ||
"bowtie2_indexes":[ | ||
{ | ||
"value": "phiX174", | ||
"dbkey": "phiX174", | ||
"name": "phiX 174", | ||
"path": "phiX174.fasta" | ||
} | ||
], | ||
"tophat2_indexes":[ | ||
{ | ||
"value": "phiX174", | ||
"dbkey": "phiX174", | ||
"name": "phiX 174", | ||
"path": "phiX174.fasta" | ||
} | ||
] | ||
} | ||
} |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
{ | ||
"data_tables":{ | ||
"bowtie2_indexes":[ | ||
{ | ||
"value": "tigHai1", | ||
"dbkey": "phiX174", | ||
"name": "Galeocerdo cuvier", | ||
"path": "phiX174.fasta" | ||
} | ||
] | ||
} | ||
} |
This file was deleted.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
#This file lists the locations and dbkeys of all the fasta files | ||
#under the "genome" directory (a directory that contains a directory | ||
#for each build). The script extract_fasta.py will generate the file | ||
#all_fasta.loc. This file has the format (white space characters are | ||
#TAB characters): | ||
# | ||
#<unique_build_id> <dbkey> <display_name> <file_path> | ||
# | ||
#So, all_fasta.loc could look something like this: | ||
# | ||
#apiMel3 apiMel3 Honeybee (Apis mellifera): apiMel3 /path/to/genome/apiMel3/apiMel3.fa | ||
#hg19canon hg19 Human (Homo sapiens): hg19 Canonical /path/to/genome/hg19/hg19canon.fa | ||
#hg19full hg19 Human (Homo sapiens): hg19 Full /path/to/genome/hg19/hg19full.fa | ||
# | ||
#Your all_fasta.loc file should contain an entry for each individual | ||
#fasta file. So there will be multiple fasta files for each build, | ||
#such as with hg19 above. | ||
# | ||
phiX174 phiX174 phiX 174 ${__HERE__}/phiX174.fasta |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
{ | ||
"data_tables":{ | ||
"bowtie_indexes":[ | ||
{ | ||
"value": "phiX174", | ||
"dbkey": "phiX174", | ||
"name": "phiX 174", | ||
"path": "phiX174.fasta" | ||
} | ||
] | ||
} | ||
} |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
{ | ||
"data_tables":{ | ||
"bowtie_indexes":[ | ||
{ | ||
"value": "tigHai1", | ||
"dbkey": "phiX174", | ||
"name": "Galeocerdo cuvier", | ||
"path": "phiX174.fasta" | ||
} | ||
] | ||
} | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool to cover this, but it seems SNAFU anyway, since the tophat2 data table refers to the bowtie2 loc file.
Maybe we just deprecate the tophat2 datatable (and update the tool to use the bowtie2 one)?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, this is probably just legacy. Good idea to update the tophat2 tool although I suppose in the unlikely case an admin has indexes in the
tophat2_indexes
table that are not inbowtie2_indexes
then they would disappear. And tophat is of course deprecated itself.