Closed Hx83866 closed 3 years ago
The problem comes from the low sphericity - see below the (sub)tessellation soon before the code aborts. Is it really the morphology you want?
Dear Mr. Quey,
Thanks for your reply. I afraid yes, such a low sphericity was obtained by EBSD data via MTEX.
Does the software Neper have a recommended sphericity range?
Best Regards, Xiang Hu
I afraid yes, such a low sphericity was obtained by EBSD data via MTEX.
Could you show your EBSD map?
Does the software Neper have a recommended sphericity range?
Not really, but nasty things can happen for unusual values.
Hi Mr. Quey,
As you can see below, the domains distinguished by four different colors refer to packets that belong to four kinds of habit plane in martensitic transformation. The packet boundaries were emphasized by bold black lines.
What I want to generate through Neper is such multi-scale RVE.
Best Regards, Xiang Hu
Did you get the sphericity measurements from the regions inside the packets?
Anyways, I would not recommend to apply these measurements "blindly" to a 3D microstructure in Neper, at least for 2 reasons: (i) they come from a 2D section, and (ii) they are probably influenced by the non-convexities, which Neper is not really able to reproduce. I would recommend to start from standard values and modify them until you get a reasonable microstructure.
EDIT Please open a discussion if you'd like to discuss more about this.
Sure Thanks a lot!
Hello Everyone,
A bug was prompted, when a tessellation job was conducted on a HPC system via Singularity in my uni. (See below) Previously, I have successfully run a tessellation via Neper through this method, so it cannot be the problem of the HPC System.
Is there any command or method that can let the software ignore or skip the error and continue calculating?
Best Regards, Xiang Hu