You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The CVS output of noise analysis generated by .PRINT statement has an issue. The column names should be quoted with double quotes because they can contain a comma (for instance DNO(M1,ID)) and comma is also the separator. So this causes a confusion when the CSV file is loaded by tools like Python datatable.
An option with which one could set the separator would also be welcome because many tools allow the use of different separators in addition to the standard comma. Setting a different separator would be an alternative way to solving the DNO(M1,ID) problem.
Best regards,
Arpad
The text was updated successfully, but these errors were encountered:
Thanks for this feedback. I can see why this would be a problem, with the comma being ambiguous.
At least one of the other file formats (tecplot) puts quotes around output variable names. So, it isn't out of the question to do this. I'll open an internal issue about this.
Hi,
The CVS output of noise analysis generated by .PRINT statement has an issue. The column names should be quoted with double quotes because they can contain a comma (for instance DNO(M1,ID)) and comma is also the separator. So this causes a confusion when the CSV file is loaded by tools like Python datatable.
An option with which one could set the separator would also be welcome because many tools allow the use of different separators in addition to the standard comma. Setting a different separator would be an alternative way to solving the DNO(M1,ID) problem.
Best regards,
Arpad
The text was updated successfully, but these errors were encountered: