The hardware and bandwidth for this mirror is donated by METANET, the Webhosting and Full Service-Cloud Provider.
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[@]metanet.ch.
Transferring over a code base from Matlab to R is often a repetitive and inefficient use of time. This package provides a translator for Matlab / Octave code into R code. It does some syntax changes, but most of the heavy lifting is in the function changes since the languages are so similar. Options for different data structures and the functions that can be changed are given. The Matlab code should be mostly in adherence to the standard style guide but some effort has been made to accommodate different number of spaces and other small syntax issues. This will not make the code more R friendly and may not even run afterwards. However, the rudimentary syntax, base function and data structure conversion is done quickly so that the maintainer can focus on changes to the design structure.
Version: | 0.4.2 |
Imports: | methods |
Suggests: | knitr, rmarkdown, testthat |
Published: | 2021-05-13 |
DOI: | 10.32614/CRAN.package.matconv |
Author: | Siddarta Jairam [aut, cre], David Hiebeler [ctb] |
Maintainer: | Siddarta Jairam <sidjsb at gmail.com> |
License: | GPL-2 | GPL-3 [expanded from: GPL (≥ 2)] |
NeedsCompilation: | no |
Materials: | README |
CRAN checks: | matconv results |
Reference manual: | matconv.pdf |
Vignettes: |
basic syntax function calls Overall design |
Package source: | matconv_0.4.2.tar.gz |
Windows binaries: | r-devel: matconv_0.4.2.zip, r-release: matconv_0.4.2.zip, r-oldrel: matconv_0.4.2.zip |
macOS binaries: | r-release (arm64): matconv_0.4.2.tgz, r-oldrel (arm64): matconv_0.4.2.tgz, r-release (x86_64): matconv_0.4.2.tgz, r-oldrel (x86_64): matconv_0.4.2.tgz |
Old sources: | matconv archive |
Please use the canonical form https://CRAN.R-project.org/package=matconv to link to this page.
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.