Quadruple LINE problem

Question

Quadruple LINE problem

Closed this issue 5 years ago · 7 comments

This overall is a great code. However, in both the example codes that you provided as well as in my own implementation there appears to be a small number of quadruple LINES, which should not exist.

This is evidenced in the fact that there are areas where four triangles attach to a single edge.

I believe there is a bug in the code that allows this to happen. As this will affect the diffusivity through the smoothed model, it needs to be corrected.

Thank you,

Madeline

I have included an instance of the problem below

Answer 1 · 2018-08-06T20:38:56.000Z

Hi Madeline,
Thanks for bringing the issue of the example data sets to my attention. hierarchical-smooth does not change the connectivity of the nodes, only smooths them. Are you using Dream.3d? If there were quad lines, they were probably generated by Dream.3d's QuickSurfaceMesh feature (which I also used for my examples). This filter tends to misbehave for very short triple lines. I would suggest remeshing with a smaller mesh size, so you can resolve the triple line better.

This is not a hierarchical-smooth problem per se. I'll upload better example data sets as soon as I can.

Answer 2 · 2018-08-07T15:17:28.000Z

Thank you, I will look into DREAM.3D's side of things.

Answer 3 · 2018-08-07T18:25:42.000Z

As an update, it does appear to be a DREAM.3D problem, not a problem with the hierarchical-smooth code.

Thank you,

Madeline

Answer 4 · 2018-08-08T16:08:23.000Z

Do you know of another program type that is able to give a quick surface mesh similar to DREAM.3D's that would give the required input for your code?

Thanks,

Madeline

Answer 5 · 2018-08-08T16:15:59.000Z

@mward22 Unfortunately no, I wrote HSmooth with DREAM.3D specifically in mind. I haven't heard of a QuickSurfaceMesh equivalent anywhere else.

Did you try QuickSurfaceMeshing in DREAM.3D with smaller steps? Hopefully you'll resolve the ambiguous features. Of course, you'll end up bloating your data set...Maybe you can isolate the misbehaving region of the microstructure and mesh that part alone at a higher resolution.

Answer 6 · 2018-08-08T16:18:56.000Z

I’m not sure what you mean by smaller steps, I don’t see any place for me to input a manual number of steps for the QuickSufaceMesh filter.

…

On Aug 8, 2018, at 11:16 AM, Siddharth Maddali ***@***.***> wrote: @mward22 <https://github.com/mward22> Unfortunately no, I wrote HSmooth with DREAM.3D specifically in mind. I haven't heard of a QuickSurfaceMesh equivalent anywhere else. Did you try QuickSurfaceMeshing in DREAM.3D with smaller steps? Hopefully you'll resolve the ambiguous features. Of course, you'll end up bloating your data set...Maybe you can isolate the misbehaving region of the microstructure and mesh that part alone at a higher resolution. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#4 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/Ajt-JrA_aLiS62WUKVmKEsmwdFNCV2BVks5uOw6_gaJpZM4Vw6zd>.

Answer 7 · 2018-08-08T16:40:10.000Z

It's been a while since I've actually used DREAM.3D on a daily basis, but I guess I meant doing something like this:

http://dream3d.bluequartz.net/binaries/Help/DREAM3D/Filters/SamplingFilters/ChangeResolution/index.html

This filter changes the voxel size before applying the QuickSurfaceMesh filter. Now how useful you think the result is going to be, that's another issue...