Search found 4070 matches
- Thu Jun 02, 2016 10:40 pm
- Forum: code_saturne usage
- Topic: Gradient of user computed field
- Replies: 2
- Views: 3297
Re: Gradient of user computed field
Hello, For fields that do not represent resolved variables, the only solution for this is to use the "low level" functions, for which you need to define variable condition arrays... Check src/alge/cs_gradient.h in the sources, or the Doxyhen documentation (not sure how far it goes into det...
- Thu Jun 02, 2016 10:17 pm
- Forum: code_saturne usage
- Topic: user_physical properties.f90
- Replies: 14
- Views: 8683
Re: user_physical properties.f90
Hello,
This may mean you have an incorrect (or badlly initialized) value one one proc. Is the case small enough to run on 1 proc for 1 or 2 times steps, for debugging ?
Regards,
Yvan
This may mean you have an incorrect (or badlly initialized) value one one proc. Is the case small enough to run on 1 proc for 1 or 2 times steps, for debugging ?
Regards,
Yvan
- Thu Jun 02, 2016 10:13 pm
- Forum: code_saturne usage
- Topic: coupling with syrthes failure
- Replies: 15
- Views: 10314
Re: coupling with syrthes failure
Hello,
I did not see any obvious error, but since you have 2 fluid domains, could you post both listing files. Murphy's law helping, the interesting info might be in the one you omitted... Also, did you try coupling one domaon at a time ?
Regards,
Yvan
I did not see any obvious error, but since you have 2 fluid domains, could you post both listing files. Murphy's law helping, the interesting info might be in the one you omitted... Also, did you try coupling one domaon at a time ?
Regards,
Yvan
- Fri May 27, 2016 12:27 am
- Forum: code_saturne usage
- Topic: Plotting particle trajectories in ParaView
- Replies: 4
- Views: 4686
Re: Plotting particle trajectories in ParaView
Hello,
You also need to set the type of the trajectory writer to "trajectory" (and not particles). The type is actually more important than the name.
Regards,
Yvan
You also need to set the type of the trajectory writer to "trajectory" (and not particles). The type is actually more important than the name.
Regards,
Yvan
- Fri May 27, 2016 12:06 am
- Forum: code_saturne usage
- Topic: user_physical properties.f90
- Replies: 14
- Views: 8683
Re: user_physical properties.f90
Hello, The numbering depends on the physical model and how many scalars you use. User-defined scalas should come first. This is why it is recommended to use the field names. (Simply avoid using names in loops over elements (for performance reasons), by obtaining the id of a field of a given name out...
- Wed May 25, 2016 9:55 pm
- Forum: code_saturne usage
- Topic: Plotting particle trajectories in ParaView
- Replies: 4
- Views: 4686
Re: Plotting particle trajectories in ParaView
Hello, I'm not sure ParaView can directly plot trajectories, at least in the Code_Saturne case (most particle-oriented formats such as h5part or associated viewers assume a constant number of particles). You can activate a dedicated trajectory writer an associate a trajectory mesh (a succession of s...
- Wed May 25, 2016 9:50 pm
- Forum: code_saturne usage
- Topic: user_physical properties.f90
- Replies: 14
- Views: 8683
Re: user_physical properties.f90
Hello, The message is related to trying to access a field of vectors as a field of scalars, or vice versa. At the root of this, you probably tried accessing the wrong fields, so you should check your field numbering (and be careful with the ivarfl() indirection, or use field_get_val_s_by_name / fiel...
- Wed May 25, 2016 9:48 pm
- Forum: code_saturne usage
- Topic: Two-way coupling code_saturne / code_aster
- Replies: 31
- Views: 56080
Re: Two-way coupling code_saturne / code_aster
Hello,
Great. I may have limited network connection next week, but at worse, I'll check on my return. If none of this works, I'll see with the colleagues who last ran this model (but the person who did most of that work may not be easily available).
Regards,
Yvan
Great. I may have limited network connection next week, but at worse, I'll check on my return. If none of this works, I'll see with the colleagues who last ran this model (but the person who did most of that work may not be easily available).
Regards,
Yvan
- Wed May 25, 2016 9:44 pm
- Forum: code_saturne usage
- Topic: Jacobi: error (divergence) solving for Velocity
- Replies: 17
- Views: 13042
Re: Jacobi: error (divergence) solving for Velocity
Hello,
I'll try to remember to mention this thread to the developper who last worked on the cavitation model, to see if he has any suggestions. I am not familiar with that model myself, and am a bit short on time these days (already too many threads to follow).
Regards,
Yvan
I'll try to remember to mention this thread to the developper who last worked on the cavitation model, to see if he has any suggestions. I am not familiar with that model myself, and am a bit short on time these days (already too many threads to follow).
Regards,
Yvan
- Fri May 20, 2016 6:30 pm
- Forum: code_saturne usage
- Topic: Two-way coupling code_saturne / code_aster
- Replies: 31
- Views: 56080
Re: Two-way coupling code_saturne / code_aster
Hello Flavio, I ran quick test on my side, and also have an error, but only for the FSI_ASTER component: +++++++++++++++++++ start calculation +++++++++++++++++++ th. 140568750806784 - Trace /home/I27518/TRAV/C2015_2/V2015_2_calibre_7/modules/src/KERNEL/src/Container/SALOME_ContainerManager.cxx [620...