Welcome to POMAShiny!

POMAShiny is an user-friendly web-based workflow for pre-processing and statistical analysis of mass spectrometry data. This tool allows you to analyze your data:

Fast: Analyze and visualize your data easily in few steps

Friendly: POMAShiny provides users a very intuitive structure and a whole interactive analysis

Free: All POMAShiny options are completely open and free for all users


Upload Data

  • Upload your data in the “Upload Data” tab
  • Data must be a CSV (comma-separated-value) file

Target File

A .CSV with two mandatory columns + n optional covariates:

  • Each row denotes a sample (the same as in the features file)
  • First/Left-hand column must be sample IDs => red
  • Second/Left-hand column must be sample group/factor (e.g. treatment) => green
  • Covariates (optional): From the third column (included) users can also include several experiment covariates => purple

Features File

A .CSV with m columns:

  • Each row denotes a sample and each column denotes a feature
  • First row must contain the feature names

More Help and Instructions

Additional help and more detailed instructions are provided in the “Help” panel.


About POMAShiny

POMAShiny has been developed by Pol Castellano-Escuder, Raúl González-Domínguez, Cristina Andrés-Lacueva and Alex Sánchez-Pla at University of Barcelona, Spain.

The source code of POMAShiny is freely available on GitHub at https://github.com/pcastellanoescuder/POMAShiny.

We would appreciate reports of any issues with the app via the GitHub issue tracking at https://github.com/pcastellanoescuder/POMAShiny/issues.


EIB NUTRIMETABOLOMICS CIBERFESpng UBpng


Upload data panel

Exploratory report

After click the button above, go to the Pre-processing step

Target File

Features File

Prepared Data


Missing value imputation

Prepared Data

Imputed Data


Normalization

Not Normalized Data


Outlier detection


Volcano plot parameters


Boxplot parameters


Density plot parameters



Heatmap parameters



Univariate analysis


Multivariate analysis


Cluster analysis


Limma parameters


Correlation parameters



Regularization parameters


Random forest parameters


Rank product parameters


Odds Ratio parameters


Help

Last update: septiembre 28, 2020

Upload Data Panel

In this panel users can upload their data to be analyzed in POMAShiny. Data format must be a CSV (comma-separated-value) file.

Target File

A .CSV with two mandatory columns + n optional covariates:

  • Each row denotes a sample (the same as in the features file)
  • First/Left-hand column must be sample IDs => red
  • Second/Left-hand column must be sample group/factor (e.g. treatment) => green
  • Covariates (optional): From the third column (included) users can also include several experiment covariates => purple

Once this file has been uploaded, users can select desired rows in the “Target File” panel table to create a subset of the whole uploaded data. If this selection is done, only selected rows are analyzed in POMAShiny, if not (default) all uploaded data are analyzed.

Features File

A .CSV with m columns:

  • Each row denotes a sample and each column denotes a feature
  • First row must contain the feature names

Exploratory report

After uploading the data and clicking the “Submit” button, POMAShiny allows users to generate an exploratory data analysis PDF report automatically by clicking the green button with the label “Exploratory report” in the top of the central panel. See a PDF report example here.

Example data

POMAShiny includes two example datasets that are both freely available at https://www.metabolomicsworkbench.org. The first example dataset consists of a targeted metabolomics three-group study and the second example dataset consists of a targeted metabolomics two-group study. These two datasets allow users to explore all available functionalities in POMAShiny. Both dataset documentations are available at https://github.com/pcastellanoescuder/POMA.

NOTE: Once target and features files are uploaded and the desired rows are selected in the target file (if necessary), users must have to click the “Submit” button to continue with the analysis.

Equivalent functions in POMA: POMA::PomaMSnSetClass() (format data) and POMA::PomaEDA() (automatic PDF report).

Pre-processing Panel

Impute Values

Usually, mass spectrometry faces with a high number of missing values, most of them due to low signal intensity of peaks. Missing value imputation process in POMAShiny is divided in three sequential steps:

  1. Distinguish between zeros and missing values. In case of the data have values of these two types users can distinguish or not between them. This option may be useful in experiments combining endogenous and exogenous features, as in this case the exogenous ones could be a real zero (absence) and the endogenous ones are unlikely to be real zeros.

  2. Remove all features of the data that have more of a specific percentage (defined by user) of missing values in ALL study groups. By default this percentage is 20%.

  3. Imputation. POMAShiny offers six different methods to impute missing values:

  • replace missing values by zero
  • replace missing values by half of the minimum positive value in the original data (in each column)
  • replace missing values by the median of the column (feature)
  • replace missing values by the mean of the column (feature)
  • replace missing values by the minimum value in the column (feature)
  • replace missing values using KNN algorithm (default)

Armitage, E. G., Godzien, J., Alonso‐Herranz, V., López‐Gonzálvez, Á., & Barbas, C. (2015). Missing value imputation strategies for metabolomics data. Electrophoresis, 36(24), 3050-3060.

Equivalent function in POMA: POMA::PomaImpute().

Normalization

It’s known that some factors can introduce variability in MS data. Even if the data have been generated under identical experimental conditions, this introduced variability can have a critical influence on the final statistical results, making normalization a key step in the workflow.

POMAShiny offers six different methods to normalize data:

  • Autoscaling
  • Level scaling
  • Log scaling
  • Log transformation
  • Vast scaling
  • Log pareto scaling (default)

van den Berg, R. A., Hoefsloot, H. C., Westerhuis, J. A., Smilde, A. K., & van der Werf, M. J. (2006). Centering, scaling, and transformations: improving the biological information content of metabolomics data. BMC genomics, 7(1), 142.

Users can evaluate the normalization effects in the interactive boxplots located in the “Normalized Data” tab.

Equivalent functions in POMA: POMA::PomaNorm() (normalization) and POMA::PomaBoxplots(group = "samples") (boxplots).

Outlier Detection

POMAShiny allows the analysis of outliers by different plots and tables as well as the possibility to remove statistical outliers from the analysis (default) using different modulable parameters.

The method implemented in POMAShiny is based on the euclidean distances (default but modulable) among observations and their distances to each group centroid in a two-dimensional space. Once this is computed, the classical univariate outlier detection formula _Q3 + 1.5*IQR_ (coefficient is modulable by the user) is used to detect multivariate group-dependant outliers using computed distance to each group centroid.

Select the method (distance), type and coefficient (the higher this value, the less sensitive the method is to outliers) to adapt the outlier detection method to your data. By switching the button “Show labels” all plots display automatically the sample IDs in the outlier detection plots.

  • Distances Polygon Plot: Group centroids and sample coordinates in a two-dimensionality space
  • Distances Boxplot: Boxplots of all computed distances to group centroid by group

NOTE: If the “Remove outliers” button is turned on (default), all detected outliers are excluded from the analysis automatically.

Equivalent functions in POMA: POMA::PomaOutliers(do = "analyze") (analyze outliers) and POMA::PomaOutliers(do = "clean") (remove outliers).

EDA Panel

POMAShiny offers several interactive and highly modulable plots designed to facilitate the exploratory data analysis (EDA) process, giving a wide range of visualization options.

Volcano Plot

In this tab, users can explore their data in an interactive volcano plot. This plot is based on the results of a standard T-test which users can define if data are paired or not and if the study group variances are equal or not. This option is only available for two-group studies.

POMAShiny interactive volcano plot gives users information about T-test significance and fold changes. log2 fold changes between groups are represented in the horizontal axis while -log10 T-test p-values are represented in the vertical axis.

Users can select if raw p-values or adjusted (FDR) p-values are displayed. Other parameters as p-value threshold, log2 fold change threshold or x-axis range are available in the parameters menu.

Equivalent function in POMA: POMA::PomaVolcano().

Boxplot

This tab provides a highly interactive boxplot that shows all data features by their different study groups. Each feature is represented by as many boxplots as there are groups in the study. Different visualization parameters are available in this tab:

  • Features to plot: By default this box is empty because all features are plotted. However, by selecting some specific features in this box, only these features are plotted
  • Show points: By turning on this button, points corresponding to each sample are shown in each feature boxplots. If your data contain many features, this option can slow down the interactive display
  • Split boxes: By default study group boxplots are overlapped in each feature. By turning on this button, study group boxplots are splitted in each feature. Only recommended if features selected to show are not too many (maximum 10 features)

Equivalent functions in POMA: POMA::PomaBoxplots(group = "features") (all features) and POMA::PomaBoxplots(group = "features", feature_name = c("XXX", "YYY", "ZZZ")) (only features XXX, YYY and ZZZ).

Density Plot

POMAShiny provides an interactive density plot to explore all study group distributions (default). However, by turning off the “Plot groups” button, POMAShiny plots the feature distributions indicated by user instead study group distributions.

Equivalent functions in POMA: POMA::PomaDensity() (study groups) and POMA::PomaDensity(group = "features", feature_name = c("XXX", "YYY", "ZZZ")) (only features XXX, YYY and ZZZ).

Heatmap

In this panel POMAShiny offers a classical heatmap as well as a hierarchical clustering with a color stripe that corresponds to each sample group label. Users can display or not sample IDs (not recommended if n is too large) and feature names (not recommended for too many features).

Equivalent function in POMA: POMA::PomaHeatmap().

Statistical Analysis Panel

Univariate Analysis

Univariate analysis is the simplest form of data analysis where the data being analyzed contains only one variable. Since it’s a single variable it doesn’t deal with causes or relationships.

T-test

T-test is a parametric statistical hypothesis test in which the test statistic follows a Student’s t-distribution under the null hypothesis. This analysis is used when you are comparing two groups. This test assumes the normal distribution of features. T-test results can be visualized in the volcano plot provided at EDA panel.

  • Equal Variance (or pooled) T-test: The equal variance T-test is used when the variance of the two tested groups is similar.

  • Unequal Variance T-test: The unequal variance T-test is used when the variance of the two tested groups is different (default). This test is also called Welch’s T-test.

  • Paired T Test: The paired T-test is performed when samples consist of matched pairs of similar units or when there are cases of repeated measures. This method can also applies on cases where the samples are related in some manner or have matching characteristics (default is that groups are not paired).

Equivalent function in POMA: POMA::Univariate(method = "ttest").

ANOVA

The analysis of variance (ANOVA) tests the hypothesis that the averages of two or more groups are the same. The ANOVA evaluates the importance of one or more factors when comparing the means of the response variable in the different levels of the factors. The null hypothesis states that all the means of the groups are the same while the alternative hypothesis states that at least one is different. ANOVA is a parametric method that assumes the normal distribution of features.

If one or more covariates have been included in the target file, an analysis of covariance (ANCOVA) is performed automatically and the results are available at the “ANCOVA Results” tab. The ANCOVA is a general linear model which mix ANOVA and regression. ANCOVA evaluates whether the means of the groups are equal while statistically controlling the effects of other continuous variables that are not of primary interest (as group or treatment), known as covariates.

Equivalent functions in POMA: POMA::Univariate(method = "anova") (ANOVA) and POMA::Univariate(method = "anova", covariates = TRUE) (ANCOVA).

Mann-Whitney U Test

Mann-Whitney U test is the non-parametric alternative test to the independent sample T-test. It’s a non-parametric test that is used to compare two group means that come from the same population, and used to test whether two sample means are equal or not. Usually, the Mann-Whitney U test is used when the assumptions of the T-test are not met. When the study groups are paired, this test becomes a Wilcoxon signed-rank test.

Equivalent function in POMA: POMA::Univariate(method = "mann").

Kruskal Wallis Test

Kruskal-Wallis test is a non-parametric alternative to ANOVA. It is an extension of the Mann-Whitney U test for 3 or more groups. Kruskal-Wallis test does not assume normality in the data, as opposed to the traditional ANOVA.

Equivalent function in POMA: POMA::Univariate(method = "kruskal").

Multivariate Analysis

