|March 15, 1995||All That Fits is News to Print||Vol. 9, No. 4|
|Postscript version||TeX source|
Page contact and owner at end of this issue.
March 13, 1995
|Author: Ron Chestnut||Subsystem: SCP||User Impact: Small|
|Panel Changes: Few||Documentation: Yes||Help File: Yes|
Starting April 1, there will be a series of major software releases, which have, for the most part, been ready for several months, but have not been released in order to minimize impact on the program. These are scheduled as follows:
Other scheduled items:
Other unscheduled items:
March 15, 1995
|Author: Lahey,Underwood,Gromme||Subsystem: Database||User Impact: Small|
|Panel Changes: None||Documentation: Yes||Help File: None|
The 64K database project expands the maximum allowable size of the database, allowing us to define more devices as needed.
Users and application code should see no changes, but we would like you to watch for unusual conditions in the control system that might be caused by this change. All interfaces between application code and database routines are UNCHANGED.
The changes are entirely hidden inside the database internals and low level database code on the VAX and Micro. We will release a new database and some new VAX and micro code.
March 15, 1995
|Author: T. Lahey, et. al.||Subsystem: All Software||User Impact: Small|
|Panel Changes: None||Documentation: Yes||Help File: None|
We are expanding the maximum number of SLCNET and other BITID micros that the control system supports. Any application code which calls MICROALL, MICR_EXPAND_RANGE, or GETMICROLIST must be able to accept more micros in the return arguments. Calls to BITMAP_TO_ MICRONAME and MICRONAME_TO_BITMAP must support a larger number of defined micros.
Please review all of your private code and prepare to recompile and relink it after the release of the BITID code in April.
Another related project will expand the number of micros in a display group (DGRP). This project will be released separately. Watch for an article in a later index panel. While reviewing your private code for sensitivity to the total number of defined micros, please also look for code which allocates storage for the micros in one DGRP.
March 15, 1995
|Author: Keith Jobe||Subsystem: None||User Impact: Medium|
|Panel Changes: None||Documentation: Yes||Help File: Yes|
Matlab version 4 is here, and version 3.5 is almost dead. On April 1, 1995 (no fooling) the license for Matlab version 3.5 will expire, and there is no possibility of extending the license.
We should be using version 4 by now. Transistioning to the newer version was describen in an article in the May 16, 1994 Index Panel. For those of us (myself included) who have misplaced it, here is a copy compliments of the computer:
Text of May, 1994 Index Panel article
The new version of Matlab is now available from the SLC VAX cluster mainframe computers. This version is a ``major'' release of Matlab, and has a significant number of new features and changes in the graphical interface. Unlike prior releases of Matlab, this release has broken a large fraction of the previously debugged scripts and functions developed by the SLC physicists and operations support personnel.
While the scripts and functions are being debugged, the old version (version 3.5h) will
remain as the system ``default" version for a while. To define the new version,
hskip block start 24pt hskip block end mcc> MATLAB__4
and to run it, enter:
hskip block start 24pt hskip block end mcc> MATLAB
Both versions of Matlab are licensed to allow an unlimited number of users to run on the two major mainframes (MCC and SLC ). The limited use licenses which allow a few users to run on the cluster workstations have not been upgraded to version 4 yet. Separate licenses also exist for operation on the SUN/UNIX workstations without any of the SLC extensions or database access routines. Please contact Bob Boeninger ( BOE@SLAC.STANFORD.EDU ) if you want more information regarding the SUN Matlab.
This is a new version of Matlab, the various standard SLC ``.M" files, and additions will take their authors a while to debug. Please be patient and try to contact the author of the code when problems are uncovered.
Manuals for the new version of Matlab are available from Software Engineering upstairs in MCC . Those users with the Macintosh version of Matlab will probably not need a new manual since the manual sets are almost identical.
Note: Consistent with the Matlab help files and documentation, all Matlab commands in this article (such as GET(0) ) are shown upper case. Note, however, that the commands must be entered using lower case characters (as get(0) ) to work.
The major changes and incompatibilities are:
Printing: The usual SLC -type modifications have been applied to the Matlab print support -- ignore the documentation on PRINT in the Matlab Reference Guide. These changes are required by the wealth of printer types available - Matlab presumes that the printer type and print command is fairly stable. The usual (Matlab 3.5) commands PRINT , PRINTB , PRINTOUT , PRINTER_SET , PRINTCLEAR , and PRINT_WHERE are supported.
Matlab aficionados might want direct access to the native Matlab PRINT command to generate EPS files, and will find it renamed as PRINTM .
The list of printers is smaller since Matlab insists on using Postscript level 1 or 2,
and will not generate the Tektronix 4014 language for printing (a sad good-by to VM based
Imagen printers). Your default printer may be defined in your login file by setting the
symbol MATLAB_PRINTER to the printer name as seen from inside Matlab using the PRINTER_SET
command. (Matlab 3.5 used a logical name to store this information.) For example, you
might want to add the following to your own LOGIN.COM file:
hskip block start 24pt hskip block end $ MATLAB_PRINTER :== MCC$PRINT
User customization may be done in several ways.
Some of the snazzy new features are:
Try HELP . The help is grouped by functions. Try HELP GRAPHICS and HELP PLOT for example.
Direct file read of binary files of user data (see FOPEN , FREAD ).
Colormapped plots and images (try [X,Y]=MESHGRID(-3:.125:3); Z=PEAKS(X,Y);
Try DEMO . Try this onlyif you have some time to kill.
After you plot something, explore the graph's objects with the commands GET(GCF) and GET(GCA) . To change something, try SET(GCA,'VISIBLE','OFF') . GCF means get current figure handle, GCA for axis.
Matlab now supports M-file debugging. Try HELP DBSTOP for information.
The command AXIS is different from AXES . The latter allows multiple scales on the same plot.
Matlab supports a version of a movie, where multiple frames are displayed in a defined order. The DEMO displays this. This feature is known to break on X-displays with insufficient memory.
WHITEBG toggles the background color to white. It does considerably more with various arguments.
March 14, 1995
|Author: Ralph Johnson||Subsystem: Software Knobs||User Impact: Some|
|Panel Changes: None||Documentation: No||Help File: Yes|
The mouse button processing within the SCP has been changed so that you must push the center and right buttons simultaneously to pop up the software knobs panel. The rest of the operation of the panel remains the same.
For those using a two button mouse, holding down the control key while clicking the right mouse button is the now the same as clicking the center and right mouse buttons of a three button mouse.
March 9, 1995
|Author: Kenneth Underwood||Subsystem: Wire Scanners||User Impact: Small|
|Panel Changes: None||Documentation: None||Help File: None|
Wire scanner X and Y BPM jitter correction can now be independently disabled. Until this change, BPM jitter correction could only be disabled for the entire wire scanner. BPM jitter correction for U/V wires is disabled only if both X and Y are disabled. All BPM jitter correction can still be disabled by toggling the
button to OFF on the
To modify the X or Y BPM jitter correction disables for a wire scanner you must DBEDIT the WIRE hardware descriptor secondary, HDSC. Add or remove the symbols %WIRENOXJ and %WIRENOYJ in the HDSC secondary for the desired WIRE unit while preserving all other symbols. After the DBEDIT, you must push the
to update the SCP.
For example: one of the following lines would be used to disable X or Y BPM jitter correction for WIRE:FF11,1670. The %WIREQEMT and %WIREWEMT symbols describe other WIRE hardware features and must be preserved.
:HDSC: = %WIREQEMT + %WIREWEMT; ! X and Y BPM jitter correction enabled
:HDSC: = %WIREQEMT + %WIREWEMT + %WIRENOXJ; ! disable X only
:HDSC: = %WIREQEMT + %WIREWEMT + %WIRENOYJ; ! disable Y only
:HDSC: = %WIREQEMT + %WIREWEMT + %WIRENOXJ + %WIRENOYJ; ! both disabled
Back to top of this issue
|March 9, 1995||Index Panel||Vol. 9, No. 4|
Translated from original PlainTeX by index2html.pl.
*Links followed by an asterisk are limited to SLAC clients only.