About Qa Tasks - Barco MediCal Pro Installation & User Manual

Hide thumbs Also See for MediCal Pro:
Table of Contents

Advertisement

MediCal Pro supports BARCO displays as well as displays from other
brands. It allows the connection of the following optical sensors: Barco
LCD sensor, Barco Serial sensor, X-Rite DTP92 (serial and USB), Wellhofer
Luxor LXPlus, Solar PMA2200, Minolta LS100, Verilum CPOD (serial and
USB) and Tektronix TJ17. Also the BARCO I-Guard sensor inside BARCO flat
panel displays is supported.

1.3 About QA tasks

With MediCal Pro, you can set up a schedule of QA tasks that have to run
at certain moments to check the conformance and consistency of the
viewing station displays.
When MediCal Pro is installed, a number of standard tasks are available to
be included in the QA schedule. A variety of other tasks is available as
plug-ins.
The tasks can be categorized in three groups, depending on the impact
they have on the user and the applications running on the viewing
station.
The task categories are:
Transparent inter-
vention-free
Intervention-free The task does not require any action from the user but
Non-intervention-
free
Once the QA task schedule is completed, the tasks will be executed at the
scheduled moments thanks to a service, MediCal Communicator, installed
together with MediCal Pro.
However, you can also run the tasks manually at any time, when this
would be necessary.
Introduction
The task runs completely in background. It does not
require any action from the user and does not change
the image on the display. E.g., an Automatic I-Guard
Check on a BARCO Coronis display is such a task.
These tasks can run also when no user is logged in on
the workstation.
does change the image on the display. E.g., the Mea-
sure Quality Level of a BARCO Coronis display runs
completely automatic, but during the execution of the
task, the current application image is replaced by test
images necessary for the measurement.
These tasks can run only when a user is logged in on
the workstation.
The task requires a user action. E.g., a visual check on
a test pattern requires the user to confirm that the
pattern was displayed correctly.
These tasks can run only when a user is logged in on
the workstation.
11

Advertisement

Table of Contents
loading

Table of Contents