forked from galaxyproject/tools-iuc
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request galaxyproject#2683 from mvdbeek/test_twobit_data_m…
…anager Fix tests for data_manager_twobit_builder and python 3 compatibility
- Loading branch information
Showing
10 changed files
with
172 additions
and
34 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
57 changes: 57 additions & 0 deletions
57
data_managers/data_manager_twobit_builder/test-data/alignseq.loc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,57 @@ | ||
#This is a sample file distributed with Galaxy that enables tools | ||
#to use alignment data stored as axt files (lines starting with "align") | ||
#or nib files (lines starting with "seq"). You will need to index | ||
#them and then create an alignseq.loc file similar to this one (store | ||
#it in this directory) that points to the directories in which those | ||
#alignments are stored. The "align" data referred to by the alignseq.loc | ||
#file has this format (white space characters are TAB characters): | ||
# | ||
#align <build1> <build2> <dir> | ||
# | ||
#So, for example, if you had hg18/bosTau2 alignment files stored in | ||
#/depot/data2/galaxy/hg18/align/bosTau2, then the alignseq.loc entry | ||
#would look like this: | ||
# | ||
#align hg18 bosTau2 /depot/data2/galaxy/hg18/align/bosTau2 | ||
# | ||
#and your /depot/data2/galaxy/hg18/align/bosTau2 directory would | ||
#contain all of your alignment files (e.g.): | ||
# | ||
#-rw-rw-r-- 1 nate galaxy 151842783 2006-01-08 01:00 chr10.axt | ||
#-rw-rw-r-- 1 nate galaxy 79575 2006-01-08 01:00 chr10_random.axt | ||
#-rw-rw-r-- 1 nate galaxy 155015634 2006-01-08 01:01 chr11.axt | ||
#...etc... | ||
# | ||
#Your alignseq.loc file should include an entry per line for each alignment | ||
#file you have stored. For example: | ||
# | ||
#align anoGam1 dm1 /depot/data2/galaxy/anoGam1/align/dm1 | ||
#align anoGam1 dm2 /depot/data2/galaxy/anoGam1/align/dm2 | ||
#align canFam1 hg17 /depot/data2/galaxy/canFam1/align/hg17 | ||
#...etc... | ||
# | ||
#The "seq" data referred to by the alignseq.loc file has this | ||
#format (white space characters are TAB characters): | ||
# | ||
#seq <build1> <dir> | ||
# | ||
#So, for example, if you had anoGam1 sequence files stored in | ||
#/depot/data2/galaxy/anoGam1/seq, then the alignseq.loc entry | ||
#would look like this: | ||
# | ||
#seq anoGam1 /depot/data2/galaxy/anoGam1/seq | ||
#and your seq anoGam1 /depot/data2/galaxy/anoGam1/seq directory would | ||
#contain all of your sequence files (e.g.): | ||
# | ||
#-rw-rw-r-- 1 nate galaxy 24397551 2006-06-26 12:51 chr2L.nib | ||
#-rw-rw-r-- 1 nate galaxy 31362964 2006-06-26 12:51 chr2R.nib | ||
#-rw-rw-r-- 1 nate galaxy 20642013 2006-06-26 12:51 chr3L.nib | ||
#-rw-rw-r-- 1 nate galaxy 26636071 2006-06-26 12:51 chr3R.nib | ||
# | ||
#Your alignseq.loc file should include an entry per line for each sequence | ||
#file you have stored. For example: | ||
# | ||
#seq anoGam1 /depot/data2/galaxy/anoGam1/seq | ||
#seq bosTau2 /depot/data2/galaxy/bosTau2/seq | ||
#seq bosTau3 /depot/data2/galaxy/bosTau3/seq | ||
#...etc... |
1 change: 1 addition & 0 deletions
1
data_managers/data_manager_twobit_builder/test-data/all_fasta.loc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
sacCer2 sacCer2 sacCer2 ${__HERE__}/sacCer2.fa |
1 change: 1 addition & 0 deletions
1
data_managers/data_manager_twobit_builder/test-data/data_manager_twobit.json
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
{"data_tables": {"alignseq_seq": [{"path": "sacCer2.2bit", "type": "seq", "value": "sacCer2"}], "lastz_seqs": [{"name": "sacCer2", "path": "sacCer2.2bit", "value": "sacCer2"}], "twobit": [{"path": "sacCer2.2bit", "value": "sacCer2"}]}} |
30 changes: 30 additions & 0 deletions
30
data_managers/data_manager_twobit_builder/test-data/lastz_seqs.loc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
#This is a sample file distributed with Galaxy that enables tools | ||
#to use a directory of 2bit genome files for use with Lastz. You will | ||
#need to supply these files and then create a lastz_seqs.loc file | ||
#similar to this one (store it in this directory) that points to | ||
#the directories in which those files are stored. The lastz_seqs.loc | ||
#file has this format (white space characters are TAB characters): | ||
# | ||
#<unique_build_id> <display_name> <file_path> | ||
# | ||
#So, for example, if your lastz_seqs.loc began like this: | ||
# | ||
#hg18 Human (Homo sapiens): hg18 /depot/data2/galaxy/twobit/hg18.2bit | ||
#hg19 Human (Homo sapiens): hg19 /depot/data2/galaxy/twobit/hg19.2bit | ||
#mm9 Mouse (Mus musculus): mm9 /depot/data2/galaxy/twobit/mm9.2bit | ||
# | ||
#then your /depot/data2/galaxy/twobit/ directory | ||
#would need to contain the following 2bit files: | ||
# | ||
#-rw-r--r-- 1 james universe 830134 2005-09-13 10:12 hg18.2bit | ||
#-rw-r--r-- 1 james universe 527388 2005-09-13 10:12 hg19.2bit | ||
#-rw-r--r-- 1 james universe 269808 2005-09-13 10:12 mm9.2bit | ||
# | ||
#Your lastz_seqs.loc file should include an entry per line for | ||
#each file you have stored that you want to be available. Note that | ||
#your files should all have the extension '2bit'. | ||
# | ||
#Note that for backwards compatibility with workflows, the unique ID of | ||
#an entry must be the path that was in the original loc file, because that | ||
#is the value stored in the workflow for that parameter. | ||
# |
Binary file not shown.
2 changes: 2 additions & 0 deletions
2
data_managers/data_manager_twobit_builder/test-data/sacCer2.fa
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
>chr1 | ||
ATGCATCGATCGATCGCATCGACTACGACTACGATCAGTCACTACACTACGTACAGCTACGACTACGACTACGATCGACTACGATCAGCTACGACA |
26 changes: 26 additions & 0 deletions
26
data_managers/data_manager_twobit_builder/test-data/twobit.loc
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
#This is a sample file distributed with Galaxy that is used by some | ||
#tools. The twobit.loc file has this format (white space characters | ||
#are TAB characters): | ||
# | ||
#<Build> <FullPathToFile> | ||
# | ||
#So, for example, if you had droPer1 twobit files stored in | ||
#/depot/data2/galaxy/droPer1/, then the twobit.loc entry | ||
#would look like this: | ||
# | ||
#droPer1 /depot/data2/galaxy/droPer1/droPer1.2bit | ||
# | ||
#and your /depot/data2/galaxy/droPer1/ directory would | ||
#contain all of your twobit files (e.g.): | ||
# | ||
#-rw-rw-r-- 1 nate galaxy 48972650 2007-05-04 11:27 droPer1.2bit | ||
#...etc... | ||
# | ||
#Your twobit.loc file should include an entry per line for each twobit | ||
#file you have stored. For example: | ||
# | ||
#droPer1 /depot/data2/galaxy/droPer1/droPer1.2bit | ||
#apiMel2 /depot/data2/galaxy/apiMel2/apiMel2.2bit | ||
#droAna1 /depot/data2/galaxy/droAna1/droAna1.2bit | ||
#droAna2 /depot/data2/galaxy/droAna2/droAna2.2bit | ||
#...etc... |
21 changes: 21 additions & 0 deletions
21
data_managers/data_manager_twobit_builder/tool_data_table_conf.xml.test
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,21 @@ | ||
<!-- Use the file tool_data_table_conf.xml.oldlocstyle if you don't want to update your loc files as changed in revision 4550:535d276c92bc--> | ||
<tables> | ||
<!-- Locations of all fasta files under genome directory --> | ||
<table name="all_fasta" comment_char="#"> | ||
<columns>value, dbkey, name, path</columns> | ||
<file path="${__HERE__}/test-data/all_fasta.loc" /> | ||
</table> | ||
<!-- Locations of 2bit sequence files for use in Lastz --> | ||
<table name="lastz_seqs" comment_char="#"> | ||
<columns>value, name, path</columns> | ||
<file path="${__HERE__}/test-data/lastz_seqs.loc" /> | ||
</table> | ||
<table name="twobit" comment_char="#"> | ||
<columns>value, path</columns> | ||
<file path="${__HERE__}/test-data/twobit.loc" /> | ||
</table> | ||
<table name="alignseq_seq" comment_char="#"> | ||
<columns>type, value, path</columns> | ||
<file path="${__HERE__}/test-data/alignseq.loc" /> | ||
</table> | ||
</tables> |