Understanding metabolism is fundamental in biomedical and plant research and the identification and quantification of thousands of metabolites by mass spectrometry in modern metabolomics is a prerequisite for elucidating this area. However, the identification of metabolites is a major bottleneck in traditional approaches hampering advances. Here, we present a novel approach for the untargeted discovery of metabolite families offering a bird's eye view of metabolic regulation in comparative metabolomics. We implemented the presented methodology in the easy-to-use web application MetFamily to enable the analysis of comprehensive metabolomics studies for all researchers worldwide. MetFamily is available under http://msbi.ipb-halle.de/MetFamily/.
GNU General Public License v3.0
9
stars
7
forks
source link
Project export can cause bad gateway error corrupting the download #52
Saving a huge project will result in a corrupted file download if the application is deployed in an orchestration system (Kubernetes).
Furthermore, the export takes a lot of time and the end-user can be confused because the R session is not responsible anymore.
Steps to reproduce
Visit metfamilies page, load a huge project (example files are provided) and try to export the project.
Solution
The connection error is caused by a 502 error of the ingress component because the shiny-server is not responsible (the R session does not respond because of its high load).
A better solution would be to preprocess the files that should be exported and then offer a download instead of opening the HTTP connection before.
Issue
Saving a huge project will result in a corrupted file download if the application is deployed in an orchestration system (Kubernetes). Furthermore, the export takes a lot of time and the end-user can be confused because the R session is not responsible anymore.
Steps to reproduce
Visit metfamilies page, load a huge project (example files are provided) and try to export the project.
Solution
The connection error is caused by a 502 error of the ingress component because the shiny-server is not responsible (the R session does not respond because of its high load). A better solution would be to preprocess the files that should be exported and then offer a download instead of opening the HTTP connection before.