/var/lib/mobyle/programs/twofeat.xml is in mobyle-programs 5.1.1-1.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 | <?xml version="1.0" encoding="ISO-8859-1"?>
<!-- XML Authors: Corinne Maufrais and Nicolas Joly, -->
<!-- 'Biological Software and Databases' Group, Institut Pasteur, Paris. -->
<!-- Distributed under LGPLv2 License. Please refer to the COPYING.LIB document. -->
<program>
<head>
<name>twofeat</name>
<package>
<name>EMBOSS</name>
<version>6.3.1</version>
<doc>
<title>EMBOSS</title>
<description>
<text lang="en">European Molecular Biology Open Software Suite</text>
</description>
<authors>Rice,P. Longden,I. and Bleasby, A.</authors>
<reference>EMBOSS: The European Molecular Biology Open Software Suite (2000) Rice,P. Longden,I. and Bleasby, A. Trends in Genetics 16, (6) pp276--277</reference>
<sourcelink>http://emboss.sourceforge.net/download</sourcelink>
<homepagelink>http://emboss.sourceforge.net</homepagelink>
</doc>
</package>
<doc>
<title>twofeat</title>
<description>
<text lang="en">Finds neighbouring pairs of features in sequence(s)</text>
</description>
<doclink>http://bioweb2.pasteur.fr/docs/EMBOSS/twofeat.html</doclink>
<doclink>http://emboss.sourceforge.net/docs/themes</doclink>
</doc>
<category>sequence:edit:feature_table</category>
<command>twofeat</command>
</head>
<parameters>
<paragraph>
<name>e_input</name>
<prompt lang="en">Input section</prompt>
<parameters>
<parameter issimple="1" ismandatory="1">
<name>e_sequence</name>
<prompt lang="en">sequence option</prompt>
<type>
<datatype>
<class>Sequence</class>
</datatype>
<dataFormat>EMBL</dataFormat>
<dataFormat>FASTA</dataFormat>
<dataFormat>GCG</dataFormat>
<dataFormat>GENBANK</dataFormat>
<dataFormat>NBRF</dataFormat>
<dataFormat>CODATA</dataFormat>
<dataFormat>RAW</dataFormat>
<dataFormat>SWISSPROT</dataFormat>
<dataFormat>GFF</dataFormat>
<card>1,n</card>
</type>
<format>
<code proglang="python">("", " -sequence=" + str(value))[value is not None]</code>
</format>
<argpos>1</argpos>
</parameter>
<paragraph>
<name>e_afeaturesection</name>
<prompt lang="en">First feature options</prompt>
<parameters>
<parameter>
<name>e_asource</name>
<prompt lang="en">Source of first feature</prompt>
<type>
<datatype>
<class>String</class>
</datatype>
</type>
<format>
<code proglang="python">("", " -asource=" + str(value))[value is not None]</code>
</format>
<argpos>2</argpos>
<comment>
<text lang="en">By default any feature source in the feature table is allowed. You can set this to match any feature source you wish to allow.
The source name is usually either the name of the program that detected the feature or it is the feature table (eg: EMBL) that the feature came from.
The source may be wildcarded by using '*'.
If you wish to allow more than one source, separate their names with the character '|', eg:
gene* | embl</text>
</comment>
</parameter>
<parameter issimple="1" ismandatory="1">
<name>e_atype</name>
<prompt lang="en">Type of first feature</prompt>
<type>
<datatype>
<class>String</class>
</datatype>
</type>
<format>
<code proglang="python">("", " -atype=" + str(value))[value is not None]</code>
</format>
<argpos>3</argpos>
<comment>
<text lang="en">By default every feature in the feature table is allowed. You can set this to be any feature type you wish to allow.
See http://www.ebi.ac.uk/embl/WebFeat/ for a list of the EMBL feature types and see Appendix A of the Swissprot user manual in http://www.expasy.org/sprot/userman.html for a list of the Swissprot feature types.
The type may be wildcarded by using '*'.
If you wish to allow more than one type, separate their names with the character '|', eg:
*UTR | intron</text>
</comment>
</parameter>
<parameter>
<name>e_asense</name>
<prompt lang="en">Sense of first feature</prompt>
<type>
<datatype>
<class>Choice</class>
</datatype>
</type>
<vdef>
<value>0</value>
</vdef>
<vlist>
<velem>
<value>0</value>
<label>Any sense</label>
</velem>
<velem>
<value>+</value>
<label>Forward sense</label>
</velem>
<velem>
<value>-</value>
<label>Reverse sense</label>
</velem>
</vlist>
<format>
<code proglang="python">("", " -asense=" + str(value))[value is not None and value!=vdef]</code>
</format>
<argpos>4</argpos>
<comment>
<text lang="en">By default any feature sense is allowed. You can set this to match the required sense.</text>
</comment>
</parameter>
<parameter>
<name>e_aminscore</name>
<prompt lang="en">Minimum score of first feature</prompt>
<type>
<datatype>
<class>Float</class>
</datatype>
</type>
<vdef>
<value>0.0</value>
</vdef>
<format>
<code proglang="python">("", " -aminscore=" + str(value))[value is not None and value!=vdef]</code>
</format>
<argpos>5</argpos>
<comment>
<text lang="en">If this is greater than or equal to the maximum score, then any score is allowed.</text>
</comment>
</parameter>
<parameter>
<name>e_amaxscore</name>
<prompt lang="en">Maximum score of first feature</prompt>
<type>
<datatype>
<class>Float</class>
</datatype>
</type>
<vdef>
<value>0.0</value>
</vdef>
<format>
<code proglang="python">("", " -amaxscore=" + str(value))[value is not None and value!=vdef]</code>
</format>
<argpos>6</argpos>
<comment>
<text lang="en">If this is less than or equal to the maximum score, then any score is permitted.</text>
</comment>
</parameter>
<parameter>
<name>e_atag</name>
<prompt lang="en">Tag of first feature</prompt>
<type>
<datatype>
<class>String</class>
</datatype>
</type>
<format>
<code proglang="python">("", " -atag=" + str(value))[value is not None]</code>
</format>
<argpos>7</argpos>
<comment>
<text lang="en">Tags are the types of extra values that a feature may have. For example in the EMBL feature table, a 'CDS' type of feature may have the tags '/codon', '/codon_start', '/db_xref', '/EC_number', '/evidence', '/exception', '/function', '/gene', '/label', '/map', '/note', '/number', '/partial', '/product', '/protein_id', '/pseudo', '/standard_name', '/translation', '/transl_except', '/transl_table', or '/usedin'. Some of these tags also have values, for example '/gene' can have the value of the gene name.
By default any feature tag in the feature table is allowed. You can set this to match any feature tag you wish to allow.
The tag may be wildcarded by using '*'.
If you wish to allow more than one tag, separate their names with the character '|', eg:
gene | label</text>
</comment>
</parameter>
<parameter>
<name>e_avalue</name>
<prompt lang="en">Value of first feature's tags</prompt>
<type>
<datatype>
<class>String</class>
</datatype>
</type>
<format>
<code proglang="python">("", " -avalue=" + str(value))[value is not None]</code>
</format>
<argpos>8</argpos>
<comment>
<text lang="en">Tag values are the values associated with a feature tag. Tags are the types of extra values that a feature may have. For example in the EMBL feature table, a 'CDS' type of feature may have the tags '/codon', '/codon_start', '/db_xref', '/EC_number', '/evidence', '/exception', '/function', '/gene', '/label', '/map', '/note', '/number', '/partial', '/product', '/protein_id', '/pseudo', '/standard_name', '/translation', '/transl_except', '/transl_table', or '/usedin'. Only some of these tags can have values, for example '/gene' can have the value of the gene name. By default any feature tag value in the feature table is allowed. You can set this to match any feature tag value you wish to allow.
The tag value may be wildcarded by using '*'.
If you wish to allow more than one tag value, separate their names with the character '|', eg:
pax* | 10</text>
</comment>
</parameter>
</parameters>
</paragraph>
<paragraph>
<name>e_bfeaturesection</name>
<prompt lang="en">Second feature options</prompt>
<parameters>
<parameter>
<name>e_bsource</name>
<prompt lang="en">Source of second feature</prompt>
<type>
<datatype>
<class>String</class>
</datatype>
</type>
<format>
<code proglang="python">("", " -bsource=" + str(value))[value is not None]</code>
</format>
<argpos>9</argpos>
<comment>
<text lang="en">By default any feature source in the feature table is allowed. You can set this to match any feature source you wish to allow.
The source name is usually either the name of the program that detected the feature or it is the feature table (eg: EMBL) that the feature came from.
The source may be wildcarded by using '*'.
If you wish to allow more than one source, separate their names with the character '|', eg:
gene* | embl</text>
</comment>
</parameter>
<parameter issimple="1" ismandatory="1">
<name>e_btype</name>
<prompt lang="en">Type of second feature</prompt>
<type>
<datatype>
<class>String</class>
</datatype>
</type>
<format>
<code proglang="python">("", " -btype=" + str(value))[value is not None]</code>
</format>
<argpos>10</argpos>
<comment>
<text lang="en">By default every feature in the feature table is allowed. You can set this to be any feature type you wish to allow.
See http://www.ebi.ac.uk/embl/WebFeat/ for a list of the EMBL feature types and see Appendix A of the Swissprot user manual in http://www.expasy.org/sprot/userman.html for a list of the Swissprot feature types.
The type may be wildcarded by using '*'.
If you wish to allow more than one type, separate their names with the character '|', eg:
*UTR | intron</text>
</comment>
</parameter>
<parameter>
<name>e_bsense</name>
<prompt lang="en">Sense of second feature</prompt>
<type>
<datatype>
<class>Choice</class>
</datatype>
</type>
<vdef>
<value>0</value>
</vdef>
<vlist>
<velem>
<value>0</value>
<label>Any sense</label>
</velem>
<velem>
<value>+</value>
<label>Forward sense</label>
</velem>
<velem>
<value>-</value>
<label>Reverse sense</label>
</velem>
</vlist>
<format>
<code proglang="python">("", " -bsense=" + str(value))[value is not None and value!=vdef]</code>
</format>
<argpos>11</argpos>
<comment>
<text lang="en">By default any feature sense is allowed. You can set this to match the required sense.</text>
</comment>
</parameter>
<parameter>
<name>e_bminscore</name>
<prompt lang="en">Minimum score of second feature</prompt>
<type>
<datatype>
<class>Float</class>
</datatype>
</type>
<vdef>
<value>0.0</value>
</vdef>
<format>
<code proglang="python">("", " -bminscore=" + str(value))[value is not None and value!=vdef]</code>
</format>
<argpos>12</argpos>
<comment>
<text lang="en">If this is greater than or equal to the maximum score, then any score is allowed.</text>
</comment>
</parameter>
<parameter>
<name>e_bmaxscore</name>
<prompt lang="en">Maximum score of second feature</prompt>
<type>
<datatype>
<class>Float</class>
</datatype>
</type>
<vdef>
<value>0.0</value>
</vdef>
<format>
<code proglang="python">("", " -bmaxscore=" + str(value))[value is not None and value!=vdef]</code>
</format>
<argpos>13</argpos>
<comment>
<text lang="en">If this is less than or equal to the maximum score, then any score is permitted.</text>
</comment>
</parameter>
<parameter>
<name>e_btag</name>
<prompt lang="en">Tag of second feature</prompt>
<type>
<datatype>
<class>String</class>
</datatype>
</type>
<format>
<code proglang="python">("", " -btag=" + str(value))[value is not None]</code>
</format>
<argpos>14</argpos>
<comment>
<text lang="en">Tags are the types of extra values that a feature may have. For example in the EMBL feature table, a 'CDS' type of feature may have the tags '/codon', '/codon_start', '/db_xref', '/EC_number', '/evidence', '/exception', '/function', '/gene', '/label', '/map', '/note', '/number', '/partial', '/product', '/protein_id', '/pseudo', '/standard_name', '/translation', '/transl_except', '/transl_table', or '/usedin'. Some of these tags also have values, for example '/gene' can have the value of the gene name.
By default any feature tag in the feature table is allowed. You can set this to match any feature tag you wish to allow.
The tag may be wildcarded by using '*'.
If you wish to allow more than one tag, separate their names with the character '|', eg:
gene | label</text>
</comment>
</parameter>
<parameter>
<name>e_bvalue</name>
<prompt lang="en">Value of second feature's tags</prompt>
<type>
<datatype>
<class>String</class>
</datatype>
</type>
<format>
<code proglang="python">("", " -bvalue=" + str(value))[value is not None]</code>
</format>
<argpos>15</argpos>
<comment>
<text lang="en">Tag values are the values associated with a feature tag. Tags are the types of extra values that a feature may have. For example in the EMBL feature table, a 'CDS' type of feature may have the tags '/codon', '/codon_start', '/db_xref', '/EC_number', '/evidence', '/exception', '/function', '/gene', '/label', '/map', '/note', '/number', '/partial', '/product', '/protein_id', '/pseudo', '/standard_name', '/translation', '/transl_except', '/transl_table', or '/usedin'. Only some of these tags can have values, for example '/gene' can have the value of the gene name. By default any feature tag value in the feature table is allowed. You can set this to match any feature tag value you wish to allow.
The tag value may be wildcarded by using '*'.
If you wish to allow more than one tag value, separate their names with the character '|', eg:
pax* | 10</text>
</comment>
</parameter>
</parameters>
</paragraph>
<paragraph>
<name>e_featurerelationsection</name>
<prompt lang="en">Feature relation options</prompt>
<parameters>
<parameter>
<name>e_overlap</name>
<prompt lang="en">Type of overlap required</prompt>
<type>
<datatype>
<class>Choice</class>
</datatype>
</type>
<vdef>
<value>A</value>
</vdef>
<vlist>
<velem>
<value>A</value>
<label>Any</label>
</velem>
<velem>
<value>O</value>
<label>Overlap required</label>
</velem>
<velem>
<value>NO</value>
<label>No overlaps are allowed</label>
</velem>
<velem>
<value>NW</value>
<label>Overlap required but not within</label>
</velem>
<velem>
<value>AW</value>
<label>A must be all within b</label>
</velem>
<velem>
<value>BW</value>
<label>B must be all within a</label>
</velem>
</vlist>
<format>
<code proglang="python">("", " -overlap=" + str(value))[value is not None and value!=vdef]</code>
</format>
<argpos>16</argpos>
<comment>
<text lang="en">This allows you to specify the allowed overlaps of the features A and B.
You can allow any or no overlaps, specify that they must or must not overlap, that one must or must not be wholly enclosed within another feature.</text>
</comment>
</parameter>
<parameter issimple="1" ismandatory="1">
<name>e_minrange</name>
<prompt lang="en">The minimum distance between the features</prompt>
<type>
<datatype>
<class>Integer</class>
</datatype>
</type>
<vdef>
<value>0</value>
</vdef>
<format>
<code proglang="python">("", " -minrange=" + str(value))[value is not None and value!=vdef]</code>
</format>
<argpos>17</argpos>
<comment>
<text lang="en">If this is greater or equal to 'maxrange', then no min or max range is specified</text>
</comment>
</parameter>
<parameter issimple="1" ismandatory="1">
<name>e_maxrange</name>
<prompt lang="en">The maximum distance between the features</prompt>
<type>
<datatype>
<class>Integer</class>
</datatype>
</type>
<vdef>
<value>0</value>
</vdef>
<format>
<code proglang="python">("", " -maxrange=" + str(value))[value is not None and value!=vdef]</code>
</format>
<argpos>18</argpos>
<comment>
<text lang="en">If this is less than or equal to 'minrange', then no min or max range is specified</text>
</comment>
</parameter>
<parameter>
<name>e_rangetype</name>
<prompt lang="en">Positions from which to measure the distance</prompt>
<type>
<datatype>
<class>Choice</class>
</datatype>
</type>
<vdef>
<value>N</value>
</vdef>
<vlist>
<velem>
<value>N</value>
<label>From nearest ends</label>
</velem>
<velem>
<value>L</value>
<label>From left ends</label>
</velem>
<velem>
<value>R</value>
<label>From right ends</label>
</velem>
<velem>
<value>F</value>
<label>From furthest ends</label>
</velem>
</vlist>
<format>
<code proglang="python">("", " -rangetype=" + str(value))[value is not None and value!=vdef]</code>
</format>
<argpos>19</argpos>
<comment>
<text lang="en">This allows you to specify the positions from which the allowed minimum or maximum distance between the features is measured</text>
</comment>
</parameter>
<parameter>
<name>e_sense</name>
<prompt lang="en">Sense of the features</prompt>
<type>
<datatype>
<class>Choice</class>
</datatype>
</type>
<vdef>
<value>A</value>
</vdef>
<vlist>
<velem>
<value>A</value>
<label>Any sense</label>
</velem>
<velem>
<value>S</value>
<label>Same sense</label>
</velem>
<velem>
<value>O</value>
<label>Opposite sense</label>
</velem>
</vlist>
<format>
<code proglang="python">("", " -sense=" + str(value))[value is not None and value!=vdef]</code>
</format>
<argpos>20</argpos>
<comment>
<text lang="en">This allows you to specify the required sense that the two features must be on. This is ignored (always 'Any') when looking at protein sequence features.</text>
</comment>
</parameter>
<parameter>
<name>e_order</name>
<prompt lang="en">Order of the features</prompt>
<type>
<datatype>
<class>Choice</class>
</datatype>
</type>
<vdef>
<value>A</value>
</vdef>
<vlist>
<velem>
<value>A</value>
<label>Any</label>
</velem>
<velem>
<value>AB</value>
<label>Feature a then feature b</label>
</velem>
<velem>
<value>BA</value>
<label>Feature b then feature a</label>
</velem>
</vlist>
<format>
<code proglang="python">("", " -order=" + str(value))[value is not None and value!=vdef]</code>
</format>
<argpos>21</argpos>
<comment>
<text lang="en">This allows you to specify the required order of the two features. The order is measured from the start positions of the features. This criterion is always applied despite the specified overlap type required.</text>
</comment>
</parameter>
</parameters>
</paragraph>
</parameters>
</paragraph>
<paragraph>
<name>e_output</name>
<prompt lang="en">Output section</prompt>
<parameters>
<parameter>
<name>e_twoout</name>
<prompt lang="en">Do you want the two features written out individually</prompt>
<type>
<datatype>
<class>Boolean</class>
</datatype>
</type>
<vdef>
<value>0</value>
</vdef>
<format>
<code proglang="python">("", " -twoout")[ bool(value) ]</code>
</format>
<argpos>22</argpos>
<comment>
<text lang="en">If you set this to be true, then the two features themselves will be written out. If it is left as false, then a single feature will be written out covering the two features you found.</text>
</comment>
</parameter>
<parameter>
<name>e_typeout</name>
<prompt lang="en">Name of the output new feature</prompt>
<type>
<datatype>
<class>String</class>
</datatype>
</type>
<precond>
<code proglang="python">not e_twoout</code>
</precond>
<vdef>
<value>misc_feature</value>
</vdef>
<format>
<code proglang="python">("", " -typeout=" + str(value))[value is not None and value!=vdef]</code>
</format>
<argpos>23</argpos>
<comment>
<text lang="en">If you have specified that the pairs of features that are found should be reported as one feature in the ouput, then you can specify the 'type' name of the new feature here. By default every feature in the feature table is allowed. See http://www.ebi.ac.uk/embl/WebFeat/ for a list of the EMBL feature types and see Appendix A of the Swissprot user manual in http://www.expasy.org/sprot/userman.html for a list of the Swissprot feature types. If you specify an invalid feature type name, then the default name 'misc_feature' is used.</text>
</comment>
</parameter>
<parameter>
<name>e_outfile</name>
<prompt lang="en">Name of the report file</prompt>
<type>
<datatype>
<class>Filename</class>
</datatype>
</type>
<vdef>
<value>twofeat.report</value>
</vdef>
<format>
<code proglang="python">("" , " -outfile=" + str(value))[value is not None]</code>
</format>
<argpos>24</argpos>
</parameter>
<parameter>
<name>e_rformat_outfile</name>
<prompt lang="en">Choose the report output format</prompt>
<type>
<datatype>
<class>Choice</class>
</datatype>
</type>
<vdef>
<value>TABLE</value>
</vdef>
<vlist>
<velem>
<value>DASGFF</value>
<label>Dasgff</label>
</velem>
<velem>
<value>DBMOTIF</value>
<label>Dbmotif</label>
</velem>
<velem>
<value>DIFFSEQ</value>
<label>Diffseq</label>
</velem>
<velem>
<value>EMBL</value>
<label>Embl</label>
</velem>
<velem>
<value>EXCEL</value>
<label>Excel</label>
</velem>
<velem>
<value>FEATTABLE</value>
<label>Feattable</label>
</velem>
<velem>
<value>GENBANK</value>
<label>Genbank</label>
</velem>
<velem>
<value>GFF</value>
<label>Gff</label>
</velem>
<velem>
<value>LISTFILE</value>
<label>Listfile</label>
</velem>
<velem>
<value>MOTIF</value>
<label>Motif</label>
</velem>
<velem>
<value>NAMETABLE</value>
<label>Nametable</label>
</velem>
<velem>
<value>CODATA</value>
<label>Codata</label>
</velem>
<velem>
<value>REGIONS</value>
<label>Regions</label>
</velem>
<velem>
<value>SEQTABLE</value>
<label>Seqtable</label>
</velem>
<velem>
<value>SIMPLE</value>
<label>Simple</label>
</velem>
<velem>
<value>SRS</value>
<label>Srs</label>
</velem>
<velem>
<value>SWISS</value>
<label>Swiss</label>
</velem>
<velem>
<value>TABLE</value>
<label>Table</label>
</velem>
<velem>
<value>TAGSEQ</value>
<label>Tagseq</label>
</velem>
</vlist>
<format>
<code proglang="python">("", " -rformat=" + str(value))[value is not None and value!=vdef]</code>
</format>
<argpos>25</argpos>
</parameter>
<parameter isout="1">
<name>e_outfile_out</name>
<prompt lang="en">outfile_out option</prompt>
<type>
<datatype>
<class>Text</class>
</datatype>
<dataFormat>
<ref param="e_rformat_outfile">
</ref>
</dataFormat>
</type>
<precond>
<code proglang="python">e_rformat_outfile in ['DASGFF', 'DBMOTIF', 'DIFFSEQ', 'EMBL', 'EXCEL', 'FEATTABLE', 'GENBANK', 'GFF', 'LISTFILE', 'MOTIF', 'NAMETABLE', 'CODATA', 'REGIONS', 'SEQTABLE', 'SIMPLE', 'SRS', 'SWISS', 'TABLE', 'TAGSEQ']</code>
</precond>
<filenames>
<code proglang="python">e_outfile</code>
</filenames>
</parameter>
</parameters>
</paragraph>
<parameter ishidden="1">
<name>auto</name>
<prompt lang="en">Turn off any prompting</prompt>
<type>
<datatype>
<class>String</class>
</datatype>
</type>
<format>
<code proglang="python">" -auto -stdout"</code>
</format>
<argpos>26</argpos>
</parameter>
</parameters>
</program>
|