-
Notifications
You must be signed in to change notification settings - Fork 27
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
Add camera new tools #277
base: master
Are you sure you want to change the base?
Add camera new tools #277
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you maybe reformat your tools using 4 spaces.
Please also consider using the https://github.com/galaxyproject/galaxy-language-server it can reformat all your tools automatically and will do the lining for you as well :)
@DamienCode404 @bgruening @yguitton the way how the tool reads input data currently is wrong/broken. Through the image argument, hard-coded paths from the R session get loaded into the Galaxy tool ... this doesn't work. Which data are you using? The output from XCMS fillpeaks or CAMERA annotate? Maybe we can arrange a call to talk about these things and figure them out, then I can help with the implementation. |
Also, more in general, what is the purpose of these new tools? I can see that the existing CAMERA tool also seems to include all of these steps - do you want to split them or whats the plan here? |
Hi @hechth, I'm curious as to why this isn't working. I'm still a beginner with galaxy tools. For the groupFWHM camera tool, we use xcms fillpeaks files as input. For the rest of the tools, we only use camera rdata output. |
The main aim of this tool is, as you said, to split the annotateDiffreport tool into 4 sub-tools. This is to provide users with more options when launching these tools and to skip certain steps if necessary. Also, this method seems to give more consistent results. We expect execution time to decrease as well. |
You should use Rds files storing only a single variable if already using builin R datatypes. This is a serious security vulnerability. If you load an RData file, it might overwrite anything internal. Someone can store an environment where |
Hi Helge ! This choice has been done for all XCMS workflow in W4M since the beginning I think... ! With this we should rework all this workflow that actually works with RData containing multiple variables... Maybe we can ask @lecorguille about it ? Cause here, we just continue the workflow of XCMS in CAMERA, didn't touch the variables saved in RData files. |
@jsaintvanne Yeah I just saw - this is probably something that would make sense to address - maybe also with the update to XCMS 4? |
Currently planemo test fails with the following error message.
|
Yeah we were asking how we will go to XCMS 4, maybe that's a way... !
Think this come from the data test where there is the singlefile variable to keep the link between the cdf filename and their galaxy name and that has been done in local that's why we have this path hardcoded... @DamienCode404 is working on it ! We should maybe discuss about the RData and RDs files and their security cause we can't really see the problem here sorry ! |
…d the correct number of sample columns in tsv output.
Failed to expand inclusions [{'source': 'camera_groupfwhm.xml'}, {'source': 'camera_groupfwhm.r'}]
WARNING: Failed to expand inclusions [{'source': 'camera_groupfwhm.xml'}, {'source': 'camera_groupfwhm.r'}]
Failed Tests RData : Binary data detected, not displaying diff
- Removal of duplicate functions from scripts and lib.r files - Retrieve arguments with the W4MRUtils::parse_args function
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please include your Rscript that you use with "required_files": https://docs.galaxyproject.org/en/latest/dev/schema.html#tool-required-files
|
||
<expand macro="requirements"/> | ||
|
||
<command detect_errors="exit_code"><![CDATA[ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The indentation seems to be off here and makes it hard to read.
I recommend to use the https://github.com/galaxyproject/galaxy-language-server it has an auto-format feature.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For me, the indentation seems correct. I validate the lint steps. I've already indented and formatted the code. Is it just the 4 extra spaces that bother you @bgruening ? In all the other tools I've seen, they all have this style of indentation between <tool></tool>
tags. Maybe I've misunderstood.
…ion delta. - Try to correct conditions (findAdducts) - Gives the right delta to compare test file sizes (groupFWHM).
nSlaves issue with findAdducts. Use of 'xcmsClusterApply' is deprecated! Use 'BPPARAM' arguments instead. Need update of the package CAMERA to parallelize. nSlaves is set by default to 1.
Hello everyone,
This code should display my image in Galaxy, but I have this result : I think it's maybe a problem with the fact that i m developing in a local environment, or because my png files are too big (~55ko). |
Addition of New CAMERA Tools for the Metabolomics Suite
Description:
This PR introduces several new tools to the CAMERA tool suite, used for metabolomics analysis with LC-MS data. These tools complement existing functionalities and enhance peak detection and annotation.
New Tools Added:
camera_groupFWHM:
camera_groupCorr:
camera_findIsotopes:
camera_findAdducts:
Why These Changes?
These new tools provide greater flexibility and modularity for analyzing LC-MS data by breaking down the all-in-one annotateDiffreport tool into four distinct tools. This separation allows users to run specific tasks such as isotope detection, adduct identification, peak grouping by FWHM, or correlation independently. By decoupling these functionalities, users can better customize their workflows based on their needs, making the analysis more efficient and tailored to specific research objectives.
FOR CONTRIBUTOR: