penn-graphics-research / claymore Goto Github PK

License: MIT License

CMake 3.26% C++ 35.61% Cuda 60.77% Python 0.36%

cuda cpp14 mpm simulation-framework high-performance-computing gpu-computing physics-based-simulation

claymore's Issues

CUDA error at D:\claymore\Projects\MGSP\mgsp_benchmark.cuh:33 code=2(cudaErrorMemoryAllocation) "cudaMalloc(&ret, bytes)"

Hi,
When I run MGSP with case 2 and constexpr int g_device_cnt = 1;, the program was able to generate 11 frames, then at step 4238 this error CUDA error at D:\claymore\Projects\MGSP\mgsp_benchmark.cuh:33 code=2(cudaErrorMemoryAllocation) "cudaMalloc(&ret, bytes)" popped out and the program just stuck there. (At the end of the post you can see the information for step 4237 and step 4238.) What could be the problem?

I am using a Windows machine with Quadro P2000. The initialization info. is the following:

   [InitInfo -- DevNum] Detected 1 CUDA Capable device(s)
   [InitInfo -- DevNum] Prepare to use 1 device(s) in Multi-GPU test
   [InitInfo -- Dev Property] GPU device 0 (0-th group on board)
   global memory: 4294967296 bytes                
   shared memory per block: 49152 bytes,               
   registers per SM: 65536,
   Multi-Processor count: 6,
   SM compute capabilities: 6.1.
   [InitInfo -- stream] Create 32 streams for device 0
   monotonic allocator alignment (Bytes): 512      size (MB): 421.366
   [InitInfo -- memory] device 0                
   free bytes/total bytes: 3534671054/0,
   pre-allocated size: 441833881 bytes
  [Init] CudaContext 0
  [InitInfo -- Default Dev] Default context: 0
  [Init -- End] == Finished 'Cuda' initialization

The information for step 4237 and step 4238 is:

