Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Should maxquant tools fail when PXTQC fails? #705

Open
eschen42 opened this issue Mar 20, 2023 · 1 comment
Open

Should maxquant tools fail when PXTQC fails? #705

eschen42 opened this issue Mar 20, 2023 · 1 comment

Comments

@eschen42
Copy link
Contributor

@npinter Whatcha think?

Both maxquant and maxquant_mqpar fail if PTXQC fails. I wonder whether this is appropriate.

In both cases, the command (optionally) ends with running the PTXQC report

    #if $qc.do_it:
        &&
        Rscript '$qr' '$qr_yaml'
        #if 'log' in $output:
            >> '$log' 2>&1
        #end if
        &&
        cp ./combined/txt/report_v@VERSION_PTXQC@_combined.pdf '$ptxqc_report'
    #end if

The trouble is that, even when MaxQuant completes successfully, if PTXQC fails then the MaxQuant results (obtained at great expense of time and computational cost) are not copied back from the cluster.

I would prefer to see something like this (writing freely here, not presenting something tested):

    #if $qc.do_it:
        && (
         (
          Rscript '$qr' '$qr_yaml'
          #if 'log' in $output:
              >> '$log' 2>&1
          #end if
          &&
          cp ./combined/txt/report_v@VERSION_PTXQC@_combined.pdf '$ptxqc_report'
         ) || (echo 'PTXQC report failed: see log')
       )
    #end if

This would allow the user (e.g., me) to salvage PTXQC failures by running PTXQC (which takes a few minute or less rather than several days) separately, outside of Galaxy.

@bernt-matthias
Copy link
Collaborator

My suggestion would be to put the R script in a separate tool.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants