The hardware and bandwidth for this mirror is donated by dogado GmbH, the Webhosting and Full Service-Cloud Provider. Check out our Wordpress Tutorial.
If you wish to report a bug, or if you are interested in having us mirror your free-software or open-source project, please feel free to contact us at mirror[@]dogado.de.
jmvReadWriteThe R-package jmvReadWrite reads and writes the
.omv-files that are used by the statistical spreadsheet
jamovi (https://www.jamovi.org). It is supposed to ease using
jamovi and R together, provide helper functions for some often required
data management tasks, and to adjust and use syntax for statistical
analyses that were created using the GUI in jamovi in R (in
connection with the R-library jmv). More recently,
jmvReadWrite became easily available from within
jamovi by becoming part of the Rj module
(where you can use it by writing R commands, documented below), and via
the jTransform module that provides a graphical user
interface for most helper functions.
In R, you can either install a stable version of
jmvReadWrite which is available on CRAN using
the following command:
or you can install the development version of the
jmvReadWrite package from GitHub:
The following code uses the ToothGrowth-data set that is part of the
data sets included in R (the current file contains some modifications
though for testing the reading and writing routines:
read_omv and write_omv). With this data set, a
syntax to conduct an ANOVA is run.
The results should be similar to those obtained when running the same
analysis in jamovi (using the GUI). To do so, open the file menu (☰)
choose Open, Data Library and
ToothGrowth. Afterwards, click on the
ANOVA-button in the Analyses-tab and choose
ANOVA. There, you assign the variable len to
Dependent Variable and supp and
dose to Fixed Factors. Afterwards, you choose
/ tick Overall Model Test and ω². Open the
drop-down menu Assumption Checks and tick
Homogeneity test and Normality test. The
results should be identical apart from that the table output looks nicer
in jamovi (not only text, as below), numbers are rounded
and maybe one or two other cosmetic differences.
If you want to copy the syntax generated in jamovi, you have to
switch on the Syntax Mode.
Afterwards, the syntax is shown at the top of the analysis and can be
copied from there.
fleOMV <- system.file("extdata", "ToothGrowth.omv", package = "jmvReadWrite")
data <- jmvReadWrite::read_omv(fleOMV)
# if the "jmv"-package is installed, we can run a test analysis with the data
if ("jmv" %in% rownames(installed.packages())) {
jmv::ANOVA(
formula = len ~ supp + dose + supp:dose,
data = data,
effectSize = c("omega"),
modelTest = TRUE,
homo = TRUE,
norm = TRUE)
}
#>
#> ANOVA
#>
#> ANOVA - len
#> ────────────────────────────────────────────────────────────────────────────────────────────────
#> Sum of Squares df Mean Square F p ω²
#> ────────────────────────────────────────────────────────────────────────────────────────────────
#> Overall model 2740.1033 5 548.02067 41.557178 < .0000001
#> supp 205.3500 1 205.35000 15.571979 0.0002312 0.0554519
#> dose 2426.4343 2 1213.21717 91.999965 < .0000001 0.6925788
#> supp:dose 108.3190 2 54.15950 4.106991 0.0218603 0.0236466
#> Residuals 712.1060 54 13.18715
#> ────────────────────────────────────────────────────────────────────────────────────────────────
#>
#>
#> ASSUMPTION CHECKS
#>
#> Homogeneity of Variances Test (Levene's)
#> ────────────────────────────────────────
#> F df1 df2 p
#> ────────────────────────────────────────
#> 1.940130 5 54 0.1027298
#> ────────────────────────────────────────
#>
#>
#> Normality Test (Shapiro-Wilk)
#> ─────────────────────────────
#> Statistic p
#> ─────────────────────────────
#> 0.9849884 0.6694242
#> ─────────────────────────────Since version 0.2.0, read_omv
also extracts the syntax from analyses that you may have conducted in
the jamovi-GUI and that are stored in the .omv-file. To extract them,
you have to set the parameter getSyn = TRUE when calling read_omv
(default is FALSE). When the parameter is set, the analyses
are stored in the attribute syntax. They can be used as
shown in the following examples:
fleOMV <- system.file("extdata", "ToothGrowth.omv", package = "jmvReadWrite")
data <- jmvReadWrite::read_omv(fleOMV, getSyn = TRUE)
# shows the syntax of the analyses from the .omv-file
# please note that syntax extraction may not work on all systems
# if the syntax couldn't be extracted, an empty list (length = 0) is returned,
# otherwise, the syntax of the analyses from the .omv-file is shown and
# the commands of the first and the second analysis are run, with the
# output of the second analysis assigned to the variable result
if (length(attr(data, "syntax")) >= 2) {
attr(data, "syntax")
# if the "jmv"-package is installed, we can run the analyses in "syntax"
if ("jmv" %in% rownames(installed.packages())) {
eval(parse(text = attr(data, "syntax")[[1]]))
eval(parse(text = paste0("result = ", attr(data, "syntax")[[2]])))
names(result)
# -> "main" "assump" "contrasts" "postHoc" "emm"
# (the names of the five output tables)
}
}
#> [1] "main" "assump" "contrasts" "postHoc" "emm" "residsOV"The jmvReadWrite-package also enables you to write
.omv-files in order to use them in jamovi.
Let’s assume that you have a large collection of log-files (e.g., from
an experiment) that you compile and process (summarize, filter, etc.) in
R in order to later analyse them in jamovi. You will have
those processed log-files stored in a data frame (called, e.g.,
data) which you then write to a file that you can open in
jamovi afterwards.
# use the data set "ToothGrowth" and, if it exists, write it as jamovi-file
# using write_omv()
data("ToothGrowth", package = "jmvReadWrite")
# "retDbg" has to be set in order to return debug information to wrtDta
wrtDta <- jmvReadWrite::write_omv(ToothGrowth, "Trial.omv", retDbg = TRUE)
names(wrtDta)
#> [1] "mtaDta" "xtdDta" "dtaFrm"
# -> "mtaDta" "xtdDta" "dtaFrm"
# this debug information contains a list with the metadata ("mtaDta", e.g.,
# column and data type), the extended data ("xtdDta", e.g., variable lables),
# and the data frame (dtaFrm) for checking (understanding the file format) and
# debugging
# check whether the file was written to the disk, get the file information (size, etc.)
# and delete the file afterwards
list.files(".", "Trial.omv")
#> [1] "Trial.omv"
file.info("Trial.omv")
#> size isdir mode mtime ctime
#> Trial.omv 2617 FALSE 644 2024-11-09 22:23:04 2024-11-09 22:23:04
#> atime uid gid uname grname
#> Trial.omv 2024-11-09 22:23:04 87448 4601 sje025 ansatt
unlink("Trial.omv")Although jamovi reads R-data files (.RData, .rda, .rds) write_omv
permits to store jamovi-specific attributes (such as
variable labels) in addition. Please note that if you are reading from
an .omv-file in order to write back to an
.omv-file (perhaps after some modifications), it is
recommended to leave the sveAtt-attribute set to
TRUE (which is the default).
# reading and writing a file with the "sveAtt"-parameter permits you to keep
# essential meta-data to ensure that the written file looks and works like the
# original file (plus you modifications)
fleOMV <- system.file("extdata", "ToothGrowth.omv", package = "jmvReadWrite")
data <- jmvReadWrite::read_omv(fleOMV, sveAtt = TRUE)
# shows the names of the attributes for the whole data set (e.g., number of
# rows and columns) and the names of the attributes of the first column
names(attributes(data))
#> [1] "names" "row.names" "class" "fltLst" "removedRows"
#> [6] "addedRows" "transforms"
names(attributes(data[[1]]))
#> [1] "name" "id" "columnType" "dataType"
#> [5] "measureType" "formula" "formulaMessage" "parentId"
#> [9] "width" "type" "importName" "description"
#> [13] "transform" "edits" "missingValues" "filterNo"
#> [17] "active"
#
# perhaps do some modifications to the file here and write it back afterwards
jmvReadWrite::write_omv(data, "Trial.omv")
unlink("Trial.omv")If Trial.omv in the example above would have been kept,
it should look like the original file (plus your possible
modifications). If you, e.g., added a new column, you could adjust some
attributes (e.g., to enforce a specific columnType or
measurementType): just look at how attributes are stored
for other columns.
Helper functions
jmvReadWrite contains a number of helper functions that
assist you with data management tasks that are frequently required:
arrange_cols_omv:
Re-arranges the columns of your data file in a requested order.
convert_to_omv:
Converts data sets from other file formats into jamovi-format. This
function may be helpful if you have to convert a larger amount of
files.
describe_omv:
Adds a title and a description to a data set. This function may be
helpful for documenting what is contained in a data set, e.g. for
publishing them in a repository such as OSF, or for generated data sets,
e.g. those used in teaching.
distances_omv:
Calculates a wide range of distances measures (for continuous, frequency
or binary data). If can be determined, whether the calculation of the
distances should be carried out between columns / variables or between
rows / units of observation. The original data can be standardized
before the distances are calculated.
long2wide_omv:
Converts a data set from long to wide format: Time points for repeated
measurements are arranged as rows in the original and converted into
columns.
wide2long_omv:
Converts a data set from wide to long format: Time points for repeated
measurements are arranged as columns in the original and converted into
rows.
merge_cols_omv:
Add variables from several data sets, i.e. the variables / columns in
the second, etc. input data set are added as columns to the first data
set.
merge_rows_omv:
Add cases from several data sets, i.e. the cases / rows in the second,
etc. data set are added as rows to the first data set.
sort_omv:
Sort a data set according to one or more variable(s).
transform_vars_omv:
Transform skewed variables (aiming at they better conform to a normal
distribution).
transpose_omv:
Transpose a data set: Make rows into columns and vice versa.
These binaries (installable software) and packages are in development.
They may not be fully stable and should be used with caution. We make no claims about them.
Health stats visible at Monitor.