Unlike univariate methods, multivariate methods are focused in the study of more than one feature at a time. These type of approaches have been widely used because their informativeness. Since being more complex than conventional univariate statistics, these methods can provide information about the structure of the data and different internal relationships that would not be observed with univariate statistics. However, the interpretation of these type of analysis can be more complex.

PCA (principal component analysis)

PCA is one of the most used methods for data dimension reduction. POMAShiny allows users to compute a PCA controlling different parameters:

  • Number of components: This number indicates the number of components that are calculated
  • Scale and Center: By default these parameters are disabled. If the data have been normalized
  • Show ellipses: By turning on this button, the ellipses computed assuming a multivariate normal distribution are drawn in a score plot and biplot

Equivalent function in POMA: POMA::PomaMultivariate(method = "pca").

PLS-DA (partial least squares discriminant analysis)

PLS-DA is a supervised method that uses the multiple linear regression method to find the direction of maximum covariance between the data and the sample group. POMAShiny allows users to compute a PLS-DA controlling different parameters:

  • Number of components: This number indicates the number of components that are calculated
  • VIP cutoff: This value indicates the variable importance in the projection (VIP) cutoff. Features shown in the VIP plot tab are based on this value. Only features with a VIP higher than this value are shown in the plot. This is a reactive option, it means that users doesn’t have to recalculate a PLS-DA to change this value, it can be changed and the VIP plot are updated automatically without doing anything more
  • Show ellipses: By turning on this button (default), the ellipses computed assuming a multivariate normal distribution are drawn in a score plot
  • Validation type: Internal validation to use, options are “Mfold” (default) or “Leave One Out”
  • Number of folds: Number of folds for Mfold validation method (default is 5). If the validation method is loo, this value will become to 1
  • Number of iterations for validation process: Number of iterations for the validation method selected

Equivalent function in POMA: POMA::PomaMultivariate(method = "plsda").

sPLS-DA (sparse partial least squares discriminant analysis)

Often, sPLS-DA method is used to classify samples (supervised analysis) and to select features. POMAShiny allows users to compute a sPLS-DA controlling different parameters:

  • Number of components: This number indicates the number of components that are calculated
  • Number of features: The number of features to keep in the model
  • Show ellipses: By turning on this button (default), the ellipses computed assuming a multivariate normal distribution are drawn in a score plot
  • Validation type: Internal validation to use, options are “Mfold” (default) or “Leave One Out”
  • Number of folds: Number of folds for Mfold validation method (default is 5). If the validation method is loo, this value will become to 1
  • Number of iterations for validation process: Number of iterations for the validation method selected

Equivalent function in POMA: POMA::PomaMultivariate(method = "splsda").

Cluster Analysis

Cluster analysis is also a multivariate method like the previous ones. However, it’s in a separate section only to make the app and the analysis more understandable. POMAShiny allows users to compute easily a cluster analysis using the k-means algorithm.

k-means

k-means is an unsupervised method that aims to assign each sample of the study to one of k clusters based on the sample means and the nearest cluster centroid. POMAShiny calclulates the optimum number of clusters (k) using the elbow method. Different parameters are available for the calculation and visualization of clusters.

  • Method: Distance used to calculate multi dimensional scaling (MDS)
  • Number of clusters among which the optimal one will be selected: The total number of clusters to compute to select the optimal one. In POMAShiny, this value is selected using the “elbow” method
  • Number of clusters (k): Number of clusters that are calculated. By default this value is the optimal number of clusters computed by POMAShiny. However, by changing this value, the k selected by user is used
  • Show clusters: k different clusters are projected in the MDS plot. By turning off this button a simple MDS plot are displayed
  • Show labels: By turning on this button sample IDs are shown in the plot. If this option is enabled, an additional button is displayed:
    • Show group: By turning on this option, sample IDs are replaced by group labels

Equivalent function in POMA: POMA::PomaClust().

MDS (multi dimensional scaling)

Since k-means is a multivariate method, POMAShiny uses the two first dimensions of a classical MDS to project the computed clusters. By turning off the “Show clusters” button, users visualize a plain MDS plot. Labeling options are the same for both scenarios.

Both two first dimensions of MDS and calculated k clusters are available in the “Cluster Table” tab.

Equivalent function in POMA: POMA::PomaClust(show_clusters = FALSE).

Limma

Limma (Linear Models for Microarray Data) was created for the statistical analysis of gene expression experiments as microarrays. However, over the last years this method has been user in many other omics such as metabolomics or proteomics.

Limma performs a single-sample T-test using an empirical Bayes method to borrow information between all features. This method “leverages the highly parallel nature of features to borrow strength between the feature-wise models, allowing for different levels of variability between features and between samples, and making statistical conclusions more reliable when the number of samples is small”. See Ritchie, M. E., Phipson, B., Wu, D., Hu, Y., Law, C. W., Shi, W., & Smyth, G. K. (2015). limma powers differential expression analyses for RNA-sequencing and microarray studies. Nucleic acids research, 43(7), e47-e47..

POMAShiny allows users to compute limma models and the possibility to adjust these models by different covariates (if they have been included in the target file). The POMAShiny limma results are displayed in an interactive volcano plot at Limma’s “Volcano Plot” tab.

Equivalent functions in POMA: POMA::PomaLimma() (without covariates) and POMA::PomaLimma(covariates = TRUE) (with covariates).

Correlation Analysis

POMAShiny provides different options to conduct an accurate and interactive correlation analysis. In the “Correlation parameters” menu users can select the correlation method (pearson, spearman or kendall) to be used for all available visualizations explained below.

Pairwise Correlation Scatterplot

POMAShiny provides a highly modulable and interactive scatterplot of pairwise correlation between features. Here, users can select two desired features and explore them in a very comfortable way, being able to remove some points of the plot by clicking over, drawing a smoth line based on a linear model, showing the sample IDs instead of points or exploring and comparing pairwise correlations within each study group (factor).

Pairwise Correlation Table

A table with all pairwise correlations in the data. This table can be sorted by all different columns and it can be downloaded in different formats.

Equivalent function in POMA: POMA::PomaCorr()

Correlogram

A global correlation plot or correlogram is provided in this tab. This plot allows users to visualize all correlations in the data at once. Users can control the label size by clicking in the upper left corner menu.

Equivalent function in POMA: POMA::PomaCorr()

Correlation Network

POMAShiny offers a correlation network visualization, where correlations between features can be observed in a very clear way. Only pairs of features with a correlation absolute value over “Correlation Cutoff” indicated in the upper left corner menu are shown.

Equivalent function in POMA: POMA::PomaCorr()

Gaussian Graphical Models

POMAShiny provides an alternative method for correlation network visualization. Estimation of gaussian graphical models through glasso R package is provided in this tab. Users can define the regularizarion parameter to estimate an sparse inverse correlation matrix using lasso in the upper left corner menu.

Equivalent function in POMA: PomaCorr(corr_type = "glasso")

Regularization

POMAShiny offers three different wide used regularization methods both for feature selection and prediction model creation purposes. These methods are lasso, ridge regression and elasticnet. All of these methods are based on penalized logistic regression and are therefore only available for two-group studies. If the purpose is not predictive, users can set the test parameter to zero. Otherwise, if the purpose is to build a predictive model, users can select the proportion (%) of samples that are used as a test set.

  • Test partition (%): Percentage of observations that are used as test set. These samples are used only to perform an external validation. If this value is set to zero, all samples are used to create the model and no external validation is computed
  • Internal CV folds: Number of folds for CV (default is 10). This value can be as large as the sample size (leave-one-out CV), it is not recommended for large datasets. Smallest value allowable 3
  • Elasticnet Mixing Parameter (only for elasticnet): This value corresponds to the alpha (or penalty) parameter

Equivalent functions in POMA: POMA::PomaLasso(alpha = 1) (lasso), POMA::PomaLasso(alpha = 0) (ridge) and POMA::PomaLasso(alpha = 0.5) (elasticnet; alpha range from >0 to <1).

Random Forest

Random forest is a widely used machine learning algorithm in different omics for the purpose of creating prediction models. POMAShiny provides a classification random forest algorithm designed to create prediction models to discriminate between two or more study groups. Different parameters are available in this panel:

  • Test partition (%): Percentage of observations that are used as test set. Default is 20% of observations. These samples are used only to perform an external validation
  • Number of trees: Number of trees to grow
  • Number of variables randomly sampled as candidates at each split
  • Node Size: Minimum size of terminal nodes
  • Number of Selected Features: Number of features that are shown in the Gini plot

Equivalent function in POMA: POMA::PomaRandForest()

Rank Products

The rank product is a biologically motivated test for the detection of differential expressed/concentrated features in high throughput experiments. It’s a non-parametric statistical method based on the ranks of fold changes. Over the last years this methodology has become popular in many omics fields such as transcriptomics, metabolomics and proteomics.

Rank product test in POMAShiny skips the normalization and outlier detection steps to avoid possible negative values generated in the normalization process. Consequently, this method is based on the imputed data and all samples will be used to perform the analysis. If the user wants to remove some detected outliers from this test, it’s possible to select all samples except the detected outliers in the Upload Data panel -> Target File tab table and repeat the imputation step.

In the Rank Products panel, users can select if their data is paired or not and the possibility to apply a log2 transformarion over each feature (default). Also the method to perform the test (percentage of false prediction or p-value) and the cutoff can be modulated by users. For more details see Del Carratore, F., Jankevics, A., Eisinga, R., Heskes, T., Hong, F., Breitling, and R. (2017) RankProd 2.0: a refactored Bioconductor package for detecting differentially expressed features in molecular profiling datasets. Bioinformatics, 33, 2774–2775.

Equivalent function in POMA: POMA::PomaRankProd().

Odds Ratio

In the Odds Ratio panel users can calculate the odds ratios (OR) ans its confidence intervals based on a logistic regression model. Consequently, this panel allows only two group datasets. By default, all OR are computed. However, users can select specific features in “Select model features” box.

To include confidence intervals in the plot switch on the “Show CI” button and to include ALL covariates uploaded in the target file in the logistic regression model and in the plot, switch on the “Include covariates” button.

Equivalent function in POMA: POMA::PomaOddsRatio().


POMA R/Bioconductor Package

POMAShiny is whole based on POMA R/Bioconductor package. POMA introduces a structured, reproducible and easy-to-use workflow for the visualization, pre-processing, exploratory and statistical analysis of mass spectrometry data. The main aim of POMA is to enable a flexible data cleaning and statistical analysis processes in one comprehensible and user-friendly R package. This package uses the standardized MSnbase data structures, to achieve the maximum flexibility and reproducibility and makes POMA compatible with pre-existing Bioconductor packages. To get an overview of the package, see the POMA workflow vignette at https://pcastellanoescuder.github.io/POMA/articles/POMA-demo.html.

Citation

Castellano-Escuder P, González-Domínguez R, Andrés-Lacueva C, Sánchez-Pla A (2020). POMA: User-friendly Workflow for Pre-processing and Statistical Analysis of Mass Spectrometry Data. R package version 0.99.40, https://github.com/pcastellanoescuder/POMA.


Software License

                GNU GENERAL PUBLIC LICENSE
                   Version 3, 29 June 2007

Copyright (C) 2007 Free Software Foundation, Inc. https://fsf.org/ Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

                        Preamble

The GNU General Public License is a free, copyleft license for software and other kinds of works.

The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program–to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things.

To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.

Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it.

For the developers’ and authors’ protection, the GPL clearly explains that there is no warranty for this free software. For both users’ and authors’ sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions.

Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users’ freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users.

Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free.

The precise terms and conditions for copying, distribution and modification follow.

                   TERMS AND CONDITIONS
  1. Definitions.

“This License” refers to version 3 of the GNU General Public License.

“Copyright” also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.

“The Program” refers to any copyrightable work licensed under this License. Each licensee is addressed as “you”. “Licensees” and “recipients” may be individuals or organizations.

To “modify” a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a “modified version” of the earlier work or a work “based on” the earlier work.

A “covered work” means either the unmodified Program or a work based on the Program.

To “propagate” a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well.

