May 2013 - galaxy-dev - lists.galaxyproject.org

Setting torque queues
by Scott Hazelhurst 14 Aug '13

14 Aug '13

[Apologies for my previous email : finger slippage meant I sent before completing the email] Dear dev I would be grateful for some assistance in setting up our galaxy server to submit jobs to our torque server.. We are using release_2013.04.01 I have tried going through the install information but clearly I¹ve misunderstood something, and unfortunately most examples come from earlier versions Here is my job_conf.xml file ‹ this is just a temporary file while I set things up. My intention is to run clustalw on our cluster using the torque queue WitsLong, assuming our torque server is galaxy.bioinf.wits.ac.za Below that is the output I get in the log. From the torque log it complains that there is no default queue specified. Any help would be appreciated. Thanks Scott <?xml version="1.0"?>  <job_conf> <plugins> <plugin id="local" type="runner" load="galaxy.jobs.runners.local:LocalJobRunner"/> <plugin id="pbs" type="runner" load="galaxy.jobs.runners.pbs:PBSJobRunner"/> </plugins> <handlers default="handlers"> <handler id="main" tags="handlers,pbs"/> </handlers> <destinations default="WitsLong"> <destination id="local" runner="local"/> <destination id="WitsLong" runner="pbs"> <param id="Resource_List">walltime=72:00:00,nodes=1:ppn=8</param> <param id="-p">128</param> </destination> </destinations> <tools> <tool id="foo" handler="trackster_handler"> <param id="source">trackster</param> </tool> <tool id="clustalw" destination="WitsLong"/> </tools> </job_conf> galaxy.jobs DEBUG 2013-04-30 15:28:13,481 (33) Working directory for job is: /home/galaxy/galaxy-dist/database/job_working_directory/000/33 galaxy.jobs.handler DEBUG 2013-04-30 15:28:13,527 (33) Dispatching to pbs runner 146.141.75.218, 146.141.1.81 - - [30/Apr/2013:15:28:12 +0200] "POST /galaxy/tool_runner/index HTTP/1.1" 200 - "http://galaxy.bioinf.wits.ac.za/galaxy/tool_runner/rerun?id=9752b387803d3e1 e" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0" galaxy.jobs DEBUG 2013-04-30 15:28:14,213 (33) Persisting job destination (destination id: WitsLong) Exception AssertionError: AssertionError('State <sqlalchemy.orm.state.InstanceState object at 0x7f79682e5150> is not present in this identity map',) in <bound method InstanceState._cleanup of <sqlalchemy.orm.state.InstanceState object at 0x7f79682e5150>> ignored galaxy.jobs.handler INFO 2013-04-30 15:28:14,522 (33) Job dispatched galaxy.tools DEBUG 2013-04-30 15:28:15,189 Building dependency shell command for dependency 'clustalw2' galaxy.tools WARNING 2013-04-30 15:28:15,192 Failed to resolve dependency on 'clustalw2', ignoring galaxy.jobs.runners.pbs DEBUG 2013-04-30 15:28:15,957 (33) submitting file /home/galaxy/galaxy-dist/database/pbs/33.sh galaxy.jobs.runners.pbs DEBUG 2013-04-30 15:28:15,958 (33) command is: python /home/galaxy/galaxy-dist/tools/rgenetics/rgClustalw.py -i "/home/galaxy/galaxy-dist/database/files/000/dataset_2.dat" -o "/home/galaxy/galaxy-dist/database/files/000/dataset_60.dat" -s "ALIGNED" -l "/home/galaxy/galaxy-dist/database/files/000/dataset_61.dat" -t "Clustal_run" -d "DNA" -f "CLUSTAL" galaxy.jobs.runners.pbs WARNING 2013-04-30 15:28:15,963 (33) pbs_submit failed (try 1/5), PBS error 15039: Route rejected by all destinations galaxy.jobs DEBUG 2013-04-30 15:28:16,400 (34) Working directory for job is: /home/galaxy/galaxy-dist/database/job_working_directory/000/34 galaxy.jobs.handler DEBUG 2013-04-30 15:28:16,416 (34) Dispatching to pbs runner 146.141.75.218, 146.141.1.81 - - [30/Apr/2013:15:28:13 +0200] "POST /galaxy/tool_runner/index HTTP/1.1" 200 - "http://galaxy.bioinf.wits.ac.za/galaxy/tool_runner/rerun?id=9752b387803d3e1 e" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:20.0) Gecko/20100101 Firefox/20.0" galaxy.jobs DEBUG 2013-04-30 15:28:16,668 (34) Persisting job destination (destination id: WitsLong) galaxy.jobs.handler INFO 2013-04-30 15:28:16,689 (34) Job dispatched galaxy.tools DEBUG 2013-04-30 15:28:16,937 Building dependency shell command for dependency 'clustalw2' galaxy.tools WARNING 2013-04-30 15:28:16,938 Failed to resolve dependency on 'clustalw2', ignoring galaxy.jobs.runners.pbs DEBUG 2013-04-30 15:28:17,160 (34) submitting file /home/galaxy/galaxy-dist/database/pbs/34.sh galaxy.jobs.runners.pbs DEBUG 2013-04-30 15:28:17,161 (34) command is: python /home/galaxy/galaxy-dist/tools/rgenetics/rgClustalw.py -i "/home/galaxy/galaxy-dist/database/files/000/dataset_2.dat" -o "/home/galaxy/galaxy-dist/database/files/000/dataset_62.dat" -s "ALIGNED" -l "/home/galaxy/galaxy-dist/database/files/000/dataset_63.dat" -t "Clustal_run" -d "DNA" -f "CLUSTAL" galaxy.jobs.runners.pbs WARNING 2013-04-30 15:28:17,162 (34) pbs_submit failed (try 1/5), PBS error 15039: Route rejected by all destinations galaxy.jobs.runners.pbs WARNING 2013-04-30 15:28:17,971 (33) pbs_submit failed (try 2/5), PBS error 15039: Route rejected by all destinations galaxy.jobs.runners.pbs WARNING 2013-04-30 15:28:19,166 (34) pbs_submit failed (try 2/5), PBS error 15039: Route rejected by all destinations galaxy.jobs.runners.pbs WARNING 2013-04-30 15:28:19,975 (33) pbs_submit failed (try 3/5), PBS error 15039: Route rejected by all destinations galaxy.jobs.runners.pbs WARNING 2013-04-30 15:28:21,170 (34) pbs_submit failed (try 3/5), PBS error 15039: Route rejected by all destinations galaxy.jobs.runners.pbs WARNING 2013-04-30 15:28:21,978 (33) pbs_submit failed (try 4/5), PBS error 15039: Route rejected by all destinations galaxy.jobs.runners.pbs WARNING 2013-04-30 15:28:23,173 (34) pbs_submit failed (try 4/5), PBS error 15039: Route rejected by all destinations galaxy.jobs.runners.pbs WARNING 2013-04-30 15:28:23,982 (33) pbs_submit failed (try 5/5), PBS error 15039: Route rejected by all destinations galaxy.jobs.runners.pbs WARNING 2013-04-30 15:28:25,176 (34) pbs_submit failed (try 5/5), PBS error 15039: Route rejected by all destinations galaxy.jobs.runners.pbs ERROR 2013-04-30 15:28:25,984 (33) All attempts to submit job failed galaxy.jobs.runners.pbs ERROR 2013-04-30 15:28:27,179 (34) All attempts to submit job failed <table width="100%" border="0" cellspacing="0" cellpadding="0" style="width:100%;"> <tr> <td align="left" style="text-align:justify;"><font face="arial,sans-serif" size="1" color="#999999"><span style="font-size:11px;">This communication is intended for the addressee only. It is confidential. If you have received this communication in error, please notify us immediately and destroy the original message. You may not copy or disseminate this communication without the permission of the University. Only authorised signatories are competent to enter into agreements on behalf of the University and recipients are thus advised that the content of this message may not be legally binding on the University and may contain the personal views and opinions of the author, which are not necessarily the views and opinions of The University of the Witwatersrand, Johannesburg. All agreements between the University and outsiders are subject to South African Law unless the University agrees in writing to the contrary. </span></font></td> </tr> </table

