Dear Arash,
Each time the Synthetic generation pipeline runs, essentially all the filters past the “Initialize Synthetic Volume” DREAM3D will regenerate all of the grains based on values sampled from the distributions. This will give you a different microstructure each time through the pipeline. My suggestion would be the following.
Create a microstructure with a very fine spacing/resolution value. For instance, in the “Initialize Synthetic Volume” filter you might start with dimensions of 256x256x256 and a resolution of 0.1 x 0.1 x 0.1.
Near the end of the pipeline you can then add the “Change Resolution” filter. Double the resolution from the original values (0.2 x 0.2 x 0.2 in this example), check the renumber features, and check the “Save as New Data Container”. Fill in the rest of the input values to match yours. This will resample the original microstructure to a “lower resolution”. Note that if you have small grains, they may get “swallowed up” or “skipped over” based on your new resolution values. If you want additional resolutions, just insert the “Change Resolution” filter as many times as you want new resolutions. Keep in mind that you should ALWAYS pick the original resolution microstructure as most of the time it is beneficial to start with the highest detail model.
I am including an example pipeline to help get you started.
--
Mike Jackson
--
You received this message because you are subscribed to the Google Groups "dream3d-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dream3d-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dream3d-users/b8a4b357-b3f2-45bd-a7f0-a8b12029ab9cn%40googlegroups.com.
Add the “Write DREAM.3D File” to the end of the pipeline. This will produce a pair of files. Use the one with the .xdmf extension to load into ParaView. https://www.youtube.com/watch?v=j7WtJOcK1VI go to 7:10 time stamp in the video to see how to load the data in ParaView.
To view this discussion on the web visit https://groups.google.com/d/msgid/dream3d-users/c54c318b-b312-4c3b-8771-9ea56226bafan%40googlegroups.com.
The filter is correctly applying the change of resolution. The initial geometry is 256^3 with a resolution of 0.1. This means a physical dimension of roughly 0~25. When you applied the Change Resolution to 0.2 the physical dimension stayed the same at 0~25 BUT in order to achieve that the number of voxels is reduced half so that the grid is 128^3 voxels. See attached image which should help clarify what is happening.
To view this discussion on the web visit https://groups.google.com/d/msgid/dream3d-users/b304e599-5429-4b83-8a85-060f7b24cecfn%40googlegroups.com.
Which version of DREAM.3D are you using that corrected the issue? What version of DREAM.3D were you using that was not working? Would be good to document that here in the help forums
To view this discussion on the web visit https://groups.google.com/d/msgid/dream3d-users/02950189-af97-4563-b7bf-3c888123f97en%40googlegroups.com.
Versions with “6.6.x” are nightly builds and unofficial but if it works for you then go with it.
--
Mike Jackson
Hi,
To view this discussion on the web visit https://groups.google.com/d/msgid/dream3d-users/d6018b0b-b8d3-430b-be20-b16bc7fb2f8dn%40googlegroups.com.
Sounds like at the 256x256x256 you are just inside what your computer can handle and then adding in another geometry pushes it over the edge? Maybe? Could you send your pipeline?
--
Michael Jackson | Owner, President
BlueQuartz Software
To view this discussion on the web visit https://groups.google.com/d/msgid/dream3d-users/58feaeb0-494a-4717-8219-5878e2d54a3dn%40googlegroups.com.