DEME 2.1.7__tar.gz → 2.1.8__tar.gz

{deme-2.1.7/deme.egg-info → deme-2.1.8}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: deme
-Version: 2.1.7
+Version: 2.1.8
 Summary: PyBind Wrapper Library for DEM-Engine
 Author: Ruochun Zhang
 Author-email: ruochunz@gmail.com

{deme-2.1.7 → deme-2.1.8/deme.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: deme
-Version: 2.1.7
+Version: 2.1.8
 Summary: PyBind Wrapper Library for DEM-Engine
 Author: Ruochun Zhang
 Author-email: ruochunz@gmail.com

{deme-2.1.7 → deme-2.1.8}/setup.py

@@ -152,7 +152,7 @@ class CMakeBuild(build_ext):
 # logic and declaration, and simpler if you include description/version in a file.
 setup(
     name="deme",
-    version="2.1.7",
+    version="2.1.8",
     author="Ruochun Zhang",
     author_email="ruochunz@gmail.com",
     description="PyBind Wrapper Library for DEM-Engine",

{deme-2.1.7 → deme-2.1.8}/src/DEM/kT.cpp

@@ -656,9 +656,9 @@ void DEMKinematicThread::allocateGPUArrays(size_t nOwnerBodies,
             DEME_DEVICE_ARRAY_RESIZE(familyID_buffer, nOwnerBodies);
         }
 
-        DEME_DEVICE_ARRAY_RESIZE(relPosNode1_buffer, nOwnerBodies);
-        DEME_DEVICE_ARRAY_RESIZE(relPosNode2_buffer, nOwnerBodies);
-        DEME_DEVICE_ARRAY_RESIZE(relPosNode3_buffer, nOwnerBodies);
+        DEME_DEVICE_ARRAY_RESIZE(relPosNode1_buffer, nTriGM);
+        DEME_DEVICE_ARRAY_RESIZE(relPosNode2_buffer, nTriGM);
+        DEME_DEVICE_ARRAY_RESIZE(relPosNode3_buffer, nTriGM);
 
         // Unset the device change we just did
         DEME_GPU_CALL(cudaSetDevice(streamInfo.device));

{deme-2.1.7 → deme-2.1.8}/src/demo/DEMdemo_FlexibleMesh.cpp

@@ -141,8 +141,8 @@ int main() {
     DEMSim.Initialize();
 
     // After system initialization, you can still get an handle of the mesh components using trackers (GetMesh method).
-    // But note that if you do changes using this handle, the changes are done to the mesh and it immediate affects the
-    // simulation. So sometimes you want to copy the information you are after and keep for your record.
+    // But note that if you do changes using this handle, the changes are done to the mesh and it immediately affects
+    // the simulation. So sometimes you want to copy the information you are after and keep for your record.
     auto mesh_handle = flex_mesh_tracker->GetMesh();
     // This is keeping a copy of the RELATIVE (to the CoM) locations of the mesh nodes. In our case, the Z coordinates
     // of these nodes range from -0.5 to 0.5.