-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #2 from EBI-Metabolights/MTBLS-175-0.2-documentation
Mtbls 175 0.2 documentation
- Loading branch information
Showing
24 changed files
with
192 additions
and
92 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,7 +1,11 @@ | ||
Package: ImperialNMRTool | ||
Type: Package | ||
Title: Tool for Nuclear Magnetic Resonance based spectrography. | ||
Version: 0.0.1.0 | ||
Description: Workflow for automatic processing and annotation of 1D 1H-NMR spectra from MetaboLights repository. | ||
Entrypoint to the workflow is hurricane.r, and it takes an argument which is the location | ||
of a parameters file, which itself contains the location of the files the workflow needs, | ||
and the workflow parameters. To read more visit the github repository at github.com/EBI-Metabolights/icl_nmr_R | ||
Version: 0.2.0.0 | ||
Date: 2022-09-12 | ||
Authors@R: c( | ||
person("Michael T. Judge", "PostDoc / Developer", role = c("aut")), | ||
|
@@ -11,5 +15,4 @@ Maintainer: Callum Martin <[email protected]> | |
Depends: R (>= 4.0.0) | ||
Imports: optparse, BiocManager, stringr, MassSpecWavelet, yaml, pbapply, devtools, batch, flexclust, rlang, pracma, RcppHungarian, grid, lattice, modeltools, stats4 | ||
License: GPL-2 | ||
Description: Workflows for automatic processing and annotation of 1D 1H-NMR spectra from MetaboLights repository. | ||
RoxygenNote: 7.2.1 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2,6 +2,7 @@ | |
|
||
A package 'wrapper' for the tools and functions written by michael judge and goncalo graca, as part of efforts to make the overall NMR pipeline functional in galaxy. | ||
|
||
|
||
## Installation | ||
You can install the package using the R CLI straight from this repository. | ||
|
||
|
@@ -13,4 +14,38 @@ You can install the package using the R CLI straight from this repository. | |
|
||
4 - run `library(ImperialNMRTool)` to load the package into the session. | ||
|
||
To quickly verify if the package is installed you can run `?indsubr` . This will bring up the manual page for this function, and if loaded means that the package itself was installed and loaded successfully. The manual pages for each function contain the information you will need to run them. More detailed instruction may be added to either this repository or the manual pages at a later date. | ||
To quickly verify if the package is installed you can run `??hurricane` . This will bring up the manual page for this function, and if loaded means that the package itself was installed and loaded successfully. The manual pages for each function contain the information you will need to run them. | ||
|
||
## Running the workflow | ||
|
||
If you are runnning this in a normal (non cluster / workflow manager) environment, it is easiest to do so in RStudio. If you have followed the installation steps above, the package is primed to be run. The entrypoint to the package, `ImperialNMRTool::hurricane()` takes one parameter, a params.yaml file. This file needs to be replete with the parameters you want to run the workflow with. This package has some example data that you can make use of, found in `/inst/extdata`. | ||
|
||
### Parameters file | ||
The parameters .yaml file for the workflow takes the following structure: | ||
|
||
|
||
``` | ||
general_pars: | ||
peaks_location: peaks.RDS # location of peaks.RDS file. | ||
spec_location: spec.RDS # location of spec.RDS file. | ||
output_dir: ~/ # tells the workflow where to write the output files. | ||
sd_pars: | ||
cutoff : 0.8 # standard cutoff for STOCSY | ||
am_pars: | ||
rank_limit: 5 # rank limit for exporting matches IE take the top 5 matches discard the rest | ||
dist_thresh: 0.02 # no sense in allowing < precision of db peaks (0.01 ppm for hmdb) | ||
matchMethod: hungarian_scaled # or basic, itmin, hungarian, hungarian_scaled | ||
refdb_file: hmdb_spectra_28FEB2022.RDS # location of reference spectra .RDS file. | ||
vis_pars: | ||
matlab_root: /Applications/MATLAB_R2021b.app/bin # deprecated, will be removed in future release | ||
``` | ||
The four parameters that need to be configured to your local setup in order for the workflow to run are peaks_location, spec_location, output_dor and refdb_file. | ||
|
||
Once this file is prepared, you can run the workflow from RStudio / the command line via `ImperialNMRTool::hurricane("/path/to/your/params.yaml")` | ||
|
||
|
||
#### Help / contact | ||
This repository is maintained by the [MetaboLights](https://www.ebi.ac.uk/metabolights/) team at the EMBL-EBI. You can send any requests or queries to [email protected] , quoting this repository. |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.