Viewing logs

About the logs

The VWorks software records events that occur and stores the information in the following logs:

•	Main Log. Contains all of the actions that occur in the software. For more information, see Main Log.

•	Pipette Log. Contains all pipetting events and error information. For more information, see Pipette Log.

•	Time Constraints Log. Contains all information about time-limited tasks. For more information, see Time Constraints Log.

The log text colors can help you distinguish between different types of messages and events. For more information, see Log text colors.

In addition, you have the option of backing up and validating the log files for regulatory compliance. For more information, see Backing up and validating the log files.

 

Main Log

The Main Log records all available event and error information. You can view the Main Log in the following:

•	VWorks window

•	VWorks log file

Viewing the Main Log in the VWorks window

To view the Main Log in the VWorks window:

1	In the VWorks window, select View > Main Log.

2	Review the information in the Main Log tab.

 

Viewing the Main Log in a text editor

The VWorks log file is a text file with the following file name:

VWorks_log(date_time).log

To view the Main Log in a text editor:

1	In the Windows Explorer window, locate and select the VWorks_log(date_time).log file. The location is specified in the Options (Tools > Options) dialog box.

2	Open the file using a text editor such as Notepad.

Main Log contents

The Main Log contains the following information:

 

Column name	Description
Timestamp	Time and date of the event or error.
Class	The type of event or error message: • Info. General information. For example, System start up, or Simulation mode toggled on. • Event. A software action. For example, Scheduler started, or Move plate. • Error. An error that can stop the software and must be resolved. For example, Location incompatible with labware. • Warning. An error that might permit the software to continue. For example, Task requires that tips be on the pipette head.
Device	Device at which the event or error occurred.
Location	Location where the event or error occurred. For example, Bravo location 9.
Process	Name of the protocol process and subprocess that is running.
Task	Task at which the event or error occurred.
Description	Description of the action that is being recorded.
File name	Name and location of the protocol file.
Session ID	Login session number.

Pipette Log

The Pipette Log records all pipetting events and error information. You can view the Pipette Log in the following:

•	VWorks window

•	VWorks pipette log file

Viewing the Pipette Log in the VWorks window

To view the Pipette Log in the VWorks window:

1	In the VWorks window, select View > Pipette Log.

2	Review the information in the Pipette Log tab.

 

Viewing the Pipette Log in a text editor

The VWorks log file is a text file with the following file name:

VWorks_pipette_log(date_time).log

To view the Pipette Log in a text editor:

1	In the Windows Explorer window, locate and select the VWorks_pipette_log(date_time).log file. The location is specified in the Options (Tools > Options) dialog box.

2	Open the file using a text editor such as Notepad.

Pipette Log contents

The Pipette Log contains the following information:

 

Column name	Description
Timestamp	Time and date of the pipetting event or error.
Class	The type of event or error message: • Event. A software action. For example, when a protocol is started, the event is logged. • Transfer. A pipetting event.
Session ID	Login session number.
Volume	The volume of liquid transferred.
Aspirate Location	The location at which the Aspirate task occurred.
Aspirate Selection	The wells from which fluid was drawn for the Aspirate task.
Dispense Location	The location at which the Dispense task occurred.
Dispense Selection	The wells into which fluid was dispensed.
Description	The description of the action that is being recorded.
File name	The name and location of the protocol file.

Time Constraints Log

The Time Constraints Log records any time-limited task events and errors. If you did not specify time constraints, no information appears in the log.

You can view the Time Constraints Log in the following:

•	VWorks window

•	VWorks time constraint log file

Viewing the Time Constraints Log in the VWorks window

To view the Time Constraints Log in the VWorks window:

1	In the VWorks window, select View > Time Constraints Log.

2	Review the information in the Time Constraints Log tab.

 

Viewing the Time Constraints Log in a text editor

The VWorks log file is a text file with the following file name:

VWorks_time_constraints_log(date_time).log

