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

Running Maxquant on pulsar node #696

Open
mthang opened this issue Dec 13, 2022 · 4 comments
Open

Running Maxquant on pulsar node #696

mthang opened this issue Dec 13, 2022 · 4 comments

Comments

@mthang
Copy link
Contributor

mthang commented Dec 13, 2022

Hi there and @bgruening ,
This is just an PR to Galaxy-P maxquant. Currently, Galaxy Australia has cloned this Maxquant and made some modification to include DotNet and updated the maxquant from 1.6.17 to 2.0.3.0 in our maxquant.xml https://github.com/usegalaxy-au/tools-au/blob/master/tools/maxquant/maxquant.xml , so the maxquant can run on the remote pulsar node. We also increase the size of vm.max_map_count on the pulsar to prevent the tool from crashing.

sed -i -E 's:(maxQuantVersion>)1.6.5.0(<):\1'1.6.17.0'\2:' mqpar.xml

@bgruening
Copy link
Member

Thanks, @mthang for the update. Are you planning to contribute your modifications back to this repo?

@mthang
Copy link
Contributor Author

mthang commented Jan 22, 2023

@bgruening
Yes. GA had this discussion and plan, so we are happy to contribute our modifications back to the repo. Can you please let me know what I need to do ?

Best,
Mike

@bgruening
Copy link
Member

@mthang you push your changes to this repo. The tool wrapper is hosted here and everyone can contribute fixes.

@bgruening
Copy link
Member

@mthang please see #698

Now both versions are diverging I guess.

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