Release Notes for base-R3-14-12-3_1-0 ----------------------------------- base-R3-14-12-3_1-0: Shankar/Ernest/Strauman (Mar/28/2012) This is an import of EPICS baseR3.14.12.3.tar.gz from the collaboration into LCLS base-R3-14-12 with some additional patches. For the sequence and location of the patches please see SLAC_Patches.txt ----------------------------------- Patches: TSEL.patch - EPICS collaboration - Applied Sep/16/2013 Reading back a .TSEL field that is pointed to another record's .TIME field was exposing internal details (that the link target field gets changed internally to point the .VAL field) which don't need to be made visible. This patch hides the change, and should allow a .TSEL field to be saved and restored properly using autosave. OSDThread.patch - Strauman/Shankar Realtime (RT) scheduling is a feature of all Linux operating systems (not just those with an 'RT Kernel') that enables an application to meet timing deadlines more reliably. A feature that contributes significantly to the application's ability to meet timing deadlines is the ability to lock part or all of the process's virtual address space into RAM, preventing that memory from being paged to the swap area. This patch will attempt to lock the process's virtual address space into RAM if the process has the ability to run threads with different priorities. If unsuccessful, it prints an message to stderr. In Linux, one can grant a process the ability to run threads with different priorities by using a command like ulimit -r unlimited. In Linux, one can grant a process the ability to lock memory by using a command like ulimit -l unlimited. Alternatively, these limits can be configured on a per user/per group basis by using /etc/security/limits.conf or its equivalent. DBDump.patch - Zelazny/Rock The IRMIS PV crawler script parses every ioc's st.cmd file to collect PV and configured field lists to store in the RDB. The crawler is a complicated perl script developed at APS over 8 years ago. Over the years new st.cmd syntax elements have been introduced. Many of these changes affect elements parsed by the IRMIS crawler, and therefore the script must be constantly modified to keep up with syntax and usage changes. dbdump creates a file containing a formatted list of PV and field names. Instead of parsing complex and changeable st.cmd syntax, the crawler (or any other software for that matter) can simply read and parse the dbdump file to obtain PV and field lists. envPerl.patch - EPICS collaboration If you need to use a version of Perl which is not found at /usr/bin/perl some of the scripts that come with Base will run the wrong perl. This patch changes all of the Perl preamble lines to #!/usr/bin/env perl which should be correct on all modern Unix-like systems. This line is not used on Windows systems. dbScan.patch - EPICS collaboration A fix for bug 597054 is available for sites that want their period scan tasks to not drift on workstaion OSs. Apply this patch which prints warning messages when repeated over-run errors occur. 1091401.patch - EPICS collaboration A race condition can occur when reloading the access security file from a subroutine record that is processed using "caput" rather than a longer-running CA client such as MEDM or "caput -c". This patch fixes the problem. ----------------------------------- Notes: Migration for IOC Application Engineers: Some additional notes for those that start new applications and want to use the slac style templates. You will be able to do the same as before: makeBaseApp.pl -t slac The templates have been moved outside of EPICS BASE and now live in the modules area. EPICS_MBA_TEMPLATE_TOP=${EPICS_MODULES_TOP}/icdTemplates/MAIN_TRUNK When logging into the DEV system sourcing: "$EPICS_SETUP/go_epics_3-14-12-3_1-0.bash" will setup the EPICS environment as well the ENV Var mentioned above. If you have an existing application and would like to migrate, please use the sample slac template as your guide/reference. When checking out modules from CVS including IOC application modules please use the "eco" utility. Note: For engineers that had applications for linuxRT targets, it is now easier. To migrate your existing linuxRT application follow the "slac" template for sure. If you try to use the new EPICS BASE as is, your App will not build. Note: For engineers that would like to try and build softIOCs for linux-x86 as a static based executable; we now support this in the new EPICS BASE. Here, I am referring only to softIOCs on linux hosts since they are all currently dynamically built. All of our cross targets namely, RTEMS and linuxRT-x86 create static binaries already. So, to have your softIOC build statically you just need to do the following: Add two variables below in your ""/configure/CONFIG_SITE" file: =============================================== SHARED_LIBRARIES=NO STATIC_BUILD=YES =============================================== Do not touch the "CHECK_RELEASE = YES" variable