Answers.Body: <ol>
  <li>Picard, like most tools, prints logs to stderr.</li>
  <li>It should be in the Galaxy history. Are you using a version of picard from the toolshed (if so, which one)? You might set <code>cleanup_job</code> to <code>never</code> in the config, which will prevent galaxy from cleaning the working directory. This will enable seeing what the job actually produced.</li>
  </ol>
  
  <p>Most likely there's more in the log file that you're not showing is us and picard itself never ran to completion. In lieu of that information, what I wrote above is usually sufficient to debug things.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-03-12T15:44:35.823Z
Answers.Text: Picard was running (exit status was 0 when I set to 1 if there was an error) The log was the same as when I run the command in the terminal. I just excluded the prefix "./" in naming the output and it worked (I guess galaxy add a path to the filename with is not "./" ?).
  Thanks!
Answers.UserDisplayName: aerijman
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-03-12T08:10:23.107Z
Answers.LastActivityDate: 2019-03-12T08:10:23.107Z
Answers.UserDisplayName: Devon Ryan
Body: <p>I am running the Picard tool CollectSequencingArtifactMetrics in galaxy (locally in my pc).</p>
  
  <p>The output files are saved into disk and not passed to <em>stdout</em> and (I guess) they can't be passed as output from picad to galaxy .  </p>
  
  <p>In the xml file I am including:</p>
  
  <pre><code>&lt;outputs&gt;
      &lt;data name='preSummary' format="tabular"  from_work_dir="pref.pre_adapter_summary_metrics"/&gt;
  &lt;/outputs&gt;
  </code></pre>
  
  <p><br><br>
  When I click on <em>View details</em>, in <em>"stderr"</em>, I see: </p>
  
  <blockquote>
    <p>[Mon Mar 11 13:43:07 EDT 2019]
    picard.analysis.artifacts.CollectSequencingArtifactMetrics done.
    Elapsed time: 0.19 minutes. Runtime.totalMemory()=3323461632</p>
  </blockquote>
  
  <p>1 - It looks like it worked but shouldn't I see the highlighted information in <em>"stdout"</em> rather than in the <em>"stderr"</em>?<br>
  2- If it worked, How can I get my output files? I tracked the working directory printing <code>pwd</code> from the <code>&lt;command&gt;</code> but I guess all files are deleted immediately once the picard process has finished.
  <br><br><br></p>
  
  <p>Any idea of what am I doing wrong? </p>
  
  <p>What basic knowledge am I missing here?</p>
  
  <p>Thank you!</p>
  
Tags: <picard><galaxy>
Title: Including Picard tool in galaxy
ThreadText: # Including Picard tool in galaxy
  
  (Asked by: username_0 on 2019-03-11)
  
  I am running the Picard tool CollectSequencingArtifactMetrics in galaxy (locally in my pc).
  
  The output files are saved into disk and not passed to *stdout* and (I guess) they can't be passed as output from picad to galaxy .
  
  In the xml file I am including:
  
  ```
  <outputs>
      <data name='preSummary' format="tabular"  from_work_dir="pref.pre_adapter_summary_metrics"/>
  </outputs>
  
  ```
  
  When I click on *View details*, in *"stderr"*, I see:
  
  > [Mon Mar 11 13:43:07 EDT 2019]
  > picard.analysis.artifacts.CollectSequencingArtifactMetrics done.
  > Elapsed time: 0.19 minutes. Runtime.totalMemory()=3323461632
  
  1 - It looks like it worked but shouldn't I see the highlighted information in *"stdout"* rather than in the *"stderr"*?  
  2- If it worked, How can I get my output files? I tracked the working directory printing `pwd` from the `<command>` but I guess all files are deleted immediately once the picard process has finished.
  
  Any idea of what am I doing wrong?
  
  What basic knowledge am I missing here?
  
  Thank you!
  
  **Tags:** picard, galaxy
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-03-12. Score: 1
  
  1. Picard, like most tools, prints logs to stderr.
  2. It should be in the Galaxy history. Are you using a version of picard from the toolshed (if so, which one)? You might set `cleanup_job` to `never` in the config, which will prevent galaxy from cleaning the working directory. This will enable seeing what the job actually produced.
  
  Most likely there's more in the log file that you're not showing is us and picard itself never ran to completion. In lieu of that information, what I wrote above is usually sufficient to debug things.
  
  > **Comments:**
  > **username_0**: Picard was running (exit status was 0 when I set to 1 if there was an error) The log was the same as when I run the command in the terminal. I just excluded the prefix "./" in naming the output and it worked (I guess galaxy add a path to the filename with is not "./" ?). Thanks!  
  
  ---
  
  