←[0m←[38;2;000;255;255mGPU[0] frame 11 step 4237 grid_update_query: 0.261056 ms
←[0m←[1m----------------------------------------------------------------
←[0m←[1m0.42346576 --0.0001--> 0.45833334, defaultDt: 0.0001, maxVel: 2.8010573
←[0m←[38;2;000;255;255mGPU[0] frame 11 step 4237 halo_g2p2g: 0.221856 ms
←[0m←[1m----------------------------------------------------------------
←[0m←[1m----------------------------------------------------------------
←[0m←[38;2;000;255;255mGPU[0] step 4237 collect_send_halo_grid: 0.0012 ms
←[0m←[1m----------------------------------------------------------------
←[0m←[38;2;000;255;255mGPU[0] frame 11 step 4237 non_halo_g2p2g: 13.597696 ms
←[0m←[1m----------------------------------------------------------------
←[0m←[38;2;000;255;255mGPU[0] step 4237 receive_reduce_halo_grid: 0.0171 ms
←[0m←[1m----------------------------------------------------------------
←[0m←[38;2;000;255;255mGPU[0] frame 11 step 4237 update_partition: 2.519936 ms
←[0m←[38;2;000;255;255mGPU[0] frame 11 step 4237 build_partition_for_grid: 0.105344 ms
←[0m←[38;2;000;255;255mGPU[0] frame 11 step 4237 copy_grid_blocks: 0.494464 ms
←[0m←[1m----------------------------------------------------------------
←[0m←[1m----------------------------------------------------------------
←[0m←[1m----------------------------------------------------------------
←[0m←[38;2;000;255;255mGPU[0] step 4237 halo_tagging: 0.291648 ms
←[0m←[38;2;000;128;000mhalo particle blocks[0]: 0
←[0m←[38;2;000;128;000mhalo grid blocks[0][0]: 0
←[0m←[1m----------------------------------------------------------------
←[0m←[1m←[38;2;255;255;000mblock count on device 0: 5383, 9291, 13522 [18000]; 42058 [62500]
←[0m←[38;2;000;255;255mGPU[0] frame 11 step 4237 build_partition_for_particles: 0.202016 ms
←[0m←[1m----------------------------------------------------------------
←[0m←[1mresizing blocks 13522 -> 27000
←[0m←[38;2;000;255;255mGPU[0] frame 11 step 4238 grid_update_query: 0.262624 ms
←[0m←[1m----------------------------------------------------------------
←[0m←[1m0.42356575 --0.0001--> 0.45833334, defaultDt: 0.0001, maxVel: 2.8178828
←[0m←[38;2;000;255;255mGPU[0] frame 11 step 4238 halo_g2p2g: 0.235968 ms
←[0m←[1m----------------------------------------------------------------
←[0m←[1m----------------------------------------------------------------
←[0m←[38;2;000;255;255mGPU[0] step 4238 collect_send_halo_grid: 0.0011 ms
←[0m←[1m----------------------------------------------------------------
←[0m←[38;2;000;255;255mGPU[0] frame 11 step 4238 non_halo_g2p2g: 13.612352 ms
←[0m←[1m----------------------------------------------------------------
←[0m←[38;2;000;255;255mGPU[0] step 4238 receive_reduce_halo_grid: 0.0201 ms
←[0m←[1m----------------------------------------------------------------
←[0m←[38;2;000;255;255mGPU[0] frame 11 step 4238 update_partition: 2.341984 ms
←[0m←[38;2;000;255;255mGPU[0] frame 11 step 4238 build_partition_for_grid: 0.13248 ms
←[0mCUDA error at D:\Work\claymore\Projects\MGSP\mgsp_benchmark.cuh:33 code=2(cudaErrorMemoryAllocation) "cudaMalloc(&ret, bytes)"

Excutable issue with "cudaErrorInvalidDevice", any solution?

Try to run mgsp with single GPU, while report the following error

[Init -- Begin] Cuda
[InitInfo -- DevNum] Detected 1 CUDA Capable device(s)
[InitInfo -- DevNum] Prepare to use 1 device(s) in Multi-GPU test
[InitInfo -- Dev Property] GPU device 0 (0-th group on board)
global memory: 25390546944 bytes,
shared memory per block: 49152 bytes,
registers per SM: 65536,
Multi-Processor count: 84,
SM compute capabilities: 8.6.
[InitInfo -- stream] Create 32 streams for device 0
monotonic allocator alignment (Bytes): 512 size (MB): 2900.7
[InitInfo -- memory] device 0
free bytes/total bytes: 24332795904/25390546944,
pre-allocated size: 3041599488 bytes

    [Init] CudaContext 0
    [InitInfo -- Default Dev] Default context: 0

[Init -- End] == Finished 'Cuda' initialization

CUDA error at /home/chi/MyCode/GitHub/claymore/Library/MnSystem/Cuda/Cuda.h:73 code=101(cudaErrorInvalidDevice) "cudaSetDevice(dev_id)"

Any idea?

Can't figure out, how to get rid of this error

Severity Code Description Project File Line Suppression State
Error C2668 'mn::logic_and': ambiguous call to overloaded function mncuda C:\Users\janis\Downloads\claymore-master\claymore-master\Library\MnBase\Meta\Meta.h 37

incorrect implementation (?) of NACC algorithm in "constitutive_models.cuh"

In the function "compute_stress<float, MaterialE::NACC>" that updates the deformation gradient there is the variable "s_hat_trial_sqrnorm" that stands for the squared norm of the matrix s_hat. However, in the paper "CD-MPM: Continuum Damage Material Point Methods for Dynamic Fracture Animation: Supplemental Document", just the norm is used, not the squared norm.

GMPM crashes for me, even before trying to load objects.

Where are benchmarks?

Hi,

I've checked your projects.

You compared with Taichi in your paper, but the code in this project contains only initialization.

Do you have any sources written in Taichi?
If you have any sources, could you share with us?

Best regards,

Error: ""Assertion failed: IsObject(), file D:\claymore\build\_deps\rapidjson-src\include\rapidjson/document.h, line 1274" while running GMPM

When I am running the GMPM executable with input files "knot1.poly" or "dragon_particles.bin", I keep getting error as mentioned in the title.

Any help is appreciated. Thank you.

cmake error with "fopen_s"

Hi there,
I have recently encountered a cmake error that: "error: identifier 'fopen_s' is undefined" in the process of compiling gmpm. I didn't quite understand the cause of the error. How can I solve this problem? Thank you so much in advance

And my system info should be as: gcc (Ubuntu 9.4.0-1ubuntu1~20.04.1) 9.4.0, nvidia driver Version: 515.65.01, CUDA Version: 11.7

Recommend Projects

React

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

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

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

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
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.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

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

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.