2 1

Adding GATK tools to Galaxy Cloudman
by Iry Witham 12 Aug '13

12 Aug '13

Hi Team, I am trying to get GATK tools added to my cloud instance and keep getting the following error: [Errno 2] No such file or directory: '/mnt/galaxyData/tmp/tmpszWRLP/GenomeAnalysisTKLite-2.3-9-gdcdccbb/GenomeAnalysisTK.jar'. Then when I try to install it again I get the following: All selected tool dependencies are already installed. I also get the following error: Initializing repository installation failed. Thanks, Iry The information in this email, including attachments, may be confidential and is intended solely for the addressee(s). If you believe you received this email by mistake, please notify the sender by return email as soon as possible.

3 3

Invalid Galaxy URL: None - Installing Tools Shed
by Adam Brenner 06 Aug '13

06 Aug '13

Howdy, I am trying to install a tools shed item, Emboss, but when I do this via the admin interface, I get the following text: Repository installation is not possible due to an invalid Galaxy URL: None. You may need to enable cookies in your browser. I have searched the universe_wsgi.ini file and could not find anything that looks like Galaxy URL. Any ideas on how to set the Galaxy URL? Thanks, -Adam -- Adam Brenner Computer Science, Undergraduate Student Donald Bren School of Information and Computer Sciences Research Computing Support Office of Information Technology http://www.oit.uci.edu/rcs/ University of California, Irvine www.ics.uci.edu/~aebrenne/ aebrenne(a)uci.edu