To “convey” a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying.

An interactive user interface displays “Appropriate Legal Notices” to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion.

  1. Source Code.

The “source code” for a work means the preferred form of the work for making modifications to it. “Object code” means any non-source form of a work.

A “Standard Interface” means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language.

The “System Libraries” of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A “Major Component”, in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it.

The “Corresponding Source” for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work’s System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.

The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.

The Corresponding Source for a work in source code form is that same work.

  1. Basic Permissions.

All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.

You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you.

Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.

  1. Protecting Users’ Legal Rights From Anti-Circumvention Law.

No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures.

When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work’s users, your or third parties’ legal rights to forbid circumvention of technological measures.

  1. Conveying Verbatim Copies.

You may convey verbatim copies of the Program’s source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.

You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.

  1. Conveying Modified Source Versions.

You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions:

a) The work must carry prominent notices stating that you modified
it, and giving a relevant date.

b) The work must carry prominent notices stating that it is
released under this License and any conditions added under section
7.  This requirement modifies the requirement in section 4 to
"keep intact all notices".

c) You must license the entire work, as a whole, under this
License to anyone who comes into possession of a copy.  This
License will therefore apply, along with any applicable section 7
additional terms, to the whole of the work, and all its parts,
regardless of how they are packaged.  This License gives no
permission to license the work in any other way, but it does not
invalidate such permission if you have separately received it.

d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your
work need not make them do so.

A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an “aggregate” if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation’s users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate.

  1. Conveying Non-Source Forms.

You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways:

a) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium
customarily used for software interchange.

b) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
written offer, valid for at least three years and valid for as
long as you offer spare parts or customer support for that product
model, to give anyone who possesses the object code either (1) a
copy of the Corresponding Source for all the software in the
product that is covered by this License, on a durable physical
medium customarily used for software interchange, for a price no
more than your reasonable cost of physically performing this
conveying of source, or (2) access to copy the
Corresponding Source from a network server at no charge.

c) Convey individual copies of the object code with a copy of the
written offer to provide the Corresponding Source.  This
alternative is allowed only occasionally and noncommercially, and
only if you received the object code with such an offer, in accord
with subsection 6b.

d) Convey the object code by offering access from a designated
place (gratis or for a charge), and offer equivalent access to the
Corresponding Source in the same way through the same place at no
further charge.  You need not require recipients to copy the
Corresponding Source along with the object code.  If the place to
copy the object code is a network server, the Corresponding Source
may be on a different server (operated by you or a third party)
that supports equivalent copying facilities, provided you maintain
clear directions next to the object code saying where to find the
Corresponding Source.  Regardless of what server hosts the
Corresponding Source, you remain obligated to ensure that it is
available for as long as needed to satisfy these requirements.

e) Convey the object code using peer-to-peer transmission, provided
you inform other peers where the object code and Corresponding
Source of the work are being offered to the general public at no
charge under subsection 6d.

A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work.

A “User Product” is either (1) a “consumer product”, which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, “normally used” refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product.

“Installation Information” for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made.

If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).

The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.

Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.

  1. Additional Terms.

“Additional permissions” are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.

When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.

Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:

a) Disclaiming warranty or limiting liability differently from the
terms of sections 15 and 16 of this License; or

b) Requiring preservation of specified reasonable legal notices or
author attributions in that material or in the Appropriate Legal
Notices displayed by works containing it; or

c) Prohibiting misrepresentation of the origin of that material, or
requiring that modified versions of such material be marked in
reasonable ways as different from the original version; or

d) Limiting the use for publicity purposes of names of licensors or
authors of the material; or

e) Declining to grant rights under trademark law for use of some
trade names, trademarks, or service marks; or

f) Requiring indemnification of licensors and authors of that
material by anyone who conveys the material (or modified versions of
it) with contractual assumptions of liability to the recipient, for
any liability that these contractual assumptions directly impose on
those licensors and authors.

All other non-permissive additional terms are considered “further restrictions” within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.

If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.

Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.

  1. Termination.

You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).

