Open topic with navigation
Records a user-defined data sample and enables logging option.
int lr_user_data_point_ex( const char *sample_name, double value, int log_flag );
|Example: lr_user_data_point_ex||Informational Functions|
|sample_name||A string indicating the name of the sample type.|
|value||The value to record.|
|log_flag||Determines whether the data point should be logged or not: DP_FLAGS_NO_LOG (1) DP_FLAGS_STANDARD_LOG (2) DP_FLAGS_EXTENDED_LOG (3)|
The lr_user_data_point_ex function is the same as lr_user_data_point except that lr_user_data_point_ex has an additional parameter, log_flag.
Logging means writing data to a file. lr_user_data_point_ex enables you to write a data point to the Vuser log file. When run in VuGen, the output is output.txt
You may want to write the data point conditionally according to how important the data to be logged is. It can either be part of a Standard level when only the most important information is logged or an Extended level, when fuller control over logging is required.
log_flag denotes the log level and corresponds to the settings found in VuGen's Log runtime setting. This setting specifies how the script handles logging to a file during execution. If DP_FLAGS_EXTENDED_LOG is passed to lr_user_data_point_instance_ex then the data point is logged only when the Extended runtime Log setting is currently activate. If log_flag is DP_FLAGS_STANDARD_LOG then it will be logged only if the Standard setting is active. DP_FLAGS_NO_LOG indicates that this data point is never written to a log file.
This function returns 0 if it succeeds, and -1 if it fails to write the sampled data.
All string arguments (char type) can be parameterized using standard parameterization.