text:
The Gateway server snapshot featured in last week's Hardware Today presented a vendor making waves in the commodity server market. Gateways' servers run the gamut from low-end 1-way Xeon towers designed for small to midsize businesses lacking an IS department, to more robust 4-way Xeon MP racks suited for departmental use as multiprocessing servers with mainframe-level error correction. These priced-to-move servers bring Gateway to a much more competitive sales level than was occupied previously by more-rudimentary and less-targeted server lines.
Gateway customers themselves are a varied group -- almost as varied as the ways in which the servers are deployed. One customer that stands apart from the crowd though is Autobase, a company whose bread and butter comes from providing customer relationship management (CRM) solutions to car dealerships. Autobase uses Gateway products internally to meet its operations and back-office needs, and also functions in a VAR-like role, bundling low-end Gateway towers with its CRM software.
On the sales side, Autobase bundles various entry-level Gateway hardware options with its software. "As the nation's largest automotive CRM software distributor, Autobase helps Gateway connect with thousands of small and medium-sized automotive dealerships nationwide," Gateway vice president of SMB and professional channels Steve McAllister told ServerWatch. "Gateway ships servers, desktop PCs, and notebooks to Autobase, which then bundles Gateway hardware with its software and services to dealer customers."
McAllister sees Gateway's dedicated 24x7 support (which is actually through IBM Global Services) as a sturdy complement to Autobase's robust, sales-driving CRM software. "Autobase software features powerful and interactive logbooks, letters, business planners, and statistical reports," he said. "Ultimately, the software helps dealerships close sales by building and maintaining strong relationships with customers."
To aid Autobase in this task, "Gateway backs up its PCs, notebooks, and network systems with dedicated support and services, around-the-clock, seven days a week," McAllister noted. This has proven to be a fuel-efficient combination for Autobase; to date, it has having rolled out more than 100 servers, 200 desktop machines, and 100 notebooks with its software management offerings.
Autobase's CRM software is available as a stand-alone offering, but the fully loaded version is a popular option. It bundles lightweight Gateway servers with software for more than 100 dealership customers. "Car dealerships are not the most technical-minded [firms] in the world, unless they're very large," Autobase Installation Engineer Eric Hinsch told ServerWatch, "so we offer to supply servers, printers, and, to a lesser extent, workstations."
Autobase most frequently deploys its software on the 960X, a dual-processor, Xeon-based tower server. Overall, rack servers are a less popular choice. "You don't have a lot of car dealerships who even know what a rack is," Hinsch said, "but those who do will usually ask during our pre-installation conference call." The servers ship with Windows 2003 based on OEM requirements.
|The 960X Tower
Under the Hood
In addition to functioning as a VAR for Gateway, Autobase relies on Gateway servers to keep its business running. Gateway servers power many of the Indianapolis-based vendor's operations and back-office applications. Autobase IT Director Dannie Stanley described Gateway servers as part of the company's Windows 2000 back-end, complementing a homogeneous data center that includes Dell servers running Linux.
One 975 rack server is used for development, while another runs Autobase's own CRM software for Autobase internal CRM. A 955 is used for testing, and an older Gateway 935 server model is used for human resources. Three "vintage" Gateway legacy servers are still trucking. The 7450R servers (which date all the way back to 2001) are from Gateway's earlier, less-focused stab at the enterprise market are also used for the likes of Active Directory and network storage.


