ReDU is a community-minded approach to find and reuse public data containing tandem MS data at the repository scale. ReDU is a launchpad for co- or re-analysis of public data via the Global Natural Product Social Molecular Networking Platform (GNPS). Our aim is to empower researchers to put their data in the context of public data as well as explore questions using public data at the repository scale.
This is a community effort and everyone is encouraged to participate by submitting their own data and sample information instructions. The sharing of new applications (and code) which use ReDU is highly encouraged.
To get ReDU up and running on your local system, it should be as easy as
server-compose-interactive
We have unit tests to test the validators. There are several naming conventions:
valid_*
- These are valid files implying passing validation and finding the same number of files in MassIVEinvalid_*
- These are invalid files that fail validationinvaliddata_*
- These are valid files that pass validation but fail to match with data in MassIVE
To run all unit tests, we are using act to run github actions locally:
make test-push
to simulate a push to the repository and run the full suite of unit tests exactly as we'd run at github.
To simulate selenium and production integration tests:
make test-schedule
- Check number of files avaliable in the File Selector
- Check the humber of unique chemical annotated in Chemical Explorer.
- Check that graphs in Chemical Explorer are functional, available after clicking an example chemical's 'view assocations' button. (e.g.
/compoundenrichmentdashboard?compound=Spectral%20Match%20to%20Sulfachloropyridazine%20from%20NIST14
) - Test all buttons to ensure links are correct.
One of the key steps in ReDU is the updating of the database to include the latest identifications for files within ReDU. These are the following steps:
- Download batch template for GNPS at
https://redu.ucsd.edu/metabatchdump
- Run Batch Workflow for Spectral Library Search
- Get the set of tasks as tsv and save to here.
- Remove database here
- Remove all untracked files in temp, this will be for the global pca
- Start ReDU back up and it will autopopulate
- Wait Until full autopopulate before going to global PCA views