There is now general agreement with the administrators of the current Refrigeration and Gas system that all FIX SCADA and View nodes will have 21" monitors that are set to display 1280 by 1024 pixels. In addition, picture sizes will be 7 x 5 in FIX units, whatever they are. This corresponds to the picture sizes that are currently in use for the Refrigeration, Gas, Environmental, and Rack Monitoring systems. We will attempt to define this more precisely.

Meanwhile, in order to set the picture size, you should do the following. By setting the WINDOW size in the WORKSPACE -> USER PREFERENCES -> PICTURE PREFERENCES menu you can define the window size then fit the picture to the window. We don't know what the window height and width values mean. Once set to, say, a width of 75.00 and a height of 50.00 that will become the default size for any new pictures. You can create a picture larger than the window size but require it to fit by selecting from the VIEW menu the FIT PICTURE TO WINDOW selection.

If you have pictures you have already created, you can change their size in the following way. You can resize the current pictures by playing with the values in the WORKSPACE -> USER PREFRENCES -> PICTURE PREFERENCES menu. These values apparently define the Window size but not the picture size. You can define a smaller window size; then select VIEW -> FIT PICTURE TO WINDOW selection. Finally the VIEW -> UPDATE WINDOW LOCATION selection will decrease the size of a large picture. Save the picture. When the picture is reloaded it will be set to the new window size.

It is also agreed that all menus will have a similar layout and color. Menu buttons will be red if the system they correspond to has an alarm or yellow if the condition is an alert. Otherwise, they will normally be green or grey with black text.

We still need to discuss colors and the look and feel of the lower level high voltage and temperature pages. Hopefully there will be examples soon from the users that we can look at and discuss.

There is now a proposal to record all readings in each system at 10 minute intervals. There may be specific items that the detector group might wish to record at a higher rate, but if these are wished to be archived over the duration of the experiment, they will need to be small in number.

Locally

This would mean saving historian files to a local Zip or Jazz drive disk. The user would be responsible for archiving his or her own files. These files can only be viewed by using the FIX historian.

Online Database

This option would involve copying logged files to the online data base for each system. This might saturate the bandwidth available for copying to Oracle and needs to be discussed and evaluated. The total amount of disk space required for the entire run is probably less than 2 GB.

It is also be possible to export the historian file to a text file which can then be viewed with tools from PAW if desired. This can be done by the user at any time.

Server

The server administrators would prefer not to be responsible for backing up this data, but we could certainly discuss doing it automatically this way to writable CD's. The CD's could be read by the local PC.

All user pictures will be kept on the server in a subdirectory devoted to the particular detector. The directory structure for the muon system would be

S:\wdmacs\pic\cdfmcs\muon\

The global pages are kept in

S:\wdmacs\pic\cdfmcs

When pages have been developed that can be integrated into the system, they should be placed on the server in the appropriate directory. They can then be linked to the appropriate global page.

Note that there is a global variable defined by the CDF main menu page that determines whether pictures are obtained from the server or locally. For the final system, the pictures should be normally obtained from the server and locally only when the server is not available. During the development period, the user will probably want to work locally and copy pictures that are ready for general use to the server.

There is a bug in the current developer's edition of FD so that the ReplacePicture command does not work properly. This is known to Intellution and will be fixed in the final release later this year. Meanwhile, the workaround is to use the ClosePicture command together with the OpenPicture command.

We need to create alarm areas for each of the subsystems. I would propose to create the following alarm areas, which can be used to filter alarms. I welcome any feedback as to any other suggestions. If I have left out any detector element, please let me know.

Muon

Central

SVX

ISL

COT

Plug

Power Supplies

We also need to set up accounts for each system for the various levels of user access that are required. This means defining group and user accounts for each group. The groups would presumably include the above alarm areas in addition to the administrative ones. User accounts then need to be defined for each user for the particular group. If the groups as defined can be agreed upon, I would like to start setting up security on the server for FD. In order to do that, I need the user names and what access you would like for your detector group.