text:
Sir Shridath Ramphal of Guyana was Commonwealth Secretary-General 1975–90.
Guyanese writers have won the overall Best First Book award of the Commonwealth Writers' Prize in 1991 (Pauline Melville) and in 2006 (Mark McWatt).
The Government of Guyana, at the 1989 CHOGM, offered to set aside about 360,000 hectares of pristine rainforest for research to demonstrate methods for conservation and sustainable use of forest resources and biodiversity: as a result, the Commonwealth's flagship Iwokrama Rainforest Programme was launched the following year.
The Commonwealth Youth Programme Caribbean Centre is based in Georgetown.
The Co-operative Republic of Guyana lies in the north-east of South America, north of the equator. It is bordered by Suriname, Brazil and Venezuela and, to the north and east, extends to the North Atlantic Ocean. The country comprises ten regions.
Georgetown (capital, pop. 118,363 in 2012), Linden (27,277), New Amsterdam (17,329), Anna Regina (11,793), Corriverton (10,600), Bartica (8,500), Rosignol, Skeldon and Vreed en Hoop. Georgetown is famous for its Dutch-inspired wooden architecture, street layout and drainage canals.
Surface travel in the interior of the country is hindered by dense forest, rapids on the rivers, and the generally undeveloped character of the interior. Thus, apart from in the coastal belt and on one inland route, most journeys are by air.
There are all-weather roads along the eastern part of the coast and some all-weather roads inland, including one across the country to the border with Brazil, and about seven per cent of the total network of 7,970 km is paved. There is no passenger rail service, although mining companies have private goods lines.
There are some 1,600 km of navigable river, 1,000 km of which are in areas of some economic activity. Passenger and cargo vessels travel up the Demerara, Essequibo and Berbice rivers, and also along the coast between the rivers. Apart from the Demerara, which has a road bridge, the other major rivers have to be crossed by ferries, which can take some hours for the wider rivers. At the Corentyne river ferry services link Guyana with Suriname.
Georgetown is the main port, and the international airport is CBJ International Airport, at Timehri, 40 km from Georgetown; larger towns and many mining companies have airports or landing strips.
Guyana is a member of the African, Caribbean and Pacific Group of States, Association of Caribbean States, Caribbean Community, Non-Aligned Movement, Organisation of Islamic Cooperation, Organization of American States, United Nations and World Trade Organization.
Guyana hosts the headquarters of the Caribbean Community in Georgetown.
Guyana has three distinct geographical zones. It has a narrow coastal belt, seldom more than 25 km wide and much of it 1–1.5 metres below sea level, where sugar and rice are grown and 90 per cent of the people live. In the far interior are high savannah uplands; between these, thick, hilly tropical forest covers most of the land area. For the country as a whole forest covers 77 per cent of the land area. In the forest zone are found most of the country's resources of bauxite, diamonds, gold, manganese and other minerals. Guyana's massive rivers include the Demerara, Berbice, Essequibo and Corentyne; rapids, bars and other obstacles make navigation difficult. The Kaieteur Falls on the Potaro river have a 222 metres drop – five times the height of Niagara. The Amerindian name 'Guiana' (part of the country's former name) means 'Land of Many Waters'.
Guyana has a warm tropical climate with high rainfall and humidity. The rainy seasons are November–January and May–July with an average rainfall of 2,350 mm p.a. in the coastal region. Inland rainfall averages 1,520 mm p.a. North-east trade winds moderate coastal temperatures.
The most significant environmental issues are water pollution by sewage, and agricultural and industrial chemicals; and deforestation.
Guyana's tropical forest, covering 77 per cent of the land area, is among the most ecologically valuable and best preserved in the world. The environment is an issue of great political importance in Guyana. There is concern about climate change and sea-level rise, because the low-lying littoral plain relies on a system of dams, walls and drainage canals to prevent flooding from the sea or the huge rivers. Forest resources are also important; the country has taken a lead in advancing forestry conservation and sustainable development and there was no significant loss of forest cover during 1990–2012.
Under the Iwokrama Rainforest Programme, some 371,000 hectares, much of it virgin forest, have been set aside for preservation and scientific study of its ecology and for sustainable development of the parts inhabited by Amerindian tribes or migrant mining communities. The programme was launched by the Guyana government and the Commonwealth Secretariat.
The tapir is the largest land mammal; cats include the jaguar and ocelot. Monkeys and deer are the most numerous species, and caimans are the largest freshwater animal. The giant anaconda or water boa is also found in the rivers. The wealth of plant, animal and micro-organism species includes many so far unrecorded, whose properties are unknown to science. Some 11 species of mammals and 11 species of birds are thought to be endangered (2014).

subset: commoncrawl


text:
"In choosing a B&B, we always factor in many aspects of the stay—the owners, the breakfasts, local attractions, comfortable lodging and the simple aesthetic qualities. Your B&B—more a resort really—surpassed expectations in all these areas. The Sun and Cricket is a joy to visit in all seasons."
- Audrey and Emily Grunau, Cleveland, OH
Welcome to the Sun and Cricket Bed and Breakfast, located on a hidden 35-acre estate within 30 minutes from downtown Pittsburgh. The solitude of this very special place extends to your accommodations: a private, three-room log cabin or a spacious carriage house.
We specialize in romantic getaways for people who enjoy nature and want luxurious comfort in their own private retreat. However, we also are ideal for business travelers who want something a little different from the ordinary. A creatively designed meeting room that can host up to 12 people may be rented for an additional feefor corporate gatherings and other special occasions.
A 200-year-old bank barn provides stalls for up to five horses and is surrounded by acres of fields and forests filled with century-old cherry, oak and maple trees.


text:
Welcome to Rivapharma
Rivapharma are committed to develop, manufacture and market unique pharmaceutical products with international standards of quality with high cost-effectiveness in different therapeutic classes,that give a value to our customer's expectations, employees, share holders and society.
We will accomplish this mission by identifying our core customer's needs and supporting the shared values of our organization which will allow us to more effectively meet the needs of our customers. To our Employees: Our human resources are our success power, we will encourage personal development, initiatives, and a commitment to excellence and exceptional service. In return we will be fair and respectful to our employees.


text:
VDR Wiki:Templates
Templates are ready to use constructs of wiki syntax. They are useful for frequently used text or other unchanging things that are used more often.
One can use a template by inserting {{template_name|option1|option2}} in the text. It is then replace by the template content together with the option in the generated text. That means, changing a template changes the text in all articles the template is used in.
If this is not intended prepend a subst: to the template name as in {{subst:template_name}}.
Template list
Here are the templates listed, that exist for VDR Wiki.
These are article skeletons. Create an empty article, place the appropiate template in it (with a prepended subst: before the template name, save the article and edit it again. The basic structure is now in place.
These are some info boxes. They get the info text as parameter.
Standard elements
- {{VDRWiki Header(Standard)}}
- {{VDRWiki Header(Hardware)}}
- {{VDRWiki Header(Software)}}
- {{VDRWiki Footer}}
Create empty article and place
{{subst:Article (plugin)}}
save, and edit again, the content is now in place.
Place this somewhere in an article
{{Box Hint| This is a hint. }}
and save it. The resulting page show noch a Box with the text This is a hint in it. Edit it again. Again the call of the template is there, not the content.


text:
Janet AndersonCopyright (c) 2002 The University of Chicago,
This document presents a description of the functions provided by the Alarm Handler (ALH) and describes its graphical user interface. The purpose of this guide is to explain how to use and configure the Alarm Handler.
This guide is written for individuals who wish to use and understand the Alarm Handler, namely accelerator operators and accelerator physicists.
The Alarm Handler is part of the Experimental Physics and Industrial Control System EPICS) co-developed by Los Alamos National Laboratory and Argonne National Laboratory. EPICS consists of a set of software components and tools with which application developers and designers can create an extremely flexible control system that minimizes the need for custom coding and helps ensure uniform operator interfaces. The Alarm Handler is one of the EPICS control system tools.
The Alarm Handler provides an interface between an operator and the EPICS control system database. The database is the interface between instrumentation hardware and all the EPICS control system software tools. This database is distributed throughout a network on I/O Controllers and contains records that are used to transfer information to and from the attached instrumentation to the Alarm Handler and other EPICS software tools.
Database records are made up of fields of various types. Scan fields specify under what circumstances a record will be processed. Convert fields determine how to convert a raw signal to/from engineering units. Device fields are used to specify the software interface to the device. Operator display fields specify how to display the record value. Processing fields are used by the run-time code for processing the record. There are also alarm fields that are used to specify conditions for alarm and to determine if the record is in an alarm state. Most fields are accessible throughout the network by means of the channel access interface software layer by specifying the record name and the field name. All monitoring and control operations are performed through the database.
Each record in the database includes fields for specifying the record's current alarm condition. There are two parts to this alarm condition: the alarm status and the severity of that alarm status. Alarm status and severity values are set and checked whenever a record is processed. When a new condition is detected, a routine is called to send a message to each process monitoring this record. The Alarm Handler is one of these processes.
Each database record also includes two fields for specifying the record's current alarm acknowledgment state. The unacknowledged severity field is the highest severity value of unacknowledged alarms, and the acknowledge transients field specifies whether transient alarms need to be acknowledged. A transient alarm is when the record enters alarm state and then returns to normal before the alarm is acknowledged. When any change to these fields is detected, a routine is called to send a message to each process monitoring this record.
The Alarm Handler filters alarm messages and displays alarms to the operator hierarchically. The alarm configuration structure defined in the alarm configuration file is used to determine this hierarchical display. The Alarm Handler brings alarms to the operator's attention, logs the alarms, allows the operator to acknowledge alarms, and gives the operator guidance on handling of specific alarms.
Chapter 1 is this Preface describing the users guide. Chapter 2 is an Introduction to the Alarm Handler and describes the scope of the tool and explains some Alarm Handler terminology. Chapter 3 explains how to invoke the Alarm Handler and describes the command line options. The Main Window is explained in Chapter 4 and Chapter 5 contains a description all Main Window menu functions. The content of an alarm configuration file is described in Chapter 6. An index of terms is available at the end of the document. Using the alarm configuration mode will be explained in Chapter 7 of a future version of this document.
The Alarm Handler is an interactive graphical application used primarily by accelerator operators and physicists to display and monitor EPICS database alarm states. It serves as an interface between an operator and the EPICS database and it communicates with the database using channel access function calls. The user interface for the Alarm Handler contains a hierarchical display of an alarm configuration structure allowing both high level and detailed views of the alarm configuration structure in one window.
The alarm handler is a Motif and X11 Window based application written in C language, and it runs on Unix, Linux, and Windows 95/NT hosts. The Alarm Handler source code is available via WWW as an EPICS extension.
The Alarm Handler monitors alarm conditions of EPICS database records. The primary responsibilities of the Alarm Handler (ALH) are to:
The Alarm Handler currently requires either an IBM personal computer with Windows 95/NT and Hummingbird's Exceed software or a workstation running a Unix type operating system with X Windows and Motif Version 1.2 or above. The Alarm Handler also requires the global alarm acknowledgment in EPICS base Version 3.11 or above.
An unexpected change of state for an EPICS database record. Examples of alarm conditions are:
There are two parts to an alarm: the alarm status and the severity of that alarm status. Alarm status and severity are set and checked whenever a record is processed. When a change is detected, a routine is called which sends a message to each process monitoring this record. The Alarm Handler may be one of these processes.
The SEVR alarm field in an EPICS database record specifies the severity of an alarm state. Currently the alarm severity can take one of the following four values:
Each EPICS database record has a STAT alarm field that specifies the alarm state of the database record. Currently the status field can take one of more than 20 values, some of which are:
The Alarm Handler displays alarms for an arbitrary set of channels. Each Alarm Channel refers to a specific EPICS database record.
The Alarm Handler provides a grouping mechanism so that related channels can be grouped together. An Alarm Group consists of a named set of lower level groups and/or database channels.
An Alarm Channel will be considered in an error state if there is a loss of communication between the Alarm Handler and the channel or if a channel access exception or other error occurs on the channel.
The alarm handler can execute in either a local or global mode. Global mode means that unacknowledged severity and acknowledge transients states will be determined by the current value of the fields in an EPICS database record. Local mode means that the unacknowledged severity and acknowledge transients states are local alh settings. Command line options determine the execution mode with local mode being the default setting. There is no way to change between local and global mode during execution.
The alarm handler can execute in either a passive (monitor) or active (modify) state. Passive state means that the alarm handler does not allow alarm acknowledgment and does not allow changes to acknowledge transients settings. There will be no channel access puts when executing in a passive state. The passive/active execution state is determined by a command line option with active state being the default and there is no way to change the current state during execution.
In Global Mode the Alarm Handler reads all ACKT and ACKS fields of the configured Alarm Channels: the Alarm Handler starts with the complete memory of still unacknowledged alarms. These alarms will have to be acknowledged, even if some may not be active anymore. (If a channel's ACKT field is set, any transient alarm will be latched and has to be acknowledged later on.) Global Mode also makes the Alarm Handler write alarm acknowledgements into the channels using Channel Access, i.e. all other Alarm Handlers in Global Mode will receive an alarm acknowledgment. Usually, all Alarm Handlers in the Control Room will run in Global Mode, so that any alarm has to be acknowledged only on one of the Alarm Handlers.
In Local Mode, the Alarm Handler starts without reading open acknowledgements from the channels, all alarm acknowledgements made will be valid only for this instance of the Alarm Handler. Usually, Alarm Handlers outside of the Control Room will run in Local Mode.
The Alarm Handler display consists of two types of windows, a runtime window and a Main Window. While the Alarm Handler is executing, the runtime window is always displayed.
The runtime window is a small icon like window that contains a single button containing the name of the alarm configuration main Alarm Group. The color of this button is used to show the highest alarm severity of any outstanding alarms. Beeping and blinking of the button is used to show the presence of unacknowledged alarms. Pressing the runtime window button will open the Alarm Handler Main Window or, if already open, bring the Main Window to the top of the window stack. The Close or Quit item on the window manager menu allows the user to exit the Alarm Handler.
The Alarm Handler Main Window is divided into three parts: a menu bar, an alarm configuration display area, and a message area.
On the menu bar, there are selections for pull-down menu items that perform all the functions of the Alarm Handler.
The alarm configuration display area is divided into two major parts: an alarm configuration tree structure display and an Alarm Group contents display. The current alarm configuration tree structure appears in the first area, and a list of the contents of the currently selected Alarm Group from the alarm configuration tree structure appears in the second area. Color is used to show alarm severity. A single character severity code is also provided for an operator with a monochrome display.
The message area displays the name of the current configuration file and has indicators to show definitions of the summary alarms fields for the currently open alarm configuration file.
There are three files used by the alarm handler while it is executing. They are the alarm configuration file, the alarm log file, and the operation modification log file.
The alarm configuration file is the only file used as input to the Alarm Handler. This file defines the Alarm Group structure and takes data in a flexible input format. The alarm configuration file specifies the Alarm Groups, Alarm Channels, channel masks, hierarchy of Alarm Groups, and other configuration information. The format and contents of the alarm configuration file are described in Chapter 6.
The user can specify the desired alarm configuration file using a file selection window at Alarm Handler start-up, or on the command line.
The Alarm Log output file contains a log of alarm state changes. For each change of alarm state, channel access connection state, and read/write access state, the date, time, channel name and current state values are recorded. The alarm log file is an ASCII file that can be displayed on any terminal or sent to a printer.
The Operation Modification Log output file contains a log of alarm acknowledgments and changes the user has made to the current alarm handler configuration. For each operator modification the date, time and description of the operator's modification are recorded.
Before invoking the Alarm Handler for the first time, the path to the executable and configuration files must be established. Contact your EPICS administrator to find the locations of the Alarm Handler executable, alh, and your site's Alarm Handler configuration input files.
The optional environment variable ALARMHANDLER can be used to point the Alarm Handler to a desired working directory. If ALARMHANDLER is not set, the current working directory is assumed. If the alarm configuration file resides on a different directory (e.g. /home/cs/appl/ah /dev) from the current working directory, under UNIX ALARMHANDLER can be set to point to the desired path by issuing the UNIX c shell command:
setenv ALARMHANDLER /home/cs/appl/ah/dev
The user must have read and write privileges in this directory.
Once the path is properly set, invoke the Alarm Handler by executing the command:
This command displays a file selection box in which to specify an alarm configuration file name. The default path for files is the directory defined by the ALARMHANDLER environment variable or the current directory and the default alarm handler output file names are ALH-default.alhAlarm and ALH-default.alhOpmod . If there is an alarm configuration file in the current directory with the name ALH-default.alhConfig, it will be used as the input configuration file.
The Alarm Handler command has several options and a usage message similar to the table below will be displayed if you enter: "alh -help".
alh [OPTIONS] [Xoptions] [configfile]
The alarm handler options are:
|-a alarmlogfile
|Alarm log filename [ALH-default.alhAlarm
|Alarm log using CMLOG
|Message Broadcast System
|Alarm Configuration Tool mode
|Caput the config file ackt settings to channels (if global and active)
|Disable alarm and opMod log output
|Debug output will be sent to stdout
|-f filedir
|Directory for alarm configuration files [.]
|-filter f-opt
| Set alarm display filter with f-opt
being one of [nau]
n[0]: no filter
a[ctive]: show only active alarms
u[nack]: show only unacknowledged alarms
|Global mode (channel ACKS and ACKT fields)
|Print usage text to stdout
|Use Locking System
|-l logdir
|Directory for log files [.]
|-m maxrecords
|Alarm log file maximum records [2000]
|Start with Main Window
|Do not display error popup window (errors are logged)
|-O key
|Log to database (Oracle)
|-o opmodlogfile
|Opmod log filename [ALH-default.alhOpmod]
|OpMod log using CMLOG
|-P key
|Print to TCP printer
|Passive state (no ca_puts to ACKS and ACKT fields and severity PV)
|Silent execution (no alarm beeping)
|Alarm Log Dated output files
|-v, -version
|Print version number
The default settings for ALH (Alarm Handler) are as follows:
The ' configfile ' option specifies which alarm configuration input file is to be used. The default is no configuration file and a file selection window is displayed.
The '-a alarmlogfile ' option specifies the name of the alarm log file. The default name is ALH-default.alhAlarm.
The '-aCM' option enables alarm logging into a CMLOG system. The default is not to use CMLOG. (Note: This option is only available if the Alarm Handler is compiled with CMLOG support.)
The '-B' option enables an operator to send messages using message broadcasting. The default is no message broadcasting. When this option is specified a send message menu item appears on the Main Window menu, and a message input dialog popup appears when the menu item is selected. The operator can then type in a message that will be sent to other alh processes when OK is pressed. A popup dialog box containing a sent message will appear when an Alarm Handler process receives a message.
The '-c ' option causes the Alarm Handler to enter the Alarm Configuration Tool mode. The default is to bring up Alarm Handler mode. The Alarm Configuration Tool mode is used for creating and editing alarm configuration files. Documentation for this mode will be added to this guide later.
The ' -caputackt ' option specifies that the Alarm Handler should write the alarm configuration file ACKT values using channel access puts to the EPICS database records when the Alarm Handler reads the configuration file. The default is not to write the alarm configuration file ACKT values.
The ' -D ' option allows running the Alarm Handler without creating and/or modifying the alarm log and alarm opmod files. This is useful if one alh process runs without this option, creating and modifying some fixed named alarm log files and all other alh process specifying the same file names run with the -D option which does not allow them to overwrite the alarm log files.
The '-debug' option specifies that debugging output should be printed to stdout. The default is not to print debug output.
The '-f filedir ' option specifies the directory for the Alarm Handler input and output files. The default location is the current working directory.
The '-filter f-opt' option sets the initial alarm display filter for the Alarm Handler (see ->>Menu Functions->Setup Menu->Display Filter). `f-opt' may be one of `n[o]' (for no filter), `a[ct]' (show active alarms) or `u[nack]' (show only unacknowledged alarms). Default is `no', i.e. all Alarm Groups and channels in the current configuration will be displayed. This option is particularly useful in combination with `-mainwindow' to start Alarm Handlers from operator panels.
The '-global' options specifies that the alarm handler should run in a global mode. In global mode an Alarm Channel's unacknowledged severity and it's acknowledge transients state will be determined by the current value of the EPICS database record's ACKS and ACKT field settings. In local mode, the default mode, the unacknowledged severity and acknowledge transients settings are local to the alarm handler.
The '-help' option will print alh command usage text to stdout.
The '-L' option activates a file locking system (based on lockf(), i.e. NFS-safe) making sure that only one of multiple Alarm Handlers with enabled log writing has access to the log. If the `master' (i.e. actively logging) process dies, another Alarm Handler will seamlessly take over logging. Default is not to use this locking mechanism.
The '-l logdir' option specifies the location of the alarm log file and the operation modification log file. The default location is the current working directory.
The '-m maxrecords' option allows the user to specify the maximum number of records that the alarm handler will allow in the alarm log file. If this number of records is reached, new records will overwrite old alarm records. The default number of records is 2000. Specifying zero means the file can have an unlimited number of records.
The `-mainwindow' option makes the Alarm Handler start with the Main Window instead of the Runtime Window. This is useful in conjunction with the `-filter f-opt' option to start Alarm Handlers from operator panels. The default is to start with the Runtime Window.
The `-noerrorpopup' option tells the Alarm Handler not to use popup boxes for displaying errors. This is useful for Alarm Handlers running as overhead displays (and no mouse attached to handle popups). The default is to use popups.
The '-O key' means that the alarm handler should send log messages to a database (Oracle).
The -'o opmodlogfile' option specifies the location of the operation modification log file. The default location is the current working directory.
The '-oCM' option enables opmod logging into a CMLOG system. The default is not to use CMLOG. (Note: This option is only available if the Alarm Handler is compiled with CMLOG support.)
The '-P' option allows simultaneously printing of new alarms to the log file and to a TCP printer (socket connection). The user must specify all three printer values: 'Name:port:colorModel ' (where colorModel is mono,hp_color,...). Currently the printing is done asynchronously by adding an additional task "alh_printer". (This option is still under construction and will use pipes in the future)
The '-s' option specifies that alh should start executing in a silent mode with no beeping when alarms are present. Setup menu items can be used to change the startup silence status.
Specifying this '-S' option means that the alh will execute in a passive (monitor) mode. This means that alh can not send channel access acknowledgment of alarms and can not do channel access puts to the acknowledge transients fields and cannot write to the severity process variable. It is useful for a non-operator alh user.
With the '-T' option, alarmLog file names will have "date" extensions like YYYY-MM-DD, and log files are automatically switched at midnight. For this option, there is a Main Window menu browser that is displayed after pressing View-"Alarm Log File Window". This browser allows searches in the AlarmLogFile and find all alarms inside of [t1,t2]-diapason containing some <String>.
The '-v' or '-version' option specifies that the Alarm Handler version number should be printed to stdout.
When executing on Unix, the 'alh' command line accepts all X options such as '-bg color_name' and '-fg color_name' and '-geometry geom_spec'
If the Alarm Configuration file is not specified on the command line, a file selection window is presented so the user can select the desired Alarm Configuration file
There are several ways to select the directory using this window:
Once in the appropriate directory, there are several ways to select the desired file:
Cancel ends the Alarm Handler session.
Help has not been implemented in this release.
Once an Alarm Configuration file has been selected, the Runtime window is displayed which appears on the user's screen as a small icon like window. This window contains a button labeled with the name of the Alarm Configuration file's Main Alarm Group.
The color of the button indicates the highest outstanding alarm severity level in the active alarm configuration.:
There will be beeping and the button will blink to indicate the presence of unacknowledged alarms.
To exit the Alarm Handler, use the Window Manager Menu on the Runtime Window and choose the Close menu item.
This will bring up the Alarm Handler Exit dialog window.
Click on OK to exit the Alarm Handler.
Click on Cancel to return to the Alarm Handler.
Help has not been implemented in this release.
Click the Runtime window button to open the Alarm Handler Main window or, if the Main window is already open, clicking the button will bring the Main window to the top of the window stack. This window contains the hierarchy of Alarm Groups and Alarm Channels (Process Variables) being monitored. The left half of the window contains the tree-structure of the Alarm Group, and the right side contains the contents of the selected Alarm Group. This window will be discussed in detail in the next chapter.
When the Runtime Window button is clicked, the Main Alarm Handler window. is displayed. The Alarm Handler Main Window is divided into two major parts: an alarm configuration tree structure display and an Alarm Group Contents display. This window also contains a menu bar and a message area.
This window shows the hierarchy of Alarm Groups and Alarm Channels (EPICS database records) being monitored. The left half of the window contains the tree-structure display of Alarm Groups, and the right side displays the contents of the tree-structure display's currently selected Alarm Group.
The Alarm Window menu bar provides menu selections for all the functions of the alarm handler and also gives users a second way to access some functions.
The current alarm configuration tree structure of Alarm Groups is graphically displayed as Group Summary Lines which are described in Group Summary Line . Buttons on the tree structure display allow the user to expand or deflate the alarm configuration tree structure.
Each group name in the configuration tree structure is displayed on a separate line. The following items appear in each group line of the tree structure display.
The configuration tree structure display has a scrolling/paging facility and a display resize facility. This allows users to view an alarm configuration tree structure too large to display on one screen.
The user will be able to choose any Alarm Group for display by pressing the Alarm Group name button from the configuration tree structure display. Selecting an Alarm Group will cause the Alarm Group contents display to show one level of the alarm subgroups and the Alarm Channels associated with the selected group.
The Alarm Group contents display for the currently selected Alarm Group contains group summary lines for each alarm subgroup followed by channel status lines for each Alarm Channel in the selected Alarm Group.
Each subgroup or channel name in the summary line is displayed with a color identifier indicating whether the name is an Alarm Group name or a channel name.
The Alarm Group display has a scrolling/paging facility to allow users to view an Alarm Group too large to display in one screen.
Each channel status line contains:
The message area shows the current execution mode (local or global), the current execution state (passive or active), the name of the current configuration file. It also contains buttons to silence alarms, and explanatory descriptions of the mask abbreviation codes and status data which appear in the group summary and channel status lines.
There are two Silence buttons which toggle beeping on or off. The Silence Current button turns off current alarm beeping until a new alarm occurs. The Silence One Hour button toggles on/off beeping of current and future alarms for one hour. When pushed in, beeping is turned off, when out, beeping is on. Beeping occurs only when there are unacknowledged alarms.
This display line summarizes the status of all alarms for the group named in this line and all lower level groups. The group summary display consists of the following items:
A one-character acknowledgment button is activated only if an unacknowledged alarm is present for the group and the alarm handler is executing in active (modify) state. This button is color-coded representing the highest severity unacknowledged alarm as follows:
This button describes the highest severity of unacknowledged alarms for this group and all associated subgroups.
Clicking on this button while alh is executing in active state will send channel access alarm acknowledgments to all Alarm Channels associated with the group. It has the same effect as individually acknowledging each channel in an unacknowledged alarm state.
A one-character severity display code. It is present only if at least one channel associated with the group is in alarm or in an error state. It is color-coded and represents the highest severity outstanding alarm as follows:
The code shows the highest severity unacknowledged alarm for this group and all it's subgroups.
ALH allows the operator to choose any Alarm Group by selecting the Group Name button on the group summary line. The result is to display one level of the contents associated with the selected group. This group also becomes the currently selected group.
The Current Mask Summary Display is a five character mask display. Each character is a"-" or one of the following:
Mask values are described in Alarm Channel Mask. If the current mask for any channel connected with this group or any subgroup has the above mask condition set, the corresponding character is displayed, otherwise the character "-" is displayed. For example the string "--A--" means that at least one channel has the NoAck mask set and that no channels have any other masks set.
The alarm summary count display shows the total number of channels in alarm and in an error state for this group and all its subgroups. This summary consists of a set of five fields:
Each field value indicates the total number of channel alarms with the specified severity in the associated group and all it's subgroups.
The channel status display is a line appearing on an Alarm Group Contents Window containing the following items:
A one character acknowledgment button. It is activated only if an unacknowledged alarm is present for the channel and the alarm handler is executing in active (modify) state. It is color coded, and represents the highest severity unacknowledged alarm as follows:
Clicking on this button while alh is executing in active state will send a channel access alarm acknowledgments to the Alarm Channel. A warning popup dialog with the message that alarm acknowledgment is not allowed in passive state will appear if the alarm handler is executing in passive (monitor) state.
The severity code character is present only if the channel is in alarm or in an error state. In this case, it is a color coded letter which represents the severity of the alarm as follows:
This button contains the database record name associated with the channel. The button is color coded in gray so that an operator can easily distinguish channels from groups. Selecting this button makes the channel the currently selected item.
The mask field contains a five-character display showing the settings of the channel's current mask. Each character is either a "-" or one of the following:
Masks are described in Alarm Channel Mask
Following the current mask characters are the channel's current alarm status and severity and the highest unacknowledged alarm severity. Current status and severity is present only if the channel is in an alarm state. Highest unacknowledged alarm severity is present only if an unacknowledged alarm is present.
The Main Window menu bar contains five pull-down menu items: File, Action, View, Setup, and Help.
The File menu has three command items: Open, Save As, and Close.
To open an existing alh configuration file, use the "File Open" menu item.
This brings up a standard file selection dialog, which allows the user to move around an existing directory structure to find the file to open.
To aid the user, the file selection box initially displays all files in the directory which end in ".alhConfig".
The " Save As" menu item, allows the user to save the current alarm configuration structure and current alarm configuration settings to a new or existing file. A dialog appears which prompts the user to supply the name of a file to write to. If the user gives the name of an existing file, another popup dialog will give a warning and ask the user if the existing file can be overwritten.
Selecting the Close item on the File menu can close the alh Main Window. This Main Window can be redisplayed again with a mouse click on the runtime window button.
The Action Menu provides selections which affect the currently selected Alarm Group or Channel. The action selections "Acknowledge Alarm", "Display Guidance", and "Start Related Process" can also be accomplished by clicking buttons on the tree structure or group contents display.
Alarm acknowledgment is only allowed while the alarm handler is executing in active (modify) state. The Alarm Handler user can acknowledge an alarm for the currently selected Alarm Group or Channel by selecting the "Acknowledge Alarm" item on the Action menu. Selecting this item for an Alarm Group acknowledges all Alarm Channels associated with the group. It has the same effect as acknowledging each channel individually.
When executing in global mode the Alarm Handler performs an alarm acknowledgment by sending a channel access alarm acknowledgment command to the channel and logging the alarm acknowledgement to the operator modification log file. The alarm acknowledgment indicators (color, blinking, and beeping) will change only after a channel access alarm event with the modified unacknowledged severity is received. Other executing alarm handler processes and other EPICS tools monitoring alarm events will also receive this alarm event.
When executing in local mode the alarm acknowledgment indicators (color, blinking and beeping) and the local unacknowledged severity level setting will change to reflect a local alarm acknowledgment and the alarm acknowledgement will be logged to the operator modification log file.
When "Display Guidance" is selected, associated guidance text lines for a selected Alarm Channel or Alarm Group will be displayed. Guidance text is intended to suggest possible reasons why this group or channel might alarm and actions that might remove the alarm condition. This menu item is inactive if guidance information is not available for the currently selected Alarm Group or Alarm Channel.
The guidance text display is a popup window displaying lines of ascii text if text was specified in the alarm configuration file. If a URL address was specified in the configuration file, Netscape will be invoked and display the text at the specified URL address.
Selecting "Start Related Process" will initiate execution of an Alarm Group or Alarm Channel's related process which was specified in the alarm configuration file. This item will be inactive if a related process was not specified for the currently selected Alarm Group or Alarm Channel.
This item displays a dialog box that allows the operator to change values of the Force Process Variable. The Force Process Variable is described in a later chapter. The user can change the name of the Force PV, the values of the Force Process Variable which will cause the Alarm Channel masks to be set and reset, and the actual mask the Force Process Variable will force on the group. The user can also disable and enable the Force PV. The force value must be set to a value different than the reset value.
There are four action buttons on this dialog box: Apply, Cancel, Dismiss, and Help. The Apply button will accept and apply the user entered changes. The Cancel button will discard the user entered changes in this dialog box and reset them to the original values. The Dismiss button will close this popup dialog, and the Help button will display a Force PV help information dialog.
Selecting "Force Mask" will popup a dialog box which allows the operator to change the mask for the currently selected group or channel. Changing a group mask will actually change the mask of all Alarm Channels within that group. Three masks are displayed: 1) the current mask, 2) the reset mask, valid for Alarm Channels only, which is the mask specified in the alarm configuration file, and 3) the mask to force, which the user defines by pressing one or more of the 5 state buttons below the mask.
The mask to be used for forcing (5 characters) may be any combination of -,C,D,A,T,L
There are four action buttons on this dialog box: Apply, Reset, Dismiss and Help. The Apply button will set the mask of all the Alarm Channels within this group to the mask as shown in the Mask line. The Reset button will reset the mask of each channel within this group to its own default mask defined in the alarm configuration file. The Dismiss button will cancel the force mask option and close the dialog window. The Help button will give force mask help information.
This menu item allows the operator to force or reset a specific bit of the current mask. For example, if the operator chooses "Add" in the "Add/Cancel Alarms" line then the Add/Cancel field of the current mask for all channels in the group are forced into the "Add" event state. Similarly choosing "Cancel" cancels the channel access add event state for all the channels. If "Reset" is chosen, the Add/Cancel field of the current mask for each channel in the group reverts to the default state defined in the active configuration file. Mask values are described in a later chapter.
This menu item gives the operator the ability to change the beep severity on individual channels or groups. A beep severity indicator will appear after the mask on the group (highest existing) and channel lines. The beep severity indicators are E=error, V=invalid, R=major, Y=minor. Beep Severity can be changed to MINOR, MAJOR, INVALID, or ERROR. If beep severity is set to MINOR,then MINOR, MAJOR, INVALID, and ERROR unacknowledged alarms will cause beeping. The -s command line option, silent execution, will override all menu and config file beep severity settings.
This menu item gives the operator the ability to set the noAck mask field of a group or channel to No Acknowlegment Necessary for one hour and have it automatically set to the reset value (config file value) after the hour expires. An "H" will be put into the noAck position of the mask on the group or channel line during the noAck hour. When a no-Ack timer is created, it will cancel any existing timers in any subgroups and channels. When a timer expires it will not reset any subgroups or channels that have an existing (i.e. more recent) timer.
The "Send Message" menu item allows alarm handler operators to send and receive messages to other alarm handler operators. A message input dialog popup appears when the "Send Message" menu item is selected. The operator can then type in a message that will be sent to other alh processes when OK is pressed. A popup message dialog containing the sent message will appear on other Alarm Handler processes when they receive the message.
The View menu allows the user to change the view of Alarm Groups in the current alarm configuration tree structure display. This menu also provides options for viewing the current working configuration file, alarm log file, and operation modification file in scrolled windows.
The View menu allows viewing of logged events while they take place. A user can simultaneously view both the alarm log file and the operator modification log files. When View is chosen, the sub-menu is presented.
The user selects this menu item to expand a collapsed the currently selected Alarm Group to graphically display one level of its alarm subgroups on the alarm configuration tree display.
The user can choose this item to expand the currently selected collapsed Alarm Group in the alarm configuration tree display to graphically show all levels of its subgroups on the alarm configuration tree structure display.
The user uses this menu item to expand all collapsed groups in the configuration tree structure display to graphically show all the groups and subgroups in the current alarm configuration.
The operator selects this item to collapse the currently selected expanded group in the alarm configuration tree to remove all its groups and subgroups from the graphical tree display.
The operator chooses this menu item to continuously display the current alarm history a display window containing the 10 most recent alarms. This display will be updated as alarms occur.
Selecting "Configuration File" brings up a scrolled window that displays the contents of the current configuration file.
Selecting this menu item will invoke a separate CMLOG browser process that allows browsing all records logged to the CMLOG system.
Selecting "Alarm Log File" brings up a scrolled window displaying time stamped alarm events in the alarm log file. Any new alarms logged into the alarm log file appear simultaneously in this window.
The date and time, Alarm Channel name, alarm status, alarm severity, and channel value are displayed when the Alarm Handler is executing in local mode. The highest unacknowledged severity and the acknowledge transients field values are also logged if the Alarm Handler is executing in global mode.
Selecting "Operation Log File" brings up a scrolled window showing the current content of the Operation Modification Log file. This file contains a log of time stamped operator configuration modification events. Any newly logged operation events appear simultaneously in this window. The top level Alarm Group name appears on each log line.
ALH does not allow an operator to view a log file that exceeds 1 Megabyte. When the log file exceeds 1 Megabyte, a new log file must be used in order for an operator to be able to view the log process within the ALH.
The Alarm Handler allows the operator to display all the current configuration settings for any selected Alarm Group or Alarm Channel.
The Setup menu provides the option of overriding initial settings for the alarm configuration, the alarm log, and the operation modification files.When this menu is selected, the Setup sub-menu, is presented
If one of the file options is chosen, a file selection dialog popup window appears and the operator is allowed to choose a new file. The operation of the file selection box is described in Configuration File Selection Window . The file selection changes are always logged in the operation modification file.
The user is allowed to set an alarm filter to display active alarms only. When the filter is set to Active Alarms Only, only those groups or channels with an outstanding alarm will be displayed. When the filter is set to Unacknowldged Alarms Only, only those groups or channels with an outstanding unacknowledged alarm will be displayed. When the selection is set to No Filter, all Alarm Groups and Alarm Channels in the current configuration will be available for display.
The operator can specify the beep condition. The beep condition is the minimum alarm unacknowledged severity necessary for beeping. The default startup value is MINOR, or a startup severity can be specified in the alarm configuration file. The ALH Beep Severity can be changed to MINOR, MAJOR, or INVALID. If the beep condition is set to MINOR,then MINOR, MAJOR, INVALID, and ERROR unacknowledged alarms will cause beeping. The -s command line option, silent execution, will override all menu and config file beep severity settings.
The alarm log file contains the log of alarm changes of states. The Alarm Handler allows the operator to specify an alarm log file name that differs from the current setting. If it does not exist, it will be automatically created. All new alarm state changes will be logged to this file.
The Alarm Handler allows the operator to specify an operation modification log file that differs from the current setting. If it does not exist, it will be automatically created by ALH. All subsequent operation changes will be logged to this new operation modification file.
The Help menu item will display this "Alarm Handler User Guide" when selected.
When the About menu item is chosen, information about the current version of the alarm handler is displayed.
The alarm configuration file is the file used as input to the Alarm Handler. This file defines the Alarm Group structure and takes data in a flexible input format. The alarm configuration file, which can be prepared via any text editor, defines a complete Alarm Group structure composed of subgroups and channels. The arrangement of channels and subgroups follow the standard tree structure. The subgroups always terminate at channels. The only input format constraint is that the definitions must be in hierarchical order. That is, after a group is defined in the configuration file as belonging to a parent group, all its subgroups and channels must be defined in the configuration file before a new group belonging to the same parent group can be defined. There can be only one top-level group (main group) and this group must have NULL as the parent group name. For each group or channel, a set of input specifications is used to define special events to be taken care of at start-up time.
When opening a new configuration file, ".alhConfig" will be used as the default suffix. The default file name for the alarm configuration file is ALH-default.alhConfig.
The configuration file statements for a given group or channel takes flexible input format which can consist of the following items:
GROUP parentName GroupName
$HEARTBEATPV heartbeatPVName <value> <seconds>
CHANNEL parentName ChannelName <mask>
INCLUDE parentName fileName
$FORCEPV forcePVName forceMask <forceValue> <resetValue>
$FORCEPV CALC forceMask <forceValue> <resetValue>
$FORCEPV_CALC <expression>
$FORCEPV_CALC_A <PVNameA>
$FORCEPV_CALC_F <PVNameF>
$SEVRPV sevrPVName
$GUIDANCE urlAddress
$ALIAS anyValidTextString
$COMMAND anyValidCommand
$SEVRCOMMAND severityChangeValue anyValidCommand
$STATCOMMAND alarmStatusStringValue anyValidCommand
$ALARMCOUNTFILTER inputCount inputSeconds
$BEEPSEVERITY ALHbeepSeverity
$BEEPSEVR GroupOrChannelBeepSeverity
Input syntax notes:
The line starting with $HEARTBEATPV is optional. It is required only when a user wants a monitored pv to show weather or not ALH is running. If the $HEARTBEATPV line is present, ALH will do CA puts of the specified value to the specified pv at the specified rate (in seconds). The heartbeatPVName must be an existing PV in the EPICS database and can be specified as <channel_name>.<field_name>.
A set of group or channel lines must appear in the alarm configuration file. These lines define the Alarm Group structure. The first line is the top level Alarm Group definition. There can be only one top-level Alarm Group and this Alarm Group must have NULL as the parent group name. Group or Channel lines must start with the keyword GROUP or CHANNEL. The GroupName is the name of a user specified Alarm Group. The ChannelName must be the name of a specific record defined in an EPICS database. The length of a GroupName or ChannelName must not exceed 28 characters. The parentName is the name of the parent Alarm Group. There is no restriction on the number of group definitions.
GROUP parentName GroupName
The channel <mask> is optional and defaults to no mask (i.e. -----). It is required only for a channel with a non default mask setting. The detailed description of mask settings is given in Alarm Channel Mask in this Chapter.
CHANNEL parentName ChannelName <mask>
The line starting with INCLUDE allows a user to designate, within his alarm configuration file, the name of another alarm configuration file to be read by the Alarm Handler at runtime. The main Alarm Group of the designated file will become a child group of the parentName group specified on the INCLUDE line.
INCLUDE parentName fileName
The lines starting with $FORCEPV are optional. They are required only when a user wants to let ALH automate changing an alarm group or channel's mask values by monitoring an EPICS database process variable or by monitoring the value of a calulated expression based on PV values.
The first method is to monitor a single EPICS database process variable. Only only one input line is required. This line defines the forcePVName (process variable to be monitored), forceMask, forceValue, and resetValue. The forcePVName must be an existing PV in the EPICS database and can be specified as <channel_name>.<field_name>. Whenever the value of the force process variable changes to be the same as the forceValue, the Alarm Group or Channel mask will be set to the forceMask. For an Alarm Group, this means that masks of all the channels in the group and its subgroups are set to the forceMask. Whenever the value of the force process variable changes to be the same as the resetValue, these channel masks are set to their default values. The forceValue must be different from the resetValue. The default setting is forceValue = 1, and resetValue = 0. A "NE" can be used in the resetValue field to reset the masks when the value of the force process variable no longer equals the force value. Alarm Handler menu items exist which allow the user to enable/disable the Force PV, change the name of the Force PV, and change the Force Process Variable values. The force PV test uses type double for forceValue, resetValue and pv value.
$FORCEPV forcePVName forceMask <forceValue> <resetValue>
The second method is to monitor the value of a calculated expression. This requires multiple Force PV CALC input lines to define the expression. This CALC facility allows algebraic, relational, and logical operations on up to 6 pv values. The result of the expression is compared to the forcePV forceValue and resetValue to determine whether or not to set group/channel masks.
To specify a forcpePV calculation expression in the alhConfig file you create the $FORCEPV record as before but you specify "CALC" instead of a PV name. Then you add a new $FORCEPV_CALC line in which you specify the calculation expression in a manner similar to the calc record expression. In fact alh uses the same code as the calc record to evaluate the expression. You specify the expression using A, B, ... instead of the pvnames. Then you add $FORCEPV_CALC_A through $FORCEPV_CALC_F lines to specify the pv names. (You can also specify constant values on these lines.) The Alarm Handler ForcePV dialog window allows users to specify or change the ForcePV CALC data.
An example of the alhConfig file lines for a calculation forcePV is
$FORCEPV_CALC_A jba:alh5
$FORCEPV_CALC_B jba:alh6
The expression is evaluated using type "double" for all pv values and constants.
The line starting with $SEVRPV is optional. It is required only when a user wants to write the severity value of a group or channel to a process variable. The sevrPVName must be defined in the IOC database and is specified as <channel_name>.<field_name>. Whenever the group or channel severity changes, the new severity value is written to the severity process variable via a channel access put (ca_put) request. Writes to a severity process variable are done only when the alarm handler is in global active mode. The value -1 is written to the servrity PV when the group or channel is disabled.
$SEVRPV sevrPVName
The lines starting with $GUIDANCE are optional. They are required only when a user wants to display alarm guidance information for a group or channel. The $GUIDANCE line may be followed by a set of ascii guidance text lines with an $END line to terminate the guidance text, or alternatively, the $GUIDANCE line may contain a url address.
<text lines>
$GUIDANCE urlAddress
The line starting with $ALIAS is optional. It is required when it is desired that the alarm handler display the specified alias text string in places where it would normally display the Alarm Group or Alarm Channel name.
$ALIAS anyValidTextString
The line starting with $COMMAND is optional. It is required only when a user wants to provide the feature of starting a related process for this group or channel. The related process will be invoked when the alh operator clicks on the Process button in the alarm handler Main Window display.
$COMMAND anyValidCommandSyntax
The line starting with $SEVRCOMMAND is optional. It is required if a process should be invoked when the alarm severity value for a group or channel changes. A single group or channel may have multiple $SEVRCOMMAND lines. This line defines the change in the severity necessary to start the process and defines the process to be started.
Valid severity change values are -
The line starting with $STATCOMMAND is optional and valid only for an Alarm Channel. It is required only when the alarm handler should start a process when the channel alarm status becomes a specified value. A single channel may have multiple $STATCOMMAND lines. This line defines the status value necessary to start the process and defines the process to be started. Valid alarm status string values can be found in the EPICS base alarmString.h header file.
Example alarm status string values are -
The line starting with $ALARMCOUNTFILTER is optional. It is required only when the alarm handler should filter the registration of alarms for a group or channel. This line defines the alarm count and seconds required for alarm registration. To register as an alarm, a channel must remain in an alarm state for more than inputSeconds seconds or the channel must enter into an alarm state from a no-alarm state more than inputCount times within inputSeconds seconds.
$ALARMCOUNTFILTER inputCount inputSeconds
The line starting with $BEEPSEVERITY is optional. It is required only when the alarm handler should filter the beeping if alarms are present. This line defines the minimum severity level required for beeping. Beeping will not occur when the highest outstanding severity is less than the specified severity. Valid severity values are MINOR, MAJOR, INVALID, and ERROR.
$BEEPSEVERITY severity
The following listing shows a simple
example of an alarm configuration file.
$COMMAND medm /home/phoebos/USER/appl/example.adl
Line 1 of guidance information about main group
Line 2 guidance.
Line 3 guidance.
$COMMAND medm /home/phoebos/USER/appl/example2.adl
CHANNEL AAA rai_2000
CHANNEL AAA rai_2001
CHANNEL BBB rbi_000
CHANNEL BBB rbi_2000
CHANNEL CCC rbo_000
CHANNEL MAIN rbo_001
In this example, the first group is named MAIN. The MAIN group contains three subgroups ( AAA, BBB, and CCC) and one channel (rbo-001). The AAA subgroup contains two channels: rai_2000 and rai_2001. The BBB subgroup contains the two channels: rbi_000 and rbi_2000. The CCC subgroup contains only one channel: rbo_000.
In this example the default mask "-----" is used for every channel. That is, no masks are specified on the group and channel lines.
In above example, $COMMAND and $GUIDANCE options are specified for the MAIN group. The $GUIDANCE option allows the user to display guidance text in a popup window when the MAIN group guidance button is pressed. The $COMMAND line option allows a user to start the display manager, medm, by pressing the MAIN group's related proccess button.
In above example, the $COMMAND, $FORCEPV, and $SEVRPV options are specified for the AAA group. This $COMMAND option allows a user to open an xterm window from the start related process button on the AAA group line. The $FORCEPV option tells alh to add an automatic force mask event for group AAA. If the value of process variable FORCE:AI becomes 1, then the mask of all the channels in this group will be set to the forceMask, "-D---". If the value of process variable FORCE:AI becomes 0, then the mask of all the channels in this group will be reset to their default mask values. The $SEVRPV option tells alh to record the alarm severity of group AAA to the process variable SEVR:AI.
Associated with each Alarm Channel are two five bit masks (default and current). The current mask can be changed by force commands or by force process variables. The default mask is defined in the alarm configuration file. A reset command forces all associated masks to return to the default values.
The definition for each bit in the mask
value follows:
This mask bit determines if a channel access add event is active. Add/Cancel means that a ca_add_event is/isn't active. If ca_add_event is not active for a channel, the IOC will not send alarm events to the alarm handler for that channel.
" C" means cancel and "-" denotes add.
Alarms aren't/are ignored by the alarm handler. Disabling an alarm has the effect of no display and NoAck. If an alarm is disabled the alarm status and severity are not displayed. Thus, even though a ca_add_event is in effect, the channel always appears to the operator to be in the NO_ALARM state. Alarm change of states will, however, still be logged unless NoLog is in effect.
When a pv is enabled after it has been disabled for a while and the pv is not in alarm state but there are unacknowledged transient alarms and the alarm handler is running in global mode, an automatic acknowledgement is sent when the pv is enabled and the auto acknowledgement is logged in the opMod file if the alarm handler is running in global mode.
" D" means alarm disabled.
The operator is/isn't required to acknowledge alarms.
" A" means alarm acknowledgment is not required.
The operator is/isn't required to acknowledge transient alarms. A transient alarm is one that enters alarm state and then returns to normal before the operator can acknowledge the alarm.
" T" means acknowledgment of transient alarms is not required.
Alarms will/won't be logged.
" L" means no alarm logging .


text:
One-pot pork with orange, olives & bay
Nutrition and extra info
- Freezable
Nutrition: per serving
- kcal670
- fat36g
- saturates11g
- carbs35g
- sugars9g
- fibre7g
- protein37g
- salt1.2g
- 85g sundried tomato in oil, roughly chopped, plus 2-3 tbsp oil from the jar
- 1kg pork shoulder, cut into chunky cubes
- 2 tbsp plain flour, seasoned
- 400g shallot (see tip, below)
Related to the onion (as opposed to being a younger version of it), shallots grow in clusters at…
- 1 onion, thinly sliced
Onions are endlessly versatile and an essential ingredient in countless recipes. Native to Asia…
- 3 bay leaves
- few thyme sprigs
This popular herb grows in Europe, especially the Mediterranean, and is a member of the mint…
- 5 garlic cloves, thinly sliced
- 400ml red wine
- strip of zest and juice from 1 orange
One of the best-known citrus fruits, oranges aren't necessarily orange - some varieties are…
- 350ml chicken stock
- 400g can chopped plum tomato
- 800g large new potato, peeled & halved or cut into fat slices, depending on size
New potatoesn-ew po-tate-oes
New potatoes have thin, wispy skins and a crisp, waxy texture. They are young potatoes and…
- 70g pack dry black olive
Heat 1 tbsp of the sundried tomato oil in a large, flameproof casserole dish. Toss the pork in the flour, tap off any excess, then brown it in 2 batches, transferring to a large bowl once golden and crusted. Use a splash more oil for the second batch if needed.
Tip 1 tbsp oil, shallots, onion, bay leaves and thyme into the pan and fry for 5 mins until golden here and there. Stir in the garlic and sundried tomatoes, cook for 1 min more, then tip onto the pork.
Splash the wine and orange juice into the dish, add the orange zest and boil hard for 5 mins. Add the meat and onions back in.
When ready to cook, heat oven to 160C/140C fan/gas 3. Stir the stock, canned tomatoes, potatoes and olives into the casserole, then bring to a simmer. Prod the potatoes as far under the surface of the liquid as you can. Cover, leaving a slight gap to one side, then cook in the oven for 2½ hrs, or until the meat is tender enough to cut with a spoon. Spoon away any excess fat and let the stew rest for a few mins before ladling into shallow bowls.
Recipe Tip
Making aheadThis one-pot is great for cooking a day ahead. The excess fat will be easy to lift away once cold, and the flavours will be even more intense once warmed very gently to a simmer. You may need to add a splash of water to loosen it a little.
Recipe Tip
Soaking your shallotsSoaking your shallots in just-boiled water for 5 minutes before peeling makes the job a lot easier. Once soaked, trim away the root end and peel from the bottom.


text:
Nuts are such a part of our everyday existence they even turn up in a host of quotations by authors, playwrights, poets, philosophers, and clergy.
Here are just a few that might bring you a chuckle, raise your hackles, or offer a moment of thoughtful reflection:
If .. 'Ifs and buts' were candy and nuts…oh, what a party we would have." –H. Bergh
"Worldly riches are like nuts; many a tooth is broke in cracking them, but never is the stomach filled with eating them." –Rabbi Nachman of Breslov
"I'm Charley's aunt from Brazil–Where the nuts come from."
'Charley's Aunt' (1892) A play by Bradon Thomas.
"It takes 50000 nuts to put a car together, but only one to scatter them all over the road."
— Darryl Somers
"I said to the almond tree, "Friend, speak to me of God," and the almond tree blossomed."
–Nikos Kazantzakis
Almond blossom, sent to teach us
That the spring days soon will reach us.
– -Sir Edwin Arnold, Almond Blossoms
"A woman, a dog and a walnut tree, the more you beat them, the better they be"
–Thomas Fuller


text:
Dash-Cam Revelations In NJ Show Again The Importance Of Video As Evidence In Police Abuse
from the worth-a-thousand-words dept
Several weeks ago, Tim Cushing wrote about a case in New Jersey featuring an officer accused of abusing a cyclist who failed to engage his dash-cam during the incident. As noted in the piece, the value of having optional tape of any incident occurring between an officer and the public should be obvious. On the one hand, the public is already under a great deal of public surveillance, which can often times be used as evidence in any criminal proceedings. Tape featuring law enforcement action is valuable both ways, first in holding our public servants to account should they fail to behave appropriately and second to exonerate them if they are accused of wrong-doing.
In this latest story, also in New Jersey, we see an example of the former. Marcus Jeter was met by police at the home he shares with his girlfriend after a domestic violence call made to police. Once there, police reportedly spoke to Jeter, who says he left amicably after briefly talking to officers. It's worth noting that no charges were ever filed for that domestic incident. What happened next, however, is another matter entirely. Jeter was pulled over by officers shortly after leaving the site of his home.
The New Jersey DJ, 30, was arrested in a 2012 traffic stop and charged with eluding police, resisting arrest and assault. Prosecutors insisted that Jeter do prison time.The plea deal offered to Jeter was five years of prison time, for resisting arrest and assaulting police officers. Those were the charges levied in the officers' report. Those charges, as would later be determined by an active police dash-cam, were utter bullshit.
The video, which prosecutors say they never saw before filing the initial charges, shows Jeter holding his hands above his head.Oops. As it turns out, there wasn't any resisting of arrest and the only assault occurring was when the officers beat the hell out of Jeter. On top of that, the officers in question elected to omit surely-unimportant details of the arrest from their reports, such as when one of them careened over a median into Jeter's vehicle, which was also shown in the dash-cam footage. On top of that, police had their weapons drawn almost immediately, despite the fact that Jeter had pulled over to the shoulder as requested and remained in his vehicle, terrified.
"The next thing I know, one of them busts the [car] door and there is glass all over my face," he told ABC News station WABC-TV about the arrest. "As soon as they opened the door, one officer reached in and punched me in my face. As he's trying to take off my seat belt, I'm thinking, 'Something is going to go wrong.'" Jeter says the cops continued hitting him, telling him not to resist arrest.
Thanks to Jeter's attorney filing a request for records, which included the footage, the charges against Jeter were dropped and charges were instead filed against the officers. Those charges include aggravated assault, conspiracy, and official misconduct.
Now, we can and should respect law enforcement, but that respect doesn't come without the public's right to verify our public officials are behaving honestly and judiciously. Let there be no argument: the public has a right to the footage of officers in action.
Filed Under: abuse, dash-cam, marcus jeter, new jersey, police


text: i already whatched new dvd "Excellence" with Konstantin & Mikhail. it's really a great explained dvd. it's very interesting to heard about the knowledge of the body and human being and understand what's being the fight !!! i feel it, understand & agree with simple principles that are as Konstantin s..read more >>


text:
Thursday, March 25, 2010
Letters from my children... and Lacey being funny!
Posted by Pam at 9:40 AM 3 comments
Tuesday, March 23, 2010
Posted by Pam at 9:22 AM 1 comments
Thursday, March 18, 2010
Random pictures and stories...
Posted by Pam at 9:20 AM 2 comments
Tuesday, March 16, 2010
An unexpected and UNWANTED surprise...
Posted by Pam at 3:40 PM 1 comments
Friday, March 12, 2010
Matthew Drama...
Posted by Pam at 1:28 PM 3 comments
Saturday, March 6, 2010
The beginning of a new chapter...
Joe and I were married December 27th 2000. It was going to be in my hometown in Modesto CA, and it was sandwiched between Christmas and the celebration of my great grandfather's 100th birthday (the 29th). We had a HUGE turnout from my side of the family because of that. It was not super easy to plan our California wedding from Utah, but we managed, and it turned out well. We were married in the Fresno CA temple (I would have preferred the Oakland Temple, but it was closed for maintenance...). After the ceremony, we headed back to Modesto for our reception later that night. There were a few mishaps, but all in all a fantastic evening, with plenty of family and friends to celebrate with. After the reception Joe and I stuck around town "honeymooning" until the next evening when we made a quick stop in at Grandpa's party to wish him a happy 100th birthday. Then we left to head back to Utah, honeymooning along the way in Vegas. When we got back to Utah, we had an Open House for those of our family and friends who lived in UT. It was not as well attended, but it was beautiful and The important people came. Both Joe and I felt extremely blessed to have such amazing family and friends, and their support was greatly appreciated!
Posted by Pam at 10:03 AM 3 comments
Monday, March 1, 2010
The Big Question
I move to Utah in late June of 2000. After a week or so, I had secured myself a full time job at a local bank, and was moved in to my aunt and uncle's spare bedroom. Joe lived about half an hour away. He worked a part time night job, and was a full time student, so I wasn't able to see him much- only on the weekends, really. But it was good to be able to spend more time with him! We spent a lot of time on the phone during the week. I was introduced to all of his siblings, and their families, and I got to know them all a lot better. Within a few months we KNEW we were ready to make the next step.
Posted by Pam at 11:00 AM 2 comments


text:
nuLOOM Surreal Canvas Raye Shaggy Area Rug
Made from the finest materials in the world and with the uttermost care, our rugs are a great addition to your home.
Product Features
- Technique: Machine Made
- Material: 100% Polyester
- Primary colour: Multi
Location: Indoor use only
- Brand: nuLOOM
- Designed in USA
- Made in China
About the Brand
Founded with a desire to push boundaries and break the rules of what is expected from an area rug, nuLOOM was created to fill the void between brilliant design and affordability. nuLOOM's production team stretches the limits on the use of vibrant colours giving each piece individuality and elegance. They draw inspiration from such things as nature, textiles and architecture from around the globe, making their collection of artistic floor coverings a perfect fit for today's fashion forward shoppers.
Have a Question?
Be the first to ask a question about this.


text:
Behind The Scenes With GunPlay & The Pre$ident "Hell Of A Hustler" [Label Submitted]
Follow @thepresidentny The Pre$ident teamed up with MMG artist GunPlay with "Hell Of A Hustler" Directed By CeoDolla follow @ceodolla & M5 Films
Please click the "Report" button below if the video on this page is not working properly.
Comments will only be displayed by verified emails. No Spamming or Racism.


text:
Student Immigration
This course is recommended for any members of faculties and departments who are involved in student administration. The University is required to ensure compliance with the responsibilities of its Tier 4 sponsor licence, granted by the Home Office to provide visa sponsorship for non-EEA students. The aim of the course is to provide an overview of the immigration regulations affecting students, with a focus on the requirements for visiting students and the practicalities of supporting this activity within the Cambridge context.
- University staff
- Further details regarding PPD's eligibility criteria are available
Number of sessions: 1
|Tue 26 Nov 2019 09:30 - 12:00
|09:30 - 12:00
|Greenwich House, Edmonton Room
|Anthony Dangerfield, Rosemary Bell
- to understand the responsibilities which the University, and its students, hold in relation to the Tier 4 licence
- to provide clear guidance on all immigration matters relating to visiting students
- to understand the University's student immigration compliance responsibilities
- to be able to identify issues and know when to contact the International Student Office
One session of two hours
Booking / availability