code_saturne User's Forum

Hello, Could you provide the recommened usage info (i.e. at least the version you're using) ? Yes, in src/base/varpos.f90 (in the code sources), you'll find: if (iviext.gt.0) then nproce = nproce + 1 ivisla = nproce call field_set_n_previous(iprpfl(iviscl), 1) nproce = nproce + 1 ivista = nproce cal...

Hello,

Sorry, I've been very busy lately, and forgot to remind my colleague to check this thread.

I just sent him an e-mail a few minutes ago, so you can hope for a reply within a few days...

Best regards,

Yvan

Hello, Yes, this should be possible, though exchanging deformation info through coupling might not be automated yet, so minor developments would be need to extend the current coupling scheme. You might also be able to separate your domains using a "thin wall", which, todays, splits interio...

Hello, I took a quick look at your user subroutines, and did not see anything suspicious, but as an additional precaution, can you check if you reproduce the issue without user subroutines ? If you still have the issue, running with a debug build of the code (i.e. configured with --enable-debug=true...

Hello,

You should integrate the (vector) over the whole obstace.

Actually, "efforts" are a stress (i.e. peru unit surface) value, and were renamed in 4.2 to make things clearer.

So you need to sum efforts.surface_norma over boundary faces of the obstacle.

Regards,

Yvan

Hello,

Yes, this will rotate the whole mesh.

Basically, the general transformation matrix logic is briefly explained in cs_user_mesh.c, in cs_user_periodicity, example 3.

Regards,

Yvan

Hello, According to the backtrace, the error occurs during the parallel syncing of probe data, so it might be partition-dependent, which makes reproducing it without your data quite difficult (and possibly partitioning output file, if you are using Scotch or Metis)... I recommend upgrading to 4.0.4,...

Hello,

No, this might be a bug.

Which version are you using ? Is your case small enough and non-confidential so that you can post it here ?

Regards,

Yvan

Hello, cs_user_mesh_input is probably the simplest solution if you only need a combination of translations and rotations (which can be expressed in a homogeneous coordinates transformation matrix). For more general deformations not requiring remeshing, cs_user_mesh_modify should be enough. For more ...

Hello,

For the "stream tracer" in ParaView, how did you specify your source (ParaView sets a single point source by default, do if you do not place the point or replace it with a line source, you often don't get much) ?

Regards,

Yvan