To view the Time Constraints Log in a text editor:

1	In the Windows Explorer window, locate and select the VWorks_time_constraints_log(date_time).log file. The location is specified in the Options (Tools > Options) dialog box.

2	Open the file using a text editor such as Notepad.

Time Constraints Log contents

The Time Constraints Log contains the following information:

 

Column name	Description
Timestamp	Time and date of the event or error.
Class	The type of event or error message: • Info. General information. For example, System start up, or Simulation mode toggled on. • Event. A software action. For example, Scheduler started, or Move plate. • Error. An error that can stop the software and must be resolved. For example, Location incompatible with labware. • Warning. An error that might permit the software to continue. For example, Task requires that tips be on the pipette head.
Session ID	The login session number.
Start Process	The name of the protocol process or subprocess that contains the first of the two dependent tasks. This field also includes the instance number to help you identify the plate instance. For example, Process - 1 1 means Process - 1, instance 1. Start Process is paired with Start Task to identify the first of the two dependent tasks.
Start Task	The task number that identifies the first of the two dependent tasks. For example, 1 is the first task in the process, and 5 is the fifth task in the process. Start Task is paired with Start Process to identify the first of the two dependent tasks in the protocol.
End Process	The name of the protocol process or subprocess that contains the second of the two dependent tasks. This field also includes the instance number to help you identify the plate instance. For example, Process - 3 1 means Process - 3, instance 1. End Process is paired with End Task to identify the second of the two dependent tasks.
End Task	The task number that identifies the second of the two dependent tasks. For example, 3 is the third task in the process, and 10 is the tenth task in the process. End Task is paired with End Process to identify the second of the two dependent tasks in the protocol.
Target interval	The time specified in the Edit Time Constraints dialog box.
Allowed deviation	The time tolerance specified in the Edit Time Constraints dialog box.
Actual interval	The length of time of the first task during the run.
Actual deviation	The difference between the Target interval and the Actual interval.
Error	The result of the following: |Actual deviation| – |Allowed deviation| If the result is less than 0, Error is set to 0. For example: • Actual deviation is 66. Allowed deviation is 60. So Error is 66 – 60, or 6. • Actual deviation is 30. Allowed deviation is 60. So Error is 30 – 60, or –30. Because the result is less than 0, Error is set to 0.
Description	The description of the action that is being recorded.
File name	The name and location of the protocol file.

Log text colors

Text in the logs appear in the following colors:

 

Color	Description
Grey	Standard events with a date stamp or operator-added notes
Blue	Liquid transfer events
Orange	Warnings
Red	Error
Green	General information
Purple	Debug information (shown only if the Debug log level is greater than 0 in Tools > Options)

Backing up and validating the log files

You can back up and validate the log files to comply with regulatory requirements. The validation process checks the log file to see if it has been altered.

Backing up log files

To back up the log files:

1	With the protocol file open in the VWorks window, select Tools > Log Management. The Log Management dialog box opens.

2	Click the button, and then locate and select the log file you want to back up. The log file location is specified in Tools > Options. The file path and name appear in the Target box.

 

3	Click Backup. The Please name backup log file dialog box opens.

4	Select the folder in which you want to store the backup copy. In addition, type a name for the backup file.

5	Click Save. A backup copy of the log file is created.

Validating log files

To validate a log file:

1	With the protocol file open in the VWorks window, select Tools > Log Management. The Log Management dialog box opens.

2	Click the button, and then locate and select the log file you want to validate. The log file location is specified in Tools > Options. The file path and name appear in the Target box.

 

3	Click Validate. The software checks the log file and displays a message that explains whether the validation is successful. Validation is successful only if the file has not been altered.

Related information

 

For information about...	See...
Setting system-wide options	Setting general and view options
Specifying log file storage locations	Setting log file directories
Exporting and importing protocol and associated files	Exporting and importing protocols and associated components
Contacting Agilent Technologies and reporting problems	Reporting problems