Hello I am interested in using the PFM version of the cfdem coupled model. However, I need some help with the compilation process and changes that are required to be made in the bashrc file. Forums: CFDEM®coupling - User ForumLog...
以下为在Ubuntu20.04编译的步骤(需要说明的是编译CFDEM步骤1.3不是必须的,跳过也可编译成功): 1、下载LIGGGHTS和LPP安装包,编译LIGGGHTS,编译过程中发现LIGGGHTS-PFM单进程编译会卡住失败,尝试了多进程编译make fedora -j 4 1.1 Install prerequisites: sudo apt-get install build-essential cmake openmpi-bin libopenm...
Hello, everyone! I am trying to compile the full CFDEM-PFM, and I have successfully installed OpenFOAM-6 and the corresponding version of paraview. When I type cfdemSysTest into the terminal, it shows no problem. *** * C F D E M (R) c o u p l i n g * * * * by ...
CFDEM搬砖人 2023年06月10日 · 投稿了视频 00:06 CFDEMcoupling-PFM多相流计算:溃坝中的颗粒运动 - 277 0 转发 3 2 你已经到达世界的尽头 个人资料 UID503206537 学校哈尔滨工程大学 登录后你可以: 免费看高清视频 多端同步播放记录 发表弹幕/评论 热门番剧影视看不停 首次使用? 点我注册 ...
error when compiling CFDEMcoupling-PFM Byjennifer7 months 3 weeks ago 0n/a Normal topic fvOptions isn't working in CFDEM coupling Byyeting6 years 6 months ago 8Byjennifer8 months 2 days ago Normal topic ISSUE COMPILING CFDEM-coupling LIGGGHTS public 3.7.0 WITH VORONOI package ...
ERROR: Bond atoms I J missing on proc # [LIGGGHTS-PFM] Imprint: CFDEMresearch GmbH | Industriezeile 35, 4020 Linz, Austria | +43-732-9022-2200 |
Hello, I keep getting a segmentation fault when I start approaching 40 cells / diameter. Under 30 cells / diameter is fine, and I have this issue both on my laptop and the cluster at my univesity. I'm running this with cfdem-pfm, though I recall having what initially appeared to be ...
Normal topic Help! Can't run tutorial examples! Byvafaei7 months 1 week ago 0n/a Normal topic ABOUT cfdemSloverIB and fvOptions Byjennifer8 months 2 weeks ago 1Bymostanad7 months 2 weeks ago Normal topic cfdem-pfm Bylcy12945106027 months 3 weeks ago ...
Powder compaction capability in Liggghts Do we have powder compaction and particle breakage capability in Liggghts?
This is to avoid doing the intersection check again, as that is both unnecessary to do twice and computationally expensive. This value is however accessed through the contact_history with the help of an offset which is private. And while there are tags stored in pair_gran.history_arg it is...