{"id":166954,"date":"2023-04-05T14:32:29","date_gmt":"2023-04-05T14:32:29","guid":{"rendered":"\/knowledge\/forums\/topic\/why-is-the-monitor-value-for-a-define_report_definition_fn-ansys-fluent-udf-zero\/"},"modified":"2023-07-31T12:27:48","modified_gmt":"2023-07-31T12:27:48","slug":"why-is-the-monitor-value-for-a-define_report_definition_fn-ansys-fluent-udf-zero","status":"publish","type":"topic","link":"https:\/\/innovationspace.ansys.com\/knowledge\/forums\/topic\/why-is-the-monitor-value-for-a-define_report_definition_fn-ansys-fluent-udf-zero\/","title":{"rendered":"Why is the monitor value for a DEFINE_REPORT_DEFINITION_FN ANSYS Fluent UDF zero?"},"content":{"rendered":"

When running Fluent parallel, ensure that you pass the return value to the host process that it can be used for reporting. If you use Message or Message0 for debugging your UDF (user-defined function), you should get the expected value because most calculations are done on the node processes. But monitoring is done by the Cortex process which gets its data from the host only. If you don’t pass the data to the host process, you get whatever is stored in memory. It might be zero but it can be any arbitrary number. You can find more information about message passing with node_to_host_* macros in the ANSYS Fluent Customization Manual, chapter “Communicating Between the Host and Node Processes”. For a detailed example that uses REPORT_DEFINITION_FN, refer to solution 2053120: How can an input parameter be used for report expressions in ANSYS Fluent?<\/p>\n","protected":false},"template":"","class_list":["post-166954","topic","type-topic","status-publish","hentry","topic-tag-4391","topic-tag-fluent","topic-tag-fluid-dynamics","topic-tag-general-fluent"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t