Is anyone who provide me a valuable way to allocate quaternion values i.e. 'O' for each voxels in the initial geom - '~vti' file.

[namhgoo142]

I have tried to update the voxel orientation value after deformation by use of updating material.yaml file. In this case only averaged quaternion values is available,because the material.yaml has only input frame based on grain, grain ID. The problem has been caused in regrid process. After I did regriding and make updated geom ~.vti file and material.yamal. file, the orientation is just set to initial values. It is really trouble for me !!!

[MarDiehl]

it's totally fine to have one material entry per voxel/cell in the material configuration. That is called "cell-wise" data in damask.GeomGrid.load_DREAM3D/damask.ConfigMaterial.load_DREAM3D

But regridding implies a restart and in that case the values from the restart file overwrite the initial data from YAML/VTI.

If you need more help, pls. provide all the information required to reproduce what you're doing (https://damask-multiphysics.org/support/helpdesk.html)

[namhgoo142]

I appreciate Martin. (Vielen Dank!)
However, I have not yet solved my trouble issues. Here Is summary of my job.

1. Purpose : Hevery plastic deformation over 70% ( tensile, rolling whatever, it depends on the deformation tensor).
2. Backgroud:
   2.1. Just increase the amount of deformation, it fails with the odd grid shape, c.a. over 30% deformation is not possible.
   2.2. As a solution for the odd grid shape problem, I tried to regrid method after the Martin Diehl's github ( https://github.com/MarDiehl/regrid.git)
   2.3. The python script file is works well. But the python script (mesh_replacement.py) presents only two-step process. I need more deformation steps to obtain heavy plastic deformation.
   2.4. The process that I understood is following; first run has ~.hdf5, ~restart.hdf5, ~.sta files. By regriding function we can have -2.vti file and modified and copied -2_.hdf5 file, -2_restart.hdf5, -2_.sta file. By these -2* related files, I tried to run the second run, i,e, DAMASK_grid -g ~-2.vti, -l tensile.yaml , -m material.yaml -r 140.
   2.5 Problems occurs in the second run, using -r options.
   I guess that the load file boundary conditions are matter, Can you provide me the detailed explanation of how to use f_restart and -r option properly ?

Error messages are :
... saving results ........................................................
HDF5-DIAG: Error detected in HDF5 (1.10.10) MPI-process 0:
#000: ../../../src/H5G.c line 304 in H5Gcreate2(): unable to create group
major: Symbol table
minor: Unable to initialize object
#1: ../../../src/H5Gint.c line 146 in H5G__create_named(): unable to create and link to group
major: Symbol table
minor: Unable to initialize object
#2: ../../../src/H5L.c line 1542 in H5L_link_object(): unable to create new link to object
major: Links
minor: Unable to initialize object
#3: ../../../src/H5L.c line 1785 in H5L__create_real(): can't insert link
major: Links
minor: Unable to insert object
#4: ../../../src/H5Gtraverse.c line 830 in H5G_traverse(): internal path traversal failed
major: Symbol table
minor: Object not found
#5: ../../../src/H5Gtraverse.c line 607 in H5G__traverse_real(): traversal operator failed
major: Symbol table
minor: Callback failed
#6: ../../../src/H5L.c line 1577 in H5L__link_cb(): name already exists
major: Links
minor: Object already exists
Note: The following floating-point exceptions are signalling: IEEE_UNDERFLOW_FLAG IEEE_INEXACT_FLAG
ERROR STOP HDF5 error