Programming Reference:Debug Output - Revision history

Mellinger: /* Global Debug Level */

2011-06-07T14:52:18Z

Global Debug Level

← Older revision		Revision as of 14:52, 7 June 2011
Line 46:		Line 46:
	will start the FeedbackDemo module with a debug level of 10.		will start the FeedbackDemo module with a debug level of 10.

	Note that the debug level parameter will propagate to the other modules only after "Set Config" has been pressed from the operator module. Thus, other modules must be started with the DebugLevel argument, as well, if you need to view debugging messages from operation phases prior to the Initialization Phase.		Note that the debug level parameter will propagate to the other modules only after "Set Config" has been pressed from the operator module. Thus, other modules must be started with the DebugLevel argument as well, if you need to view debugging messages from operation phases prior to the Initialization Phase.

	==Logging into Files==		==Logging into Files==

2008-08-08T18:44:04Z

Logging into Files

← Older revision		Revision as of 18:44, 8 August 2008
Line 55:		Line 55:
	Debug log files carry the name of the corresponding run file, and a ''.dbg'' extension.		Debug log files carry the name of the corresponding run file, and a ''.dbg'' extension.

	''Note:'' Data files are written by the �[[Technical_Reference:Core_Modules#Data_Acquisition_Module\|source module]]; debug log files are maintained by the [[User_Reference:Operator_Module\|operator module]]. When source and operator module do not reside in the same directory, and the [[User Reference:DataIOFilter#DataDirectory\|'''DataDirectory''']] parameter contains a relative path, this path will be resolved differently by the two modules, and data and log files will not be located in a common directory.		''Note:'' Data files are written by the [[Technical_Reference:Core_Modules#Data_Acquisition_Module\|source module]]; debug log files are maintained by the [[User_Reference:Operator_Module\|operator module]]. When source and operator module do not reside in the same directory, and the [[User Reference:DataIOFilter#DataDirectory\|'''DataDirectory''']] parameter contains a relative path, this path will be resolved differently by the two modules, and data and log files will not be located in a common directory.

	==See also==		==See also==

2008-08-08T18:43:52Z

Logging into Files

← Older revision		Revision as of 18:43, 8 August 2008
Line 54:		Line 54:

	Debug log files carry the name of the corresponding run file, and a ''.dbg'' extension.		Debug log files carry the name of the corresponding run file, and a ''.dbg'' extension.

			''Note:'' Data files are written by the �[[Technical_Reference:Core_Modules#Data_Acquisition_Module\|source module]]; debug log files are maintained by the [[User_Reference:Operator_Module\|operator module]]. When source and operator module do not reside in the same directory, and the [[User Reference:DataIOFilter#DataDirectory\|'''DataDirectory''']] parameter contains a relative path, this path will be resolved differently by the two modules, and data and log files will not be located in a common directory.

	==See also==		==See also==

2008-08-08T18:23:05Z

← Older revision		Revision as of 18:23, 8 August 2008
Line 45:		Line 45:
	FeedbackDemo 127.0.0.1 --DebugLevel=10		FeedbackDemo 127.0.0.1 --DebugLevel=10
	will start the FeedbackDemo module with a debug level of 10.		will start the FeedbackDemo module with a debug level of 10.

	Note that the debug level parameter will propagate to the other modules only after "Set Config" has been pressed from the operator module. Thus, other modules must be started with the DebugLevel argument, as well, if you need to view debugging messages from operation phases prior to the Initialization Phase.		Note that the debug level parameter will propagate to the other modules only after "Set Config" has been pressed from the operator module. Thus, other modules must be started with the DebugLevel argument, as well, if you need to view debugging messages from operation phases prior to the Initialization Phase.

			==Logging into Files==
			Debug messages may be logged into files residing in data directories, along with data files. This behavior is governed by the '''DebugLog''' parameter. As in the case of the '''DebugLevel''' parameter, this parameter must be specified from the command line when starting a module:
			FeedbackDemo 127.0.0.1 --DebugLevel=10 --DebugLog=1
			will enable debug messages, and log them to files.

			Debug log files carry the name of the corresponding run file, and a ''.dbg'' extension.

	==See also==		==See also==

2007-11-08T17:21:58Z

← Older revision		Revision as of 17:21, 8 November 2007
Line 50:		Line 50:
	[[Programming Reference:Errors and Warnings]], [[Technical Reference:States of Operation]]		[[Programming Reference:Errors and Warnings]], [[Technical Reference:States of Operation]]

	[[Category:Framework API]]		[[Category:Framework API]][[Category:Development]]

2007-11-08T17:20:44Z

← Older revision		Revision as of 17:20, 8 November 2007
Line 48:		Line 48:

	==See also==		==See also==
	[[Programming Reference:Errors and Warnings]]\|[[Technical Reference:States of Operation]]		[[Programming Reference:Errors and Warnings]], [[Technical Reference:States of Operation]]

			[[Category:Framework API]]

2007-11-07T10:26:15Z

← Older revision		Revision as of 10:26, 7 November 2007
Line 47:		Line 47:
	Note that the debug level parameter will propagate to the other modules only after "Set Config" has been pressed from the operator module. Thus, other modules must be started with the DebugLevel argument, as well, if you need to view debugging messages from operation phases prior to the Initialization Phase.		Note that the debug level parameter will propagate to the other modules only after "Set Config" has been pressed from the operator module. Thus, other modules must be started with the DebugLevel argument, as well, if you need to view debugging messages from operation phases prior to the Initialization Phase.

	~~----~~		==See also==
	See also: [[Programming Reference:Errors and Warnings]]\|[[Technical Reference:States of Operation]]		[[Programming Reference:Errors and Warnings]]\|[[Technical Reference:States of Operation]]

2007-11-07T10:18:11Z

← Older revision		Revision as of 10:18, 7 November 2007
Line 48:		Line 48:

	----		----
	See also: [[Programming Reference:~~Error Handling~~]]\|[[Technical Reference:States of Operation]]		See also: [[Programming Reference:Errors and Warnings]]\|[[Technical Reference:States of Operation]]

2007-11-07T10:12:44Z

Message Debug Level

← Older revision		Revision as of 10:12, 7 November 2007
Line 35:		Line 35:
	The default message debug level is 1.		The default message debug level is 1.
	bcidbg << "This is an important message on any level of debugging" << endl;		bcidbg << "This is an important message on any level of debugging" << endl;
	To give a message a higher debug level, put it in brackets after the <tt>bcidbg</tt> name:		To give a message a higher debug level, put the level in brackets after the <tt>bcidbg</tt> name:
	bcidbg( 10 ) << "This is a fairly uninteresting message" << endl;		bcidbg( 10 ) << "This is a fairly uninteresting message" << endl;
	Although there is practically no upper limit to debug level values,		Although there is practically no upper limit to debug level values,

2007-11-07T10:11:45Z

← Older revision		Revision as of 10:11, 7 November 2007
Line 48:		Line 48:

	----		----
	See also: [[Error ~~Streams~~]]\|[[States of Operation]]		See also: [[Programming Reference:Error Handling]]\|[[Technical Reference:States of Operation]]