{"id":164706,"date":"2023-03-17T08:58:27","date_gmt":"2023-03-17T08:58:27","guid":{"rendered":"\/knowledge\/forums\/topic\/polyflow-issues-with-initialization-of-a-field-transport-variable-or-species-through-a-csv-file\/"},"modified":"2023-07-31T12:26:06","modified_gmt":"2023-07-31T12:26:06","slug":"polyflow-issues-with-initialization-of-a-field-transport-variable-or-species-through-a-csv-file","status":"publish","type":"topic","link":"https:\/\/innovationspace.ansys.com\/knowledge\/forums\/topic\/polyflow-issues-with-initialization-of-a-field-transport-variable-or-species-through-a-csv-file\/","title":{"rendered":"POLYFLOW: Issues with initialization of a field (transport variable or species) through a CSV file"},"content":{"rendered":"

A transport variable (species) is created and initialized through a CSV file. It happens that the field is not properly initialized. Why is that? This may happen when the transport variable has a short name which leads to a possible confusion with another field. A typical example is when the transport variable is named C (standing for concentration, why not) and which leads to confusion with the COORDINATES field whose first letter matches that of the transport variable. Replacing C e.g. with Conc would be a convenient remedy. Along the same idea, species names that may be confused with possibly existing fields should be avoided. In other words, avoid names such as T or V as they may potentially refer to TEMPERATURE or VELOCITY respectively.<\/p>\n","protected":false},"template":"","class_list":["post-164706","topic","type-topic","status-publish","hentry","topic-tag-4424","topic-tag-fluid-dynamics","topic-tag-general","topic-tag-polyflow"],"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