particle simulation

[frpageot]

Hello,

For paraview you can have the particle motion, and the filament view exactly as ensight, thought this soft is less powerfull from what I understood (but I have not spent so much time on ensight to argue on this point). To vizualize this just open the deplacement.case and trajectoires.case files and that's it. for the manual, you can find it on their internet website, this is where I downloaded mine.

[Fabio89]

Thank You for your helpful reply Fred

Best Regards,

Fabio

[Fabio89]

Hello everybody

Learning from these posts and "key words in GUI" too and looking better and better user's guide, I tried a simulation using:

-Post-pro format: MED
-Threshold for statistical weight = 1.0
-Particles and droplets tracking -> Output: no trajectory mode & no displacement mode
-Boundary Condition ->
(wall) particles deposit+memory
(inlet) number of classes = 1
statistical weight = 1.0
fliud velocity
diameter = 1e-06
variance = 1e-07

But I have thi ERROR:

@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@
@ @@ ATTENTION : ARRET A L'EXECUTION DU MODULE LAGRANGIEN
@ ========= (LAGENT)
@
@ LES CONDITIONS AUX LIMITES SONT ERRONEES
@
@ La condition a la limite representee par la variable
@ IDEPO2 n'est admissible que pour un post-processing
@ en mode deplacement IENSI2 = 1 .
@
@ Le calcul ne peut etre execute.
@
@ Verifier la valeur de IENSI2 dans USLAG1 et les
@ conditions aux limites pour la frontiere NB = 3
@ dans USLAG2.
@
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@


Call stack:
1: 0x7f083cd0a87e <lagent_+0x383e> (libsaturne.so.0)
2: 0x7f083cd36f5f <lagune_+0x7bf> (libsaturne.so.0)
3: 0x7f083ca27193 <caltri_+0x59a3> (libsaturne.so.0)
4: 0x7f083ca019e3 <cs_run+0x843> (libsaturne.so.0)
5: 0x7f083ca01cc5 <main+0x1f5> (libsaturne.so.0)
6: 0x7f08391a0c4d <__libc_start_main+0xfd> (libc.so.6)
7: 0x40a359 <> (cs_solver)
End of stack

but in GUI I didn't set deplacement mode, so I'm sure about IENSI2=0 (and IENSI1=0 too)

After that, in soubroutine USLABO, I read this:

9010 format( &
'@ ',/,&
'@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@',/,&
'@ ',/,&
'@ @@ ATTENTION : STOP IN THE EXECUTION OF THE LAGRANGIAN MODULE ',/,&
'@ ========= (USLABO) ',/,&
'@ ',/,&
'@ the normal of a boundary face is perpendicular to ',/,&
'@ a PQ ray : impossible ',/,&
'@ ',/,&
'@ The particle ',I10,' is ELIMINATED ',/,&
'@ ',/,&
'@ Please contact the development team. ',/,&
'@ ',/,&
'@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@',/,&
'@ ',/)

9020 format( &
'@ ',/,&
'@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@',/,&
'@ ',/,&
'@ @@ ATTENTION : STOP IN THE EXECUTION OF THE LAGRANGIAN MODULE ',/,&
'@ ========= (USLABO) ',/,&
'@ ',/,&
'@ The type of boundary condition IUSCLB ',/,&
'@ is not defined for the boundary NB = ',I10 ,/,&
'@ ',/,&
'@ The calculation cannot be run. ',/,&
'@ ',/,&
'@ Please check USLAG2 and USLABO. ',/,&
'@ ',/,&
'@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@',/,&
'@ ',/)

Could anyone help me one more time?
Thankyou so much

Best Regards,

Fabio

[guingo]

Hi Fabio,

in the version you use, the "deposit+memory" boundary condition is only possible when the displacement and/or trajectory post-processings are activated (that is what the message in french reads), so basically setting IENSI2 to 1 is needed. The reason is that this particular boundary condition was originally implemented for post-processing purpose only.

Concerning what you read in uslabo, you should not be worried as long as these error messages do not appear in your listing files

Best regards,
Mathieu

[Fabio89]

Oh, great!
Always very intelligible.

You said "the "deposit+memory" boundary condition is only possible when the displacement and/or trajectory post-processings are activated", but at first I would like to show off particles on my sampling plate (so I thought to deposit+memory) from output STATISTICAL_WEIGHT; in this way I would know how many particles run away from the inertial impactor and how many I could sample.
Using deposit+memory can I pull out this? or memory option is valid only for displacement and trajectory outputs?

Best Regards,

Fabio