However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation.

Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice.

Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.

  1. Acceptance Not Required for Having Copies.

You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so.

  1. Automatic Licensing of Downstream Recipients.

Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License.

An “entity transaction” is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party’s predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.

You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.

  1. Patents.

A “contributor” is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor’s “contributor version”.

A contributor’s “essential patent claims” are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, “control” includes the right to grant patent sublicenses in a manner consistent with the requirements of this License.

Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor’s essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version.

In the following three paragraphs, a “patent license” is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To “grant” such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party.

If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. “Knowingly relying” means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient’s use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid.

If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it.

A patent license is “discriminatory” if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.

Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law.

  1. No Surrender of Others’ Freedom.

If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program.

  1. Use with the GNU Affero General Public License.

Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such.

  1. Revised Versions of this License.

The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License “or any later version” applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation.

If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy’s public statement of acceptance of a version permanently authorizes you to choose that version for the Program.

Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version.

  1. Disclaimer of Warranty.

THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

  1. Limitation of Liability.

IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

  1. Interpretation of Sections 15 and 16.

If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee.

                 END OF TERMS AND CONDITIONS

        How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the “copyright” line and a pointer to where the full notice is found.

<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year>  <name of author>

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program.  If not, see <https://www.gnu.org/licenses/>.

Also add information on how to contact you by electronic and paper mail.

If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode:

<program>  Copyright (C) <year>  <name of author>
This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
This is free software, and you are welcome to redistribute it
under certain conditions; type `show c' for details.

The hypothetical commands show w' and show c' should show the appropriate parts of the General Public License. Of course, your program’s commands might be different; for a GUI interface, you would use an “about box”.

You should also get your employer (if you work as a programmer) or school, if any, to sign a “copyright disclaimer” for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see https://www.gnu.org/licenses/.

The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read https://www.gnu.org/licenses/why-not-lgpl.html.


Code of Conduct

Please note that the POMAShiny is an open source project released with the Contributor Code of Conduct attached below. By contributing to this project, you agree to abide by its terms.


Contributor Covenant Code of Conduct

Our Pledge

We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.

Our Standards

Examples of behavior that contributes to a positive environment for our community include:

  • Demonstrating empathy and kindness toward other people
  • Being respectful of differing opinions, viewpoints, and experiences
  • Giving and gracefully accepting constructive feedback
  • Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
  • Focusing on what is best not just for us as individuals, but for the overall community

Examples of unacceptable behavior include:

  • The use of sexualized language or imagery, and sexual attention or advances of any kind
  • Trolling, insulting or derogatory comments, and personal or political attacks
  • Public or private harassment
  • Publishing others’ private information, such as a physical or email address, without their explicit permission
  • Other conduct which could reasonably be considered inappropriate in a professional setting

Enforcement Responsibilities

Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.

Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.

Scope

This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.

Enforcement

Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at [INSERT CONTACT METHOD]. All complaints will be reviewed and investigated promptly and fairly.

All community leaders are obligated to respect the privacy and security of the reporter of any incident.

Enforcement Guidelines

Community leaders will follow these Community Impact Guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:

1. Correction

Community Impact: Use of inappropriate language or other behavior deemed unprofessional or unwelcome in the community.

Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.

2. Warning

Community Impact: A violation through a single incident or series of actions.

Consequence: A warning with consequences for continued behavior. No interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.

3. Temporary Ban

Community Impact: A serious violation of community standards, including sustained inappropriate behavior.

Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

4. Permanent Ban

Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.

Consequence: A permanent ban from any sort of public interaction within the community.

Attribution

This Code of Conduct is adapted from the Contributor Covenant, version 2.0, available at https://www.contributor-covenant.org/version/2/0/ code_of_conduct.html.

Community Impact Guidelines were inspired by Mozilla’s code of conduct enforcement ladder.

For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https:// www.contributor-covenant.org/translations.


Contact

Report a bug:

For any issue related to the web app, we encourage users to use the GitHub issue chanel. You can access it at the top of this page or at the link: https://github.com/pcastellanoescuder/POMAShiny/issues

Other questions:

For any other questions, please contact: