Coder Social home page Coder Social logo

particulateflow / liggghts-pfm Goto Github PK

View Code? Open in Web Editor NEW
44.0 44.0 36.0 79.17 MB

This is an academic adaptation of the LIGGGHTS software package, released by the Department of Particulate Flow Modelling at Johannes Kepler University in Linz, Austria http://www.jku.at/pfm

License: GNU General Public License v2.0

Roff 0.56% C 2.94% C++ 82.31% Makefile 0.36% Cuda 4.50% Shell 0.59% Fortran 2.95% Python 4.77% Gnuplot 0.01% CMake 0.03% Perl 0.47% Emacs Lisp 0.02% Arc 0.25% MATLAB 0.10% Awk 0.01% Rich Text Format 0.14% Odin 0.01% AMPL 0.01% Vim Script 0.01%

liggghts-pfm's People

Contributors

aaigner avatar achuth1992 avatar behradesg avatar ckloss avatar danielque avatar ekinaci avatar markoramius avatar pkieck avatar rbberger avatar tlichtenegger avatar tmjnijssen avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

liggghts-pfm's Issues

Issue with super-quadric particle simulation

Hello,
I am trying to do a simulation using superquadric particles. but it is showing error for the 'atom_style' command , then I tried the given example of superquadric particle in the package but it was also showing same error. To check if the mistake is on my end, I have ran the same simulation in two different computers, but they also end up with same error. Would you be able to look at the issue and reply me with a possible fix.

thanks.

Building with OpenMP fails on ubuntu 21.04

Using Cmake I get this error from release 21.11 trying to build with OpenMP

[ 99%] Building CXX object CMakeFiles/liggghts_bin.dir/main.cpp.o [100%] Linking CXX executable liggghts /usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::granular_nsq_newton_omp(LAMMPS_NS::NeighList*)'
/usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::respa_bin_newton_tri_omp(LAMMPS_NS::NeighList*)' /usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::half_multi_newton_omp(LAMMPS_NS::NeighList*)'
/usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::half_bin_no_newton_omp(LAMMPS_NS::NeighList*)' /usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::half_from_full_newton_omp(LAMMPS_NS::NeighList*)'
/usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::full_nsq_omp(LAMMPS_NS::NeighList*)' /usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::respa_bin_newton_omp(LAMMPS_NS::NeighList*)'
/usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::half_bin_newton_omp(LAMMPS_NS::NeighList*)' /usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::granular_nsq_no_newton_omp(LAMMPS_NS::NeighList*)'
/usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::granular_bin_no_newton_omp(LAMMPS_NS::NeighList*)' /usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::half_bin_newton_tri_omp(LAMMPS_NS::NeighList*)'
/usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::full_bin_omp(LAMMPS_NS::NeighList*)' /usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::granular_bin_newton_tri_omp(LAMMPS_NS::NeighList*)'
/usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::full_bin_ghost_omp(LAMMPS_NS::NeighList*)' /usr/bin/ld: libliggghts.so: undefined reference to vtable for LAMMPS_NS::DomainOMP'
/usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::respa_nsq_newton_omp(LAMMPS_NS::NeighList*)' /usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::half_nsq_no_newton_ghost_omp(LAMMPS_NS::NeighList*)'
/usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::half_multi_newton_tri_omp(LAMMPS_NS::NeighList*)' /usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::half_from_full_no_newton_omp(LAMMPS_NS::NeighList*)'
/usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::half_bin_no_newton_ghost_omp(LAMMPS_NS::NeighList*)' /usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::half_multi_no_newton_omp(LAMMPS_NS::NeighList*)'
/usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::respa_bin_no_newton_omp(LAMMPS_NS::NeighList*)' /usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::full_nsq_ghost_omp(LAMMPS_NS::NeighList*)'
/usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::respa_nsq_no_newton_omp(LAMMPS_NS::NeighList*)' /usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::half_nsq_no_newton_omp(LAMMPS_NS::NeighList*)'
/usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::full_multi_omp(LAMMPS_NS::NeighList*)' /usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::granular_bin_newton_omp(LAMMPS_NS::NeighList*)'
/usr/bin/ld: libliggghts.so: undefined reference to LAMMPS_NS::Neighbor::half_nsq_newton_omp(LAMMPS_NS::NeighList*)' collect2: error: ld returned 1 exit status make[2]: *** [CMakeFiles/liggghts_bin.dir/build.make:232: liggghts] Error 1 make[1]: *** [CMakeFiles/Makefile2:138: CMakeFiles/liggghts_bin.dir/all] Error 2 make: *** [Makefile:136: all] Error 2

break not working with superquadric model

hey,
I am trying to break superquadric particles but i am getting error -
//
pair_style gran model hertz/break tangential history rolling_friction epsd2 surface superquadric
ERROR on proc 0: unknown contact model (/home/cape/CFDEM/LIGGGHTS-PFM/src/pair_gran_proxy.cpp:82)
//
Would you be able to look at the issue and reply me with a possible fix.
thanks alot.

Compilation of LIGGGHTS-PFM stuck

Hello,

Compilation of LIGGGHTS-PFM on Linux Centos 8 is stuck at 67%:

[ 65%] Building CXX object CMakeFiles/liggghts.dir/fix_wall_reflect.cpp.o
[ 65%] Building CXX object CMakeFiles/liggghts.dir/fix_wall_region.cpp.o
[ 65%] Building CXX object CMakeFiles/liggghts.dir/fix_wall_region_sph.cpp.o
[ 66%] Building CXX object CMakeFiles/liggghts.dir/fix_wall_sph.cpp.o
[ 66%] Building CXX object CMakeFiles/liggghts.dir/fix_wall_sph_general_simple.cpp.o
[ 66%] Building CXX object CMakeFiles/liggghts.dir/force.cpp.o
[ 66%] Building CXX object CMakeFiles/liggghts.dir/global_properties.cpp.o
[ 67%] Building CXX object CMakeFiles/liggghts.dir/granular_pair_style.cpp.o
[ 67%] Building CXX object CMakeFiles/liggghts.dir/granular_styles.cpp.o

What dit I did wrong ?

Dump of pair vtk file

Hi,
In previous LIGGGHTS, this is a dump pair/gran/vtk command to dump the information about pair force or something. If there is still such a function in the latest version of LIGGGHTS-PFM? Thanks!
Sincerely,
Fan

Coarse grained method applied in heat conduction model

Hello,

I am trying to use the LIGGGHTS-PFM 21.11 to model coarse-grained particles in terms of flow and heat transfer process, but I failed to implement the model on LIGGGGHTS. The error is reported as:
"ERROR: The following model does not yield consistent results with coarse-graining: heat/gran (/home/561/dx4858/CFDEM/LIGGGHTS/src/fix_heat_gran_conduction.cpp:202)"

The notable changes of the version have mentioned that the coarse-graining factors in scalar transport equation (e.g. used for heat conduction) have been fixed. Therefore, I want to know whether the version can support coarse-grained method in heat transfer models and how to implement it properly.

Many thanks for your time and help.
Best regards.
Dan

Segmentation Fault Error when using Balance with granular bonds

Hello,
I have come across the above issue while testing out the bond code with the fix balance command.
I have tracked the issue down to the segmentation fault happening in atom_vec_bond_gran.cpp where values are attempted to be set in the bond history variable. The issue comes down to how the atom class is initialized. By default, the class initializes with 0 bond history values. Then later on the code sets that the history values are now greater than 0 but no call is made to reinitialize the atom class, leading to this error. I have made a hot fix on my local copy by setting the n_bondhist value to 13 in atom.cpp.

Attached is the chute wear example with the bond calls and fix balance call added.
chute_wear.zip

Unexpected behavior of region command using VTK

Hello there,

if I create a region from sample.vtk (attached) using the 'region' command i.e.

region sampleRegion mesh/tet file sample.vtk scale 1 move 0 0 0 rotate 0 0 0 units box

and attempt to remove particles from that region with:

delete_atoms region sampleRegion compress yes

I discover only some atoms are deleted (close to the 'acute' corners). I am wondering
therefore if the format of sample.vtk is incorrect. (Testing at differing resolutions of sample.vtk
yields the same unexpected behaviour).

The format of sample.vtk seems consistent with the following:

examples/LIGGGHTS/PFM/adaptive_resolution/bin_fill/meshes/surface2x1.vtk
examples/LIGGGHTS/Tutorials_public/mesh_tet/data/test.vtk

