Matlab: MATLAB client for remote or local MATLAB access
In R.matlab: Read and Write MAT Files and Call MATLAB from Within R
Matlab R Documentation
MATLAB client for remote or local MATLAB access
Description
Package: R.matlab
Class Matlab
Object
~~|
~~+--Matlab
Directly known subclasses:
public static class Matlab
extends Object
Usage
Matlab(host="localhost", port=9999, remote=!(host %in% c("localhost", "127.0.0.1")))
Arguments
host
Name of host to connect to.
port
Port number on host to connect to.
remote
If TRUE, all data to and from the MATLAB server will
be transferred through the socket connection, otherwise the data will
be transferred via a temporary file.
Fields and Methods
Methods:
as.character Gets a string describing the current MATLAB connection.
close Closes connection to MATLAB server.
evaluate Evaluates a MATLAB expression.
finalize (internal) Finalizes the object if deleted.
getOption Gets the value of an option.
getVariable Gets one or several MATLAB variables.
isOpen Checks if connection to the MATLAB server is open.
open Tries to open a connection to the MATLAB server.
readResult (internal) Reads results from the MATLAB server.
setFunction Defines a MATLAB function.
setOption Sets the value of an option.
setVariable Sets one or several MATLAB variables.
setVerbose Sets the verbose level to get more details about the MATLAB access.
startServer Static method which starts a MATLAB server.
writeCommand (internal) Writes (sends) an R-to-MATLAB command to the MATLAB server.
Methods inherited from Object:
$, $<-, [[, [[<-, as.character, attach, attachLocally, clearCache, clearLookupCache, clone, detach, equals, extend, finalize, getEnvironment, getFieldModifier, getFieldModifiers, getFields, getInstantiationTime, getStaticInstance, hasField, hashCode, ll, load, names, objectSize, print, save
Requirements
In order for R to communicate with MATLAB, MATLAB v6 or higher is
needed. It will not work with previous versions, because they
do not support Java.
We use the term server to say that MATLAB acts like a server
with regard to R. Note that it a standard MATLAB session that runs.
Also, the starting of the MatlabServer is simpler from MATLAB v7,
although it is pretty straightforward for MATLAB v6 too.
It is easier in MATLAB v7 and above, because the Java class required
for remote-data-transfer can be automatically/dynamically added to
the MATLAB Java classpath, whereas for MATLAB v6 it has to be
added manually (see below).
Remote and non-remote connections
When a remote connection (argument remote = TRUE) is used,
data is send to and from MATLAB via a data stream. This is needed
when R is running on a host with a separated file system than
the one MATLAB is running on.
If not connection "remotely" (remote = FALSE), data is
communicated via the file system, that is, by saving and reading
it to temporary MAT files.
Troubleshooting: If "remote" transfers are used, the
InputStreamByteWrapper Java class must be found by MATLAB,
otherwise an error will occur in MATLAB as soon as data is
send from R to MATLAB. In all other cases, the above Java class
is not needed.
Starting the MATLAB server from within R
The MATLAB server may be started from within R by
calling Matlab$startServer(). By default 'matlab' is called
if named differently set options(matlab = "matlab6.5"), say.
The method is experimental and may not work on your system.
By default the MATLAB server listens for connections on port 9999.
For other ports, set argument port, e.g.
Matlab$startServer(port = 9998).
Note that the code will not halt and wait for MATLAB to get
started. Thus, you have to make sure you will wait long enough for
the server to get up and running before the R client try to
connect. By default, the client will try once a second for 30 seconds
before giving up.
Moreover, on non-Windows systems, the above command will start MATLAB
in the background making all MATLAB messages be sent to the R output
screen.
In addition, the method will copy the MatlabServer.m and
InputStreamByteWrapper.class files to the current directory
and start MATLAB from there.
Starting the MATLAB server without R
If the above does not work, the MATLAB server may be started manually
from MATLAB itself. Please follow the below instructions carefully.
To be done once:
In MATLAB, add the path to the directory where MatlabServer.m sits.
See help pathtool in MATLAB on how to do this.
In R you can type system.file("externals", package = "R.matlab")
to find out the path to MatlabServer.m.
For MATLAB v6 only: Contrary to MATLAB v7 and above, MATLAB v6
cannot find the InputStreamByteWrapper class automatically. Instead,
the so called Java classpath has to be set manually. In MATLAB, type
which('classpath.txt') to find where the default
MATLAB classpath.txt file is located. Copy this file to the
current directory, and append the path (the directory)
of InputStreamByteWrapper.class to the end of classpath.txt.
The path of InputStreamByteWrapper.class can be identified by
system.file("java", package = "R.matlab") in R.
Lazy alternative: Instead of setting path and classpaths,
you may try to copy the MatlabServer.m and InputStreamByteWrapper.class
to the current directory from which MATLAB is then started.
To start the server:
In order to start the MATLAB server, type
matlab -nodesktop -nosplash -r MatlabServer
If using MATLAB v6, make sure your classpath.txt is the
current directory!
This will start MATLAB and immediately call the MatlabServer(.m)
script. Here is how it should look like when the server starts:
< M A T L A B (R) >
Copyright 1984-2012 The MathWorks, Inc.
R2012a (7.14.0.739) 64-bit (glnxa64)
February 9, 2012
To get started, type one of these: helpwin, helpdesk, or demo.
For product information, visit www.mathworks.com.
Running MatlabServer v3.0.2
MATLAB v7.x or higher detected.
Saving with option -V6.
Added InputStreamByteWrapper to dynamic Java CLASSPATH.
----------------------
MATLAB server started!
----------------------
MATLAB working directory: /home/AwesomeUser/FabulousProject/
Trying to open server socket (port 9999)...done.
Alternatively you can start MATLAB and type MatlabServer
at the prompt.
By default the MATLAB server listens for connections on port 9999.
For other ports, set environment variable MATLABSERVER_PORT.
Confirmed MATLAB versions
This package has been confirmed to work successfully out of
the box together with the following MATLAB versions:
MATLAB v6.1.0.450 (R12.1) [Jun 2001],
MATLAB v6.5.0.180913a (R13) [Jul 2002],
MATLAB v7.0.0.19901 (R14) [Jun 2004],
MATLAB v7.0.1.24704 (R14SP1) [Oct 2004],
MATLAB v7.0.4.365 (R14SP2) [Mar 2005],
MATLAB v7.2.0.232 (R2006a) [Mar 2006],
MATLAB v7.4.0 (R2007a) [Mar 2007]],
MATLAB v7.7.0.471 (R2008b) [Oct 2008],
MATLAB v7.10.0.499 (R2010a) [Mar 2010],
MATLAB v7.11.0.584 (R2010b) [Sep 2010],
MATLAB v7.14.0.739 (R2012a) [Mar 2012],
MATLAB v8.2.0.701 (R2013b) [Sep 2013], and
MATLAB v8.4.0 (R2014b) [Oct 2014].
If you successfully use a different/higher MATLAB version,
please tell us, so we can share it here.
It does not work with MATLAB v5 or before.
Security
There is no security in the communication with the MATLAB
server. This means that if you start the MATLAB server, it will
wait for requests via the connection at the specified port. As
long as your R session has not connected to this port, others
may be able to steal the connection and send malicious commands
(if they know the R.matlab protocol). The MATLAB server only
allows one connection. In other words, if you are connected it
is not possible for others to connect to the MATLAB server.
MATLAB server is timing out
It might be that an *evaluate() call to the MATLAB server
takes a long time for the server to finish resulting in a time-out
exception. By default this happens after 30 seconds, but it can
be changed by modifying options, cf. setOption().
Multiple parallel MATLAB instances
You can launch multiple parallel MATLAB instance using this interface.
This can be done in separate R sessions or in a single one. As long
as each MATLAB server/session is communicating on a separate port,
there is no limitation in the number of parallel MATLAB instances
that can be used. Example:
> library('R.matlab')
## Start two separate MATLAB servers
> Matlab$startServer(port = 9997)
> Matlab$startServer(port = 9999)
## Connect to each of them
> matlab1 <- Matlab(port = 9997); open(matlab1)
> matlab2 <- Matlab(port = 9999); open(matlab2)
## Evaluate expression in each of them
> evaluate(matlab1, "x = 1+2; x")
> evaluate(matlab2, "y = 1+2; y")
Note that the two MATLAB instance neither communicate nor
share variables.
Author(s)
Henrik Bengtsson
See Also
Stand-alone methods readMat() and writeMat()
for reading and writing MAT file structures.
Examples
## Not run:
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# This example will try to start the MATLAB server on the local machine,
# and then setup a Matlab object in R for communicating data between R
# and MATLAB and for sending commands from R to MATLAB.
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# 1. Load R.matlab
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
library(R.matlab)
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# 2. Start MATLAB
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# 2.1. Start MATLAB from R?
# Start MATLAB server on the local machine (if this fails,
# see help(Matlab) for alternatives).
Matlab$startServer()
# 2.2. OR start MATLAB externally,
# THEN add 'externals' subdirectory to the MATLAB path
# (Where is the 'externals' subdirectory?)
print(system.file("externals", package = "R.matlab"))
# THEN from within MATLAB,
# issue MATLAB command "MatlabServer"
# Note: If issued from a MATLAB command line, this last command
# prevents further MATLAB 'command line' input
# until something like close(matlab) at the end of this script
# 2.3. If both these options fail, see help(Matlab) for alternatives.
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# 3. Create a MATLAB client object used to communicate with MATLAB
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
matlab <- Matlab()
# 3.1 Check status of MATLAB connection (not yet connected)
print(matlab)
# 3.2 If you experience any problems, ask for detailed outputs
# by uncommenting the next line
# setVerbose(matlab, -2)
# 3.3 Connect to the MATLAB server.
isOpen <- open(matlab)
# 3.4 Confirm that the MATLAB server is open, and running
if (!isOpen)
throw("MATLAB server is not running: waited 30 seconds.")
# 3.5 Check status of MATLAB connection (now connected)
print(matlab)
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# 4. Sample uses of the MATLAB server
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# 4.1 Run MATLAB expressions on the MATLAB server
evaluate(matlab, "A = 1+2;", "B = ones(2, 20);")
# 4.2 Ask MATLAB to display a value (without transferring it to R)
evaluate(matlab, "A")
# 4.3 Get MATLAB variables
data <- getVariable(matlab, c("A", "B"))
cat("Received variables:\n")
str(data)
# 4.4 Set variables in MATLAB
ABCD <- matrix(rnorm(10000), ncol = 100)
str(ABCD)
setVariable(matlab, ABCD = ABCD)
# 4.5 Retrieve what we just set
data <- getVariable(matlab, "ABCD")
cat("Received variables:\n")
str(data)
# 4.6 Create a function (M-file) on the MATLAB server
setFunction(matlab, " \
function [win, aver] = dice(B) \
%Play the dice game B times \
gains = [-1, 2, -3, 4, -5, 6]; \
plays = unidrnd(6, B, 1); \
win = sum(gains(plays)); \
aver = win/B; \
")
# 4.7 Use the MATLAB function just created
evaluate(matlab, "[w, a] = dice(1000);")
res <- getVariable(matlab, c("w", "a"))
print(res)
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# 5. Exception handling
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# 5.1 Try to get non-existing MATLAB variable
# (will result in an informative error)
tryCatch({
data <- getVariable(matlab, "unknown")
cat("Received variables:\n")
str(data)
}, error = function(ex) {
print(ex)
})
# Confirm that things still work
data <- getVariable(matlab, "A")
cat("Received variables:\n")
str(data)
# 5.2 Try to evaluate a MATLAB expression that fails
# (will result in an informative error)
tryCatch({
res <- evaluate(matlab, "C = 1+unknown;")
res
}, error = function(ex) {
print(ex)
})
# Confirm that things still work
res <- evaluate(matlab, "C = 1+2;")
print(res)
data <- getVariable(matlab, "C")
cat("Received variables:\n")
str(data)
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# 6. Done: close the MATLAB client
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# When done, close the MATLAB client, which will also shutdown
# the MATLAB server and the connection to it.
close(matlab)
# 6.1 Check status of MATLAB connection (now disconnected)
print(matlab)
## End(Not run)
R.matlab documentation built on Aug. 26, 2022, 1:07 a.m.
R Package Documentation
Browse R Packages
We want your feedback!
Note that we can't provide technical support on individual packages. You should contact the package authors for that.
| Matlab | R Documentation |
MATLAB client for remote or local MATLAB access
Description
Package: R.matlab
Class Matlab
Object
~~|
~~+--Matlab
Directly known subclasses:
public static class Matlab
extends Object
Usage
Matlab(host="localhost", port=9999, remote=!(host %in% c("localhost", "127.0.0.1")))
Arguments
host |
Name of host to connect to. |
port |
Port number on host to connect to. |
remote |
If |
Fields and Methods
Methods:
as.character | Gets a string describing the current MATLAB connection. | |
close | Closes connection to MATLAB server. | |
evaluate | Evaluates a MATLAB expression. | |
finalize | (internal) Finalizes the object if deleted. | |
getOption | Gets the value of an option. | |
getVariable | Gets one or several MATLAB variables. | |
isOpen | Checks if connection to the MATLAB server is open. | |
open | Tries to open a connection to the MATLAB server. | |
readResult | (internal) Reads results from the MATLAB server. | |
setFunction | Defines a MATLAB function. | |
setOption | Sets the value of an option. | |
setVariable | Sets one or several MATLAB variables. | |
setVerbose | Sets the verbose level to get more details about the MATLAB access. | |
startServer | Static method which starts a MATLAB server. | |
writeCommand | (internal) Writes (sends) an R-to-MATLAB command to the MATLAB server. | |
Methods inherited from Object:
$, $<-, [[, [[<-, as.character, attach, attachLocally, clearCache, clearLookupCache, clone, detach, equals, extend, finalize, getEnvironment, getFieldModifier, getFieldModifiers, getFields, getInstantiationTime, getStaticInstance, hasField, hashCode, ll, load, names, objectSize, print, save
Requirements
In order for R to communicate with MATLAB, MATLAB v6 or higher is
needed. It will not work with previous versions, because they
do not support Java.
We use the term server to say that MATLAB acts like a server
with regard to R. Note that it a standard MATLAB session that runs.
Also, the starting of the MatlabServer is simpler from MATLAB v7, although it is pretty straightforward for MATLAB v6 too. It is easier in MATLAB v7 and above, because the Java class required for remote-data-transfer can be automatically/dynamically added to the MATLAB Java classpath, whereas for MATLAB v6 it has to be added manually (see below).
Remote and non-remote connections
When a remote connection (argument remote = TRUE) is used,
data is send to and from MATLAB via a data stream. This is needed
when R is running on a host with a separated file system than
the one MATLAB is running on.
If not connection "remotely" (remote = FALSE), data is
communicated via the file system, that is, by saving and reading
it to temporary MAT files.
Troubleshooting: If "remote" transfers are used, the InputStreamByteWrapper Java class must be found by MATLAB, otherwise an error will occur in MATLAB as soon as data is send from R to MATLAB. In all other cases, the above Java class is not needed.
Starting the MATLAB server from within R
The MATLAB server may be started from within R by
calling Matlab$startServer(). By default 'matlab' is called
if named differently set options(matlab = "matlab6.5"), say.
The method is experimental and may not work on your system.
By default the MATLAB server listens for connections on port 9999.
For other ports, set argument port, e.g.
Matlab$startServer(port = 9998).
Note that the code will not halt and wait for MATLAB to get started. Thus, you have to make sure you will wait long enough for the server to get up and running before the R client try to connect. By default, the client will try once a second for 30 seconds before giving up. Moreover, on non-Windows systems, the above command will start MATLAB in the background making all MATLAB messages be sent to the R output screen. In addition, the method will copy the MatlabServer.m and InputStreamByteWrapper.class files to the current directory and start MATLAB from there.
Starting the MATLAB server without R
If the above does not work, the MATLAB server may be started manually from MATLAB itself. Please follow the below instructions carefully.
To be done once:
In MATLAB, add the path to the directory where MatlabServer.m sits.
See help pathtool in MATLAB on how to do this.
In R you can type system.file("externals", package = "R.matlab")
to find out the path to MatlabServer.m.
For MATLAB v6 only: Contrary to MATLAB v7 and above, MATLAB v6
cannot find the InputStreamByteWrapper class automatically. Instead,
the so called Java classpath has to be set manually. In MATLAB, type
which('classpath.txt') to find where the default
MATLAB classpath.txt file is located. Copy this file to the
current directory, and append the path (the directory)
of InputStreamByteWrapper.class to the end of classpath.txt.
The path of InputStreamByteWrapper.class can be identified by
system.file("java", package = "R.matlab") in R.
Lazy alternative: Instead of setting path and classpaths, you may try to copy the MatlabServer.m and InputStreamByteWrapper.class to the current directory from which MATLAB is then started.
To start the server:
In order to start the MATLAB server, type
matlab -nodesktop -nosplash -r MatlabServer
If using MATLAB v6, make sure your classpath.txt is the
current directory!
This will start MATLAB and immediately call the MatlabServer(.m) script. Here is how it should look like when the server starts:
< M A T L A B (R) >
Copyright 1984-2012 The MathWorks, Inc.
R2012a (7.14.0.739) 64-bit (glnxa64)
February 9, 2012
To get started, type one of these: helpwin, helpdesk, or demo.
For product information, visit www.mathworks.com.
Running MatlabServer v3.0.2
MATLAB v7.x or higher detected.
Saving with option -V6.
Added InputStreamByteWrapper to dynamic Java CLASSPATH.
----------------------
MATLAB server started!
----------------------
MATLAB working directory: /home/AwesomeUser/FabulousProject/
Trying to open server socket (port 9999)...done.
Alternatively you can start MATLAB and type MatlabServer
at the prompt.
By default the MATLAB server listens for connections on port 9999.
For other ports, set environment variable MATLABSERVER_PORT.
Confirmed MATLAB versions
This package has been confirmed to work successfully out of the box together with the following MATLAB versions: MATLAB v6.1.0.450 (R12.1) [Jun 2001], MATLAB v6.5.0.180913a (R13) [Jul 2002], MATLAB v7.0.0.19901 (R14) [Jun 2004], MATLAB v7.0.1.24704 (R14SP1) [Oct 2004], MATLAB v7.0.4.365 (R14SP2) [Mar 2005], MATLAB v7.2.0.232 (R2006a) [Mar 2006], MATLAB v7.4.0 (R2007a) [Mar 2007]], MATLAB v7.7.0.471 (R2008b) [Oct 2008], MATLAB v7.10.0.499 (R2010a) [Mar 2010], MATLAB v7.11.0.584 (R2010b) [Sep 2010], MATLAB v7.14.0.739 (R2012a) [Mar 2012], MATLAB v8.2.0.701 (R2013b) [Sep 2013], and MATLAB v8.4.0 (R2014b) [Oct 2014]. If you successfully use a different/higher MATLAB version, please tell us, so we can share it here.
It does not work with MATLAB v5 or before.
Security
There is no security in the communication with the MATLAB server. This means that if you start the MATLAB server, it will wait for requests via the connection at the specified port. As long as your R session has not connected to this port, others may be able to steal the connection and send malicious commands (if they know the R.matlab protocol). The MATLAB server only allows one connection. In other words, if you are connected it is not possible for others to connect to the MATLAB server.
MATLAB server is timing out
It might be that an *evaluate() call to the MATLAB server
takes a long time for the server to finish resulting in a time-out
exception. By default this happens after 30 seconds, but it can
be changed by modifying options, cf. setOption().
Multiple parallel MATLAB instances
You can launch multiple parallel MATLAB instance using this interface. This can be done in separate R sessions or in a single one. As long as each MATLAB server/session is communicating on a separate port, there is no limitation in the number of parallel MATLAB instances that can be used. Example:
> library('R.matlab')
## Start two separate MATLAB servers
> Matlab$startServer(port = 9997)
> Matlab$startServer(port = 9999)
## Connect to each of them
> matlab1 <- Matlab(port = 9997); open(matlab1)
> matlab2 <- Matlab(port = 9999); open(matlab2)
## Evaluate expression in each of them
> evaluate(matlab1, "x = 1+2; x")
> evaluate(matlab2, "y = 1+2; y")
Note that the two MATLAB instance neither communicate nor share variables.
Author(s)
Henrik Bengtsson
See Also
Stand-alone methods readMat() and writeMat()
for reading and writing MAT file structures.
Examples
## Not run:
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# This example will try to start the MATLAB server on the local machine,
# and then setup a Matlab object in R for communicating data between R
# and MATLAB and for sending commands from R to MATLAB.
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# 1. Load R.matlab
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
library(R.matlab)
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# 2. Start MATLAB
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# 2.1. Start MATLAB from R?
# Start MATLAB server on the local machine (if this fails,
# see help(Matlab) for alternatives).
Matlab$startServer()
# 2.2. OR start MATLAB externally,
# THEN add 'externals' subdirectory to the MATLAB path
# (Where is the 'externals' subdirectory?)
print(system.file("externals", package = "R.matlab"))
# THEN from within MATLAB,
# issue MATLAB command "MatlabServer"
# Note: If issued from a MATLAB command line, this last command
# prevents further MATLAB 'command line' input
# until something like close(matlab) at the end of this script
# 2.3. If both these options fail, see help(Matlab) for alternatives.
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# 3. Create a MATLAB client object used to communicate with MATLAB
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
matlab <- Matlab()
# 3.1 Check status of MATLAB connection (not yet connected)
print(matlab)
# 3.2 If you experience any problems, ask for detailed outputs
# by uncommenting the next line
# setVerbose(matlab, -2)
# 3.3 Connect to the MATLAB server.
isOpen <- open(matlab)
# 3.4 Confirm that the MATLAB server is open, and running
if (!isOpen)
throw("MATLAB server is not running: waited 30 seconds.")
# 3.5 Check status of MATLAB connection (now connected)
print(matlab)
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# 4. Sample uses of the MATLAB server
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# 4.1 Run MATLAB expressions on the MATLAB server
evaluate(matlab, "A = 1+2;", "B = ones(2, 20);")
# 4.2 Ask MATLAB to display a value (without transferring it to R)
evaluate(matlab, "A")
# 4.3 Get MATLAB variables
data <- getVariable(matlab, c("A", "B"))
cat("Received variables:\n")
str(data)
# 4.4 Set variables in MATLAB
ABCD <- matrix(rnorm(10000), ncol = 100)
str(ABCD)
setVariable(matlab, ABCD = ABCD)
# 4.5 Retrieve what we just set
data <- getVariable(matlab, "ABCD")
cat("Received variables:\n")
str(data)
# 4.6 Create a function (M-file) on the MATLAB server
setFunction(matlab, " \
function [win, aver] = dice(B) \
%Play the dice game B times \
gains = [-1, 2, -3, 4, -5, 6]; \
plays = unidrnd(6, B, 1); \
win = sum(gains(plays)); \
aver = win/B; \
")
# 4.7 Use the MATLAB function just created
evaluate(matlab, "[w, a] = dice(1000);")
res <- getVariable(matlab, c("w", "a"))
print(res)
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# 5. Exception handling
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# 5.1 Try to get non-existing MATLAB variable
# (will result in an informative error)
tryCatch({
data <- getVariable(matlab, "unknown")
cat("Received variables:\n")
str(data)
}, error = function(ex) {
print(ex)
})
# Confirm that things still work
data <- getVariable(matlab, "A")
cat("Received variables:\n")
str(data)
# 5.2 Try to evaluate a MATLAB expression that fails
# (will result in an informative error)
tryCatch({
res <- evaluate(matlab, "C = 1+unknown;")
res
}, error = function(ex) {
print(ex)
})
# Confirm that things still work
res <- evaluate(matlab, "C = 1+2;")
print(res)
data <- getVariable(matlab, "C")
cat("Received variables:\n")
str(data)
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# 6. Done: close the MATLAB client
# - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
# When done, close the MATLAB client, which will also shutdown
# the MATLAB server and the connection to it.
close(matlab)
# 6.1 Check status of MATLAB connection (now disconnected)
print(matlab)
## End(Not run)
R Package Documentation
Browse R Packages
We want your feedback!
Note that we can't provide technical support on individual packages. You should contact the package authors for that.
Embedding an R snippet on your website
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.