Files
galaxy/test/functional/tools/samples_tool_conf.xml
T
John Chilton 4de71a0c82 Allow setting `auto_format="True" on tool output`s.
The metadata system will then "sniff" the outputs and set the type appropriately.

Tool used to demonstrate and test this functionality is included, run the test with:

    ./run_tests.sh -framework -id output_auto_format

If auto_format="true" than explicitly setting ``format="another_type"`` will prevent the tool from loading so that we can allow this to specify a default type later without breaking backward compatiblity.

Update 1:
 - Switched from ``format="auto"`` to ``auto_format="true"`` based on Dan's comments (https://github.com/galaxyproject/galaxy/pull/130).

Update 2:
 - Updated this to work when setting metadata internally.
 - Switch underlying representation of type from ``_auto_`` to ``_sniff_`` based on seeing a new block in ``galaxy.jobs``. ``auto`` indicates the tool should specify the datatype at runtime. This is in some ways the inverse of that (the tool telling Galaxy to detect the type instead of Galaxy telling the tool to) so I decided it would be best to not have ``auto`` and ``_auto_`` doing completely different things.
2015-04-22 12:45:11 -04:00

75 lines
2.7 KiB
XML

<?xml version="1.0"?>
<toolbox tool_path="${tool_conf_dir}">
<tool file="upload.xml"/>
<tool file="simple_constructs.xml" />
<tool file="inheritance_simple.xml" />
<tool file="composite.xml" />
<tool file="compare_bam_as_sam.xml" />
<tool file="code_file.xml" />
<tool file="disambiguate_cond.xml" />
<tool file="multi_repeats.xml"/>
<tool file="multi_page.xml"/>
<tool file="multi_select.xml" />
<tool file="multi_output.xml" />
<tool file="multi_output_configured.xml" />
<tool file="multi_output_assign_primary.xml" />
<tool file="composite_output.xml" />
<tool file="metadata.xml" />
<tool file="metadata_bam.xml" />
<tool file="detect_errors_aggressive.xml" />
<tool file="md5sum.xml" />
<tool file="job_properties.xml" />
<tool file="gzipped_inputs.xml" />
<tool file="output_order.xml" />
<tool file="output_format.xml" />
<tool file="output_filter.xml" />
<tool file="output_auto_format.xml" />
<tool file="disambiguate_repeats.xml" />
<tool file="min_repeat.xml" />
<tool file="parallelism.xml" />
<tool file="parallelism_optional.xml" />
<tool file="implicit_default_conds.xml" />
<tool file="multi_data_param.xml" />
<tool file="column_param.xml" />
<tool file="column_multi_param.xml" />
<tool file="special_params.xml" />
<tool file="section.xml" />
<tool file="top_level_data.xml" />
<tool file="validation_default.xml" />
<tool file="validation_sanitizer.xml" />
<tool file="validation_repeat.xml" />
<tool file="identifier_single.xml" />
<tool file="identifier_multiple.xml" />
<tool file="tool_directory.xml" />
<tool file="output_action_change_format.xml" />
<tool file="collection_paired_test.xml" />
<tool file="collection_nested_test.xml" />
<tool file="collection_mixed_param.xml" />
<tool file="collection_two_paired.xml" />
<tool file="collection_creates_pair.xml" />
<tool file="collection_creates_pair_from_type.xml" />
<tool file="collection_creates_list.xml" />
<tool file="collection_creates_list_2.xml" />
<tool file="collection_optional_param.xml" />
<tool file="collection_split_on_column.xml" />
<tool file="cheetah_casting.xml" />
<tool file="multiple_versions_v01.xml" />
<tool file="multiple_versions_v02.xml" />
<!-- Tools interesting only for building up test workflows. -->
<!-- Next three tools demonstrate concatenating multiple datasets
with a repeat, multiple datasets with a multiple input data
parameter, and multiple datasets from a collection. -->
<tool file="for_workflows/cat.xml" />
<tool file="for_workflows/cat_list.xml" />
<tool file="for_workflows/cat_collection.xml" />
<tool file="for_workflows/head.xml" />
<tool file="for_workflows/cat_interleave.xml" />
<tool file="simple_constructs.yml" />
</toolbox>