and where it was constructed with the following steps:

i) create geometry and mesh in Gmsh
ii) export sample.msh -> sample.stl
iii) tetgen -pk sample.stl ---> sample.vtk (for pure tet mesh)

Any ideas I wonder?

Many prospective thanks,
Richard
sample.zip
.

Documentation missing fix couple/cfd and fix couple/cfd/force.

Hi,
would be nice if you could add description of fixes fix couple/cfd and fix couple/cfd/force. As several extension fixes (e.g. fix couple/cfd/chemistry) requires those: This fix needs a fix couple/cfd before it is defined.. :-)

Edit: And couple/cfd/convection is missing as well.

Btw. great job with the compressible solver.

Build failing for mpi_liggghts.cpp

Build of the current LIGGGHTS-PFM is failing for mpi_liggghts.cpp.

Archlinux 2022.01.01
gcc (GCC) 11.1.0
-- Found MPI_C: /usr/lib/openmpi/libmpi.so (found version "3.1")
-- Found MPI_CXX: /usr/lib/openmpi/libmpi_cxx.so (found version "3.1")
-- Found MPI: TRUE (found version "3.1")

Edit:
This is caused by the new version gcc 10+.

[ 75%] Building CXX object CMakeFiles/liggghts.dir/mpi_liggghts.cpp.o
/home/jiri/apps/cfdem-pfm/LIGGGHTS-PFM/src/mpi_liggghts.cpp: In function ‘void LAMMPS_NS::mpi_abs_min_op(void*, void*, int*, ompi_datatype_t**)’:
/home/jiri/apps/cfdem-pfm/LIGGGHTS-PFM/src/mpi_liggghts.cpp:85:5: error: ‘printf’ was not declared in this scope
   85 |     printf("unsupported data type\n");
      |     ^~~~~~
/home/jiri/apps/cfdem-pfm/LIGGGHTS-PFM/src/mpi_liggghts.cpp:32:1: note: ‘printf’ is defined in header ‘<cstdio>’; did you forget to ‘#include <cstdio>’?
   31 | #include <algorithm>
  +++ |+#include <cstdio>
   32 | 
/home/jiri/apps/cfdem-pfm/LIGGGHTS-PFM/src/mpi_liggghts.cpp: In function ‘void LAMMPS_NS::mpi_abs_max_op(void*, void*, int*, ompi_datatype_t**)’:
/home/jiri/apps/cfdem-pfm/LIGGGHTS-PFM/src/mpi_liggghts.cpp:134:5: error: ‘printf’ was not declared in this scope
  134 |     printf("unsupported data type\n");
      |     ^~~~~~
/home/jiri/apps/cfdem-pfm/LIGGGHTS-PFM/src/mpi_liggghts.cpp:134:5: note: ‘printf’ is defined in header ‘<cstdio>’; did you forget to ‘#include <cstdio>’?
make[2]: *** [CMakeFiles/liggghts.dir/build.make:4696: CMakeFiles/liggghts.dir/mpi_liggghts.cpp.o] Error 1

#include "string.h" missing

Hi old colleagues,

There might be a #include "string.h" missing in compute_com_molecule.cpp in the latest version (PFM 20.09). I could not compile without adding it.

All the best, Daniel

How to run the run.config in the example cases

Hi,

I am recently learning the example case of the multisphere/creat_clump. I know I have to run the in.create_clump first to generate the particle data and then run the in.multisphere. Firstly, I use the command "liggghts < in.create_clump" to run the task 1, but it does not work. I notice there is a file with the name of run.config. I do not know how to run the files. Can you help me in running the cases? Many thanks for your help and time.

Best regards,
Dan

Inquiry about the Validation of Wall Lubrication

I have conducted a simple test calculation to examine the presence of wall lubrication. The approach involved dropping a single particle and allowing it to collide with the wall, followed by observing the distance it rebounded. I performed this validation by comparing the results at a viscosity of 1 Pa·s and 0 Pa·s. Surprisingly, both scenarios yielded identical outcomes.

I am uncertain whether there is an issue with my program or if the source code might be at fault.
Below, I have attached the relevant segment of my code for reference.

Any insights or guidance on this matter would be greatly appreciated.

Thank you

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.