0
|
1
|
|
2 [TOC]
|
|
3
|
|
4 # 1. findKEGG.py
|
|
5 **find entries with matching query keywords or other query data in a given database**
|
|
6
|
|
7 ## Works with Galaxy?
|
|
8 Yes. see [findKEGG.xml](findKEGG.xml)
|
|
9
|
|
10 ## Command line usage
|
|
11 ```
|
|
12 ../../virtualpy/bin/activate
|
|
13 python findKEGG.py
|
|
14 ```
|
|
15
|
|
16 This will use the default settings for dbname, searchpattern and output
|
|
17 To specify these :
|
|
18 ```
|
|
19 ../../virtualpy/bin/activate
|
|
20 findKEGG.py -d $dbname -q $searchpattern -o $output
|
|
21 ```
|
|
22
|
1
|
23 ## Known Issues
|
|
24 Yes, the and/or functionality of the KEGG rest API (Release 78.0+/05-05, May 16 ) does not always function as expected. This has been resolved in the code. More details, [KEGGnotes.md ](KEGGnotes.md)
|
|
25
|
0
|
26 ## Help
|
|
27 ```
|
|
28 ../../virtualpy/bin/activate
|
|
29 python findKEGG.py -h
|
|
30 ```
|
|
31
|
|
32 ## Unit Testing?
|
|
33 Yes. Use test_findKEGG.py
|
|
34
|
|
35 ```
|
|
36 ../../virtualpy/bin/activate
|
1
|
37 nosetests test_findKEGG.py
|
0
|
38 ```
|
|
39
|
|
40 # 2. getkcfKEGG,py
|
|
41 **get – retrieves given database entries _but only for GLYCANS_**
|
|
42
|
|
43
|
|
44 ## Works with Galaxy?
|
|
45 Yes. see [getkcfKEGG.xml](getkcfKEGG.xml)
|
|
46
|
|
47 ## Command line usage
|
|
48
|
|
49 ```
|
|
50 ../../virtualpy/bin/activate
|
|
51 cat "G00092" > input
|
|
52 python getkcfKEGG.py
|
|
53 ```
|
|
54
|
|
55 This will use the default settings for input, kcfout and dbout
|
|
56 To specify these :
|
|
57 ```
|
|
58 ../../virtualpy/bin/activate
|
|
59 getkcfKEGG.py -i $input -k $kcfout -d $dbout
|
|
60 ```
|
|
61
|
|
62 ## Help
|
|
63 ```
|
|
64 ../../virtualpy/bin/activate
|
|
65 python getkcfKEGG.py -h
|
|
66 ```
|
|
67
|
|
68 ## Unit Testing?
|
|
69 Yes. Use test_getkcfKEGG.py
|
|
70
|
|
71 ```
|
|
72 ../../virtualpy/bin/activate
|
1
|
73 nosetests test_getkcfKEGG.py
|
0
|
74 ```
|
|
75
|
|
76 # 3. linkKEGG.py
|
|
77 **link – find related entries by using database cross-references**
|
|
78
|
|
79 ## Works with Galaxy?
|
|
80 Yes. see [linkKEGG.xml](linkKEGG.xml)
|
|
81
|
|
82 ## Command line usage
|
|
83 ```
|
|
84 ../../virtualpy/bin/activate
|
|
85 python linkKEGG.py
|
|
86 ```
|
|
87
|
|
88 This will use the default settings for targetdb, source and output
|
|
89 linkKEGG.py -t $targetdb -s $source -o $output
|
|
90 To specify these :
|
|
91 ```
|
|
92 ../../virtualpy/bin/activate
|
|
93 linkKEGG.py -t $targetdb -s $source -o $output
|
|
94 ```
|
|
95
|
|
96 ## Help
|
|
97 ```
|
|
98 ../../virtualpy/bin/activate
|
|
99 python linkKEGG.py -h
|
|
100 ```
|
|
101
|
|
102 ## Unit Testing?
|
|
103 Yes. Use test_linkKEGG.py
|
|
104
|
|
105 ```
|
|
106 ../../virtualpy/bin/activate
|
1
|
107 nosetests test_linkKEGG.py
|
0
|
108 ```
|
|
109
|