some errors when running with GPU #63

Activity

1. rcarson3 commented on May 23, 2026

   

   rcarson3

   on May 23, 2026

   Member

   More actions

   @zgq-gg as it looks like you've just got a single phase material the region mapping files aren't required. The grain file also isn't needed for non-auto generated meshes that information should already be defined in the mesh as the PhysicalNames section if you're passing in GMSH . If it's a native MFEM mesh than it would already be defined by the element attributes. Next are you actually building things for the nvidia V100 GPUs? If not you need to make sure the GPU ID is the correct one for your GPUs. Updating that will require a full rebuild of all the packages though to the correct value.

   Outside of that, a few small things: the visualization files have a bug in the current release that output them every step and the post-processing steps are no longer every step. This is a bug being fixed in the #61 PR.

   Next, I noticed another bug recently that ExaCMech models and the orientation info is no longer automatically working out where it should go. So, I would update you [Material.Grain] sub-block to something like the below. I'll fix that in an upcoming release. It's possible this will fix your issue. If it doesn't I don't have the bandwidth to help run some of these issues down as GPU issues can be complicated or try to work out potential build issues. My recommendation if this doesn't fix things just throw a coding agent at it and see if it can't fix it locally if you don't have experience coding or debugging GPU programs.

       [Materials.Grain]
           orientation_file  = FILE_NAME
           ori_type          = "quat"
           ori_stride        = 4
           # This needs to be 9 for ExaCMech files for now
           ori_state_var_loc = 9
           num_grains        = ####
   

   Finally just for obvious reasons, I'm not going to download random untrusted files off the web.
2. rcarson3

   closed this as completedon Jun 11, 2026