Dimension doesn't match between final time step microstructure and intralayer output microstructure
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 96
- Forks
- 29
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 1
Description
Hi all,
I am using ExaCA to do the single-track CA simulation. I also want to extract the microstructure at mid-time so that I can get all the microstructure evolution information. But I found the final time microstructure dimension, with the name of singletrack.vtk, did not match the dimension from the mid-time output microstructure. For the microstructure output from intralayer, it is shorter than the final time microstructure, like the picture shown below. Left one is the output from final time, right is the output from mid-time. Do you have any suggestions so that I can make the mid-time output show all the information?
The second thing is that, I am trying to plot the IPF figure for the mid-time output. ExaCA provides us the analysis execution so that we can obtain the IPF directly, but I found it only works for the final step output. Do you have any suggestions so that we can also obtain the IPF file for the mid-time or like Euler angle information for the mid-time.
For the final one, I saw, we can enter the keywords in the intralayer or interlayer fields part, but I did not see any instructions for which keywords we can use, for the provided link does not work. Could you help check this? Thanks
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the single-track simulation and comparing the final-time singletrack.vtk output with the intralayer mid-time output. Then inspect the analysis execution used for IPF generation and the intralayer/interlayer keyword documentation or linked page. Done means the mid-time output preserves the expected information, mid-time IPF or Euler-angle data is supported, and the keyword instructions are available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- data, documentation
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100