4 9

Tool Shed test framework breaking where run_functional_tests.sh works
by Peter Cock 29 Jul '13

29 Jul '13

On Thu, May 9, 2013 at 10:49 AM, Peter Cock <p.j.a.cock(a)googlemail.com> wrote: > > Hi Dave, > > As you hoped, these test now shows up on the tool page (as expected > they are test failures - apparently my install script isn't quite right yet): > > ... > > This one is more interesting, and appears to be a problem with the > test framework (both tests pass locally via run_functional_tests.sh): > > http://testtoolshed.g2.bx.psu.edu/view/peterjc/seq_rename/16a1a5ae98e9 > Functional test results for changeset revision 16a1a5ae98e9 of seq_rename > 0 tests passed, 2 tests failed, 0 tests missing test components. > > I'll raise that on a new thread, Here's the output from the (Test) Tool Shed where the tests fail: Tests that failed *Tool id:* seq_rename *Tool version:* seq_rename *Test:*test_tool_000000 ( functional.test_toolbox.TestForTool_testtoolshed.g2.bx.psu.edu/repos/peterj… ) *Stderr:* *Traceback:* Traceback (most recent call last): File "/var/opt/buildslaves/buildslave-ec2-1/buildbot-install-test-test-tool-shed-py27/build/test/functional/test_toolbox.py", line 171, in test_tool self.do_it( td, shed_tool_id=shed_tool_id ) File "/var/opt/buildslaves/buildslave-ec2-1/buildbot-install-test-test-tool-shed-py27/build/test/functional/test_toolbox.py", line 78, in do_it self.run_tool( testdef.tool.id, repeat_name=repeat_name, **page_inputs ) File "/var/opt/buildslaves/buildslave-ec2-1/buildbot-install-test-test-tool-shed-py27/build/test/base/twilltestcase.py", line 1320, in run_tool self.submit_form( **kwd ) File "/var/opt/buildslaves/buildslave-ec2-1/buildbot-install-test-test-tool-shed-py27/build/test/base/twilltestcase.py", line 1270, in submit_form raise AssertionError( errmsg ) AssertionError: Attempting to set field 'new_column' to value '['2']' in form 'tool_form' threw exception: cannot find value/label "2" in list control control: <SelectControl(new_column=[1])> If the above control is a DataToolparameter whose data type class does not include a sniff() method, make sure to include a proper 'ftype' attribute to the tag for the control within the <test> tag set. *Tool id:* seq_rename *Tool version:* seq_rename *Test:*test_tool_000001 ( functional.test_toolbox.TestForTool_testtoolshed.g2.bx.psu.edu/repos/peterj… ) *Stderr:* *Traceback:* Traceback (most recent call last): File "/var/opt/buildslaves/buildslave-ec2-1/buildbot-install-test-test-tool-shed-py27/build/test/functional/test_toolbox.py", line 171, in test_tool self.do_it( td, shed_tool_id=shed_tool_id ) File "/var/opt/buildslaves/buildslave-ec2-1/buildbot-install-test-test-tool-shed-py27/build/test/functional/test_toolbox.py", line 78, in do_it self.run_tool( testdef.tool.id, repeat_name=repeat_name, **page_inputs ) File "/var/opt/buildslaves/buildslave-ec2-1/buildbot-install-test-test-tool-shed-py27/build/test/base/twilltestcase.py", line 1320, in run_tool self.submit_form( **kwd ) File "/var/opt/buildslaves/buildslave-ec2-1/buildbot-install-test-test-tool-shed-py27/build/test/base/twilltestcase.py", line 1270, in submit_form raise AssertionError( errmsg ) AssertionError: Attempting to set field 'new_column' to value '['c2']' in form 'tool_form' threw exception: cannot find value/label "c2" in list control control: <SelectControl(new_column=[1])> If the above control is a DataToolparameter whose data type class does not include a sniff() method, make sure to include a proper 'ftype' attribute to the tag for the control within the <test> tag set. Both tests fail with the following assertion: AssertionError: Attempting to set field 'new_column' to value '['c2']' in form 'tool_form' threw exception: cannot find value/label "c2" in list control control: <SelectControl(new_column=[1])> If the above control is a DataToolparameter whose data type class does not include a sniff() method, make sure to include a proper 'ftype' attribute to the tag for the control within the <test> tag set. Both tests pass on my development machine run via: $ ./run_functional_tests.sh -id seq_rename The two tests are defined as follows - identical bar the style used for the column arguments - I was wondering if the Tool Shed testing was stricter about numeric column names, but that does not seem to be relevant: <tests> <test> <param name="input_file" value="four_human_proteins.fasta" ftype="fasta" /> <param name="input_tabular" value="four_human_proteins.rename.tabular" ftype="tabular" /> <param name="old_column" value="1" /> <param name="new_column" value="2" /> <output name="output_file" file="four_human_proteins.rename.fasta" ftype="fasta" /> </test> <test> <param name="input_file" value="four_human_proteins.fasta" ftype="fasta" /> <param name="input_tabular" value="four_human_proteins.rename.tabular" ftype="tabular" /> <param name="old_column" value="c1" /> <param name="new_column" value="c2" /> <output name="output_file" file="four_human_proteins.rename.fasta" ftype="fasta" /> </test> </tests> I can retest with the latest galaxy-dist once this issue is resolved: http://lists.bx.psu.edu/pipermail/galaxy-dev/2013-May/014557.html Peter

5 12

Tool Shed Request - sanity check uploads?
by Peter Cock 29 Jul '13

29 Jul '13

Hi all, For what is I think the second time (fortunately this was only on the Test Tool Shed), I have managed to upload a tar-ball to the wrong repository: 2:fae4084a0bc0 http://testtoolshed.g2.bx.psu.edu/view/peterjc/fastq_paired_unpaired It could have been a glitch, but more likely is was simply inattention on my part (most likely - multiple tab browsing has its downsides). This leads me to offer some suggestions for how to prevent this kind of user error in future: (1) After the upload, show a preview of the changes for confirmation (the drawback is this could take a long time to process for a large upload, and lead to time outs). (2) After upload, before committing the changes, compare the tool contents - adding or removing some tools is normal, replacing ALL the tools with different tools is probably an error and should be subject to user confirmation. (3) Offer a repository action to revert to a prior commit (current workaround is to re-upload the old good file, which I did as 3:81ac324efa49 in this case). Peter

3 8

samtools BAM to SAM tmp directory
by Matt Shirley 03 Jul '13

03 Jul '13

Is there a reason that the samtools BAM to SAM does not respect the new_file_path set in the config file? The tmp directory handling by different tool wrappers seems to be an issue right now on systems with small system tmp directories. -- Matt Shirley Ph.D Candidate - BCMB Pevsner Lab <http://pevsnerlab.kennedykrieger.org/> Johns Hopkins Medicine

3 4

Error running tophat2 in Galaxy
by Sachit Adhikari 02 Jul '13

02 Jul '13

I am getting this error: Error in tophat: [2013-02-13 20:46:41] Beginning TopHat run (v2.0.7) ----------------------------------------------- [2013-02-13 20:46:41] Checking for Bowtie Bowtie version: 2.0.6.0 [2013-02-13 20:46:41] Checking for Samtools Samtools version: 0.1.18.0 [2013-02-13 20:46:41] Checking for Bowtie index files [2013-02-13 20:46:41] Checking for reference FASTA file Warning: Could not find FASTA file /data/rathi/Homo_sapiens/UCSC/hg19/Sequence/Bowtie2Index/genome.fa [2013-02-13 20:46:41] Reconstituting reference FASTA file from Bowtie index Executing: /usr/bin/bowtie2-inspect /data/rathi/Homo_sapiens/UCSC/hg19/Sequence/Bowtie2Index/genome > ./tophat_out/tmp/genome.fa [2013-02-13 20:48:51] Generating SAM header for /data/rathi/Homo_sapiens/UCSC/hg19/Sequence/Bowtie2Index/genome format: fastq quality scale: phred33 (default) [2013-02-13 20:49:23] Preparing reads left reads: min. length=34, max. length=34, 2 kept reads (0 discarded) Warning: you have only one segment per read. If the read length is greater than or equal to 45bp, we strongly recommend that you decrease --segment-length to about half the read length because TopHat will work better with multiple segments [2013-02-13 20:49:23] Mapping left_kept_reads to genome genome with Bowtie2 [2013-02-13 20:49:56] Searching for junctions via segment mapping Coverage-search algorithm is turned on, making this step very slow Please try running TopHat again with the option (--no-coverage-search) if this step takes too much time or memory. Warning: junction database is empty! [2013-02-13 20:51:18] Reporting output tracks [FAILED] Error running /usr/local/bin/tophat_reports --min-anchor 8 --splice-mismatches 0 --min-report-intron 50 --max-report-intron 500000 --min-isoform-fraction 0.15 --output-dir ./tophat_out/ --max-multihits 20 --max-seg-multihits 40 --segment-length 25 --segment-mismatches 2 --min-closure-exon 100 --min-closure-intron 50 --max-closure-intron 5000 --min-coverage-intron 50 --max-coverage-intron 20000 --min-segment-intron 50 --max-segment-intron 500000 --read-mismatches 2 --read-gap-length 2 --read-edit-dist 2 --read-realign-edit-dist 3 --max-insertion-length 3 --max-deletion-length 3 -z gzip -p4 --no-closure-search --no-microexon-search --sam-header ./tophat_out/tmp/genome_genome.bwt.samheader.sam --report-discordant-pair-alignments --report-mixed-alignments --samtools=/bin/samtools --bowtie2-max-penalty 6 --bowtie2-min-penalty 2 --bowtie2-penalty-for-N 1 --bowtie2-read-gap-open 5 --bowtie2-read-gap-cont 3 --bowtie2-ref-gap-open 5 --bowtie2-ref-gap-cont 3 ./tophat_out/tmp/genome.fa ./tophat_out/junctions.bed ./tophat_out/insertions.bed ./tophat_out/deletions.bed ./tophat_out/fusions.out ./tophat_out/tmp/accepted_hits ./tophat_out/tmp/left_kept_reads.bam Loading ...done What's wrong?

2 1

Tool menu customization :: Card #727
by Björn Grüning 13 Jun '13

13 Jun '13

Hi, thanks to the awesome work from John Chilton in pull request #160 [1] I hacked up a first version of a tool customization that can be controlled by the user [2]. Requested as trello card #727. The user will have a new preference panel (see the attached screenshot) and can toggle several customization options. The options can be specified by each administrator as filter modules under lib/galaxy/tools/filters/. More details in John's original pull request. For example, one use case would be to offer different module sets for different studies. You can specify system-customizations (John's work) with tool_filters = module:function, module:function2 tool_label_filters = ... tool_section_filters = ... and offer user-customizations with: user_tool_filters = examples:restrict_upload_to_admins user_tool_section_filters = examples:restrict_text user_tool_label_filters = ... at the same time. Only user-customizations will be shown in the preference panel. The description of each filter is parsed from the docstring and shown to the user. The patch requires no modification to the database, all user preferences will be stored in user_preference with three special names. Is there any plan from the core development team how such a feature should be addressed. Is that approach flexible enough? It would be great to get some feedback in which direction such a feature should evolve and if its worth to put more time on it. Thanks John, hope you code will be merged! Thanks for your comments, Bjoern [1] https://bitbucket.org/galaxy/galaxy-central/pull-request/160/implement-dyna… [2] https://bitbucket.org/BjoernGruening/galaxy-central-bgruening/commits/68e7b…

1 1

Galaxy on Cluster - how to set -a flag with username
by greg 12 Jun '13

12 Jun '13

In our local galaxy install we want the cluster jobs to be run from the galaxy user but we want to include a -a [account name] to our grid software bills properly. Here's what I currently have in universe.wsgi: default_cluster_job_runner = drmaa://-V -pe batch 8/ What I want is something like this: default_cluster_job_runner = drmaa://-V -pe batch 8 -a [logged in user name]/ Is this possible? Thanks, Greg

3 5

Problems running functional tests
by Ira Cooke 06 Jun '13

06 Jun '13

Hi All, I'm starting to add functional tests to my tools but I've found that I can't get the test framework to work well with tool dependencies. The tool I'm considering is xtandem http://testtoolshed.g2.bx.psu.edu/view/iracooke/xtandem When I install this tool on my local galaxy instance (on a clean install) the tool runs fine and if I look in the handler logs I see executing: PACKAGE_BASE=/home/iracooke/tool_dependencies/galaxy_protk/1.2.0/iracooke/xtandem/0940ff5d28ab; export PACKAGE_BASE; . /home/iracooke/tool_dependencies/galaxy_protk/1.2.0/iracooke/xtandem/0940ff5d28ab/env.sh; PACKAGE_BASE=/home/iracooke/tool_dependencies/trans_proteomic_pipeline/4.6.1/iracooke/xtandem/0940ff5d28ab; export PACKAGE_BASE; . /home/iracooke/tool_dependencies/trans_proteomic_pipeline/4.6.1/iracooke/xtandem/0940ff5d28ab/env.sh; rvm 1.9.3(a)protk-1.2.0 do tandem_search.rb -d /home/iracooke/galaxy-central/database/files/000/dataset_1.dat --var-mods=' 57.021464__at__C ' --fix-mods=' 15.994915__at__M ' /home/iracooke/galaxy-central/database/files/000/dataset_2.dat -o /home/iracooke/galaxy-central/database/files/000/dataset_4.dat -r --enzyme=Trypsin --precursor-ion-tol-units=ppm -v 0 -f 0.65 -p 100.0 --strict-monoisotopic-mass --keep-params-files galaxy.jobs DEBUG 2013-04-27 06:53:35,586 (4) Persisting job destination (destination id: local:///) Note that in this case the tool environments from my tool dependencies are loaded ... and the tool runs fine. When running functional tests however the tests are executed without first loading the environments from tool dependencies ... and naturally the tool fails. On my local machine I get the following when running the tests (Note that no loading of dependency shel environments occurs). (This seems to be the same issue on the testtoolshed.g2.bx.psu.edu ). Job dispatched galaxy.jobs.runners.local DEBUG 2013-04-27 06:55:19,564 (3) executing: rvm 1.9.3(a)protk-1.2.0 do tandem_search.rb -d /tmp/tmp3I8GgN/database/files/000/dataset_1.dat --var-mods=' 15.994915__at__M , ' --fix-mods=' 57.021464__at__C ' /tmp/tmp3I8GgN/database/files/000/dataset_2.dat -o /tmp/tmp3I8GgN/database/files/000/dataset_3.dat -r --enzyme=Trypsin --precursor-ion-tol-units=ppm -v 0 -f 0.65 -p 100.0 --strict-monoisotopic-mass --keep-params-files galaxy.jobs DEBUG 2013-04-27 06:55:19,730 (3) Persisting job destination (destination id: local:///) galaxy.jobs.runners.local DEBUG 2013-04-27 06:55:19,889 execution finished: rvm 1.9.3(a)protk-1.2.0 do tandem_search.rb -d /tmp/tmp3I8GgN/database/files/000/dataset_1.dat --var-mods=' 15.994915__at__M ,' --fix-mods=' 57.021464__at__C ' /tmp/tmp3I8GgN/database/files/000/dataset_2.dat -o /tmp/tmp3I8GgN/database/files/000/dataset_3.dat -r --enzyme=Trypsin --precursor-ion-tol-units=ppm -v 0 -f 0.65 -p 100.0 --strict-monoisotopic-mass --keep-params-files ... galaxy.jobs DEBUG 2013-04-27 06:55:24,277 setting dataset state to ERROR Is there something wrong with the way I've defined my tool dependencies for this tool? Or perhaps it's a bug in the testing framework. Cheers Ira

4 7