This page contains information about using EPICS with MATLAB and Java in the LCLS Development and Production environments.
Attention:
All scripts in this page are assuming that your current shell is Bash.
In order to change your default shell at login from tcsh (or any other shell) to Bash, please execute the following command on a Linux server on the AFS network, such as a rhel6-64* node. (You will be prompted for your password during this process):
|
After that, close the terminal and open a new one. You will be using Bash as the default shell.
You can check if all went well with the following command in a new Terminal window:
|
matpva: Integrate EPICS7 into MATLAB using PVAccess for Python (P4P) module
How to test matpva in DEV and PROD (lcls and facet)
At the time of this writing, the latest version of Java available in Development and Production is 1.8.0_181 (64-bit). In order to use this Java version, source the following scripts depending on your environment:
For Oracle compatibility, the Oracle client used must also be compiled for 64-bit. In order to use the supported 64-bit Oracle client, source the following scripts depending on your environment:
The EPICS Java APIs are located at:
At these locations you will be able to find the following libraries:
phoebus
This repository contains the whole phoebus code (replacement for the CS-Studio backend) but it also contains the new pva client library developed by Kay Kasemir.
exampleJava
Includes a set of examples of client and server code for PVAcess.
Click the version name of MATLAB shown below to move to the detailed instructions for each version.
For MATLAB admins (epicsmgr group members) only:
At the time of this writing, the latest version of MATLAB deployed for LCLS Development and Production is 2022b.
Individual AFS user accounts in the LCLS Development environment default to set up and use MATLAB 2012a unless overridden.
The default MATLAB versions for shared login accounts in Production are as follows:
Account | Default MATLAB version |
---|---|
physics | 2012a |
softegr | 2019a |
laci | 2012a |
To use one of the supported versions of MATLAB, you need to set up your environment following the appropriate procedures.
For the Development and Production environments, a set of working configuration files is already provided for users and invoked upon login. Users can override the usage of these files by having their own custom files in the folder where they launch MATLAB (see: Creating A Custom MATLAB Environment).
MATLAB is non-standard Unix software and does not adhere to values set by PATH, LD_LIBRARY_PATH, CLASSPATH, and other global environment variables that are used by most other Unix software. Instead, MATLAB uses the following configuration files to set its environment:
For questions on the installation and deployment of MATLAB in Development or Production, please contact:
Description: This file is used to pass variables and configurations to the Java JVM used by MATLAB.
Location:
<matlabroot>/bin/<architecture>/java.opts
e.g., in Development environment: /afs/slac/g/lcls/package/matlab/2019a/bin/glnxa64/java.opts
Description: This file is used to augment the Java classpath used by MATLAB.
Location:
<matlabroot>/toolbox/local/classpath.txt
e.g., in Development environment: /afs/slac/g/lcls/package/matlab/2019a/toolbox/local/classpath.txt
Description: This file is used to augment the library search path used by MATLAB.
Location:
<matlabroot>/toolbox/local/librarypath.txt
e.g., in Development environment: /afs/slac/g/lcls/package/matlab/2019a/toolbox/local/librarypath.txt
If you need to use a MATLAB environment configuration that does not match the default environment provided in Development or Production, you will need to create your own java.opts, classpath.txt or librarypath.txt files in your working directory prior to launching MATLAB.
It is strongly recommended to only override the files needed in your local workspace, since MATLAB will inspect your current working directory before looking at the global configuration files.
If you need to connect to a different set of EPICS servers, copy the java.opts file from one of the locations above to your local working directory and modify it according to your needs.
If you need to test a new JAR file, copy the classpath.txt file from one of the locations above to your local working directory and modify it according to your needs.
If you need to test a new library to add to the library path, copy the librarypath.txt file from one of the locations above to your local working directory and modify it according to your needs.
Never try to modify the existing global configuration files. If you need changes made to the global configuration files, consult the MATLAB admins for LCLS Development and Production (TID-ACS and EED Systems Group). Any changes to the global MATLAB configuration must be approved and implemented by those groups.
This is a known issue in MATLAB R2022b Update 5. The bug that triggers the warning when starting up MATLAB will be resolved in the upcoming update.