code_saturne User's Forum

Hello,

I'd like to add monitoring points in the postprocessing tab with an imported csv file but . I created a csv file including probe coordinates as follows :

• n name x y z
  1 1 x1 y1 z1
  2 2 x2 y2 z2

Do you have an idea why the coordinates are not well imported ?

Thank you in advance

Hello,

I am not sure about this part of the GUI code, but could you try either/and :

-without the first (id) column ?
- without the first (legend) row ?

The decimal separator . or , depending on the language might also have an impact (that is one of the issues with text formats such as csv, for which we might not handle all cases yet).

best regards,

Yvan

Hello Yvan,

Thank you for your reply.
I tried multiple combination, with/without the first row, using space, dot or comma.

I will continue the trials

Hello,

You can send me a csv file so I can try.

Regards,

Yvan

Hello Yvan,

Here is an example of a working csv file.
The following syntax shall be fulfilled (Example for 3 monitoring probes) :

x,y,z
0.1,0.1,0.5
0.2,0.7,0.4
0.7,0.5,0.3

Comma must be use as letters and values separator

Hope it will help some users

Hello,

Thanks for the feedback. This seems related to the fact that .csv files can be interpreted with locale settings for handling of decimal points and separators, which is one of the painful aspects of text files.

We should try to improve the reader to handle more cases.

Best regards,

Yvan

Quentin01 wrote: ↑Mon Nov 15, 2021 11:36 am Hello Yvan,

Here is an example of a working csv file.
The following syntax shall be fulfilled (Example for 3 monitoring probes) :

x,y,z
0.1,0.1,0.5
0.2,0.7,0.4
0.7,0.5,0.3

Comma must be use as letters and values separator

Hope it will help some users

Yes it sure does.Thanks a bunch.
Also since you achived this do you know if I could in some way input the inlet velocity as a table in some way?As only using formula is availbe in the GUI.

Hello,

Using a table for inlet velocity values is not available from the GUI, and users doing that need to read the table and match inlet coordinates to table entries in cs_user_boundary_conditions, for which I am not sure we have any simple examples (the ones I have are from industrial studies which are not public).

This definitely would be a nice feature to have, an is on our TODO list (but with many other things on that list).

Best regard,

Yvan