Warnings when using calcGrains

[David Mainprice]

Please be as detailed as possible, explain what you want to do, what kind of data you are using. Attaching simplified code and data is always useful. Click the the button { } to inline code and finally remove these lines before posting :)

Warning: QH7074 qhull warning: more than 16777215 ridges.  ID field overflows and two ridges

may have the same identifier.  Otherwise output ok.

 

Warning: QH7074 qhull warning: more than 16777215 ridges.  ID field overflows and two ridges

may have the same identifier.  Otherwise output ok.

 

> In qhullmx

  In voronoin (line 107)

  In spatialDecomposition (line 28)

  In EBSD/calcGrains (line 26) 

Warning: QH7074 qhull warning: more than 16777215 ridges.  ID field overflows and two ridges

may have the same identifier.  Otherwise output ok.

 

> In qhullmx

  In voronoin (line 107)

  In spatialDecomposition (line 28)

  In EBSD/calcGrains (line 26) 

Is there anything we can do to avoid this ?

all the best David

[Luiz F. G. Morales]

Hi Dave

I had this when working with maps cleaned on TSL. The way it works for me is something like:

%% Selecting the region of interest

region = [0 0 35624 11818]

close all

figure

oM2 = ipdfHSVOrientationMapping(ebsd('olivine'))

color = oM2.orientation2color(ebsd('olivine').orientations);

plot(ebsd('olivine'),color,'figSize','medium')

rectangle('position',region,'edgecolor','r','linewidth',2)

saveFigure('SAM-1-Y_restricted_symmetry_with_retangle_olivine.tif')

condition = inpolygon(ebsd,region);

ebsd = ebsd(condition);

 

%% Remove repeated data or NaN from clean EBSD data from TSL

[x,y]=ginput(2);

minx=min(x);

miny=min(y);

xspan=max(x)-min(x);

yspan=max(y)-min(y);

region = [minx,miny,xspan,yspan];

condition = inpolygon(ebsd,region);

ebsdCrop= ebsd(condition);

ebsd=ebsdCrop

But it should be a more “elegant” way to write this according to Dani Schmid :)

--
If you want to reduce the number of emails you get through this forum login to https://groups.google.com/forum/?fromgroups=#!forum/mtexmail, click "My membership" and select "Don't send me email updates". You can still get emails on selected topics by staring them.
---
You received this message because you are subscribed to the Google Groups "MTEX" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mtexmail+u...@googlegroups.com.
Visit this group at https://groups.google.com/group/mtexmail.
For more options, visit https://groups.google.com/d/optout.

ETH Zürich
Luiz F. G. Morales
Scientific Center for Optical and Electron Microscopy (ScopeM)
HPT D 9
Auguste-Piccard-Hof 1
8093 Zurich, Switzerland
Phone +41 44 633 37 46
E-mail: luiz.m...@scopem.ethz.ch
URL: www.scopem.ethz.ch
URL: https://sites.google.com/site/luizfgmorales/
Skype: lfgmorales

[David Mainprice]

Dear Luiz,

Thanks for the advice.

all the best David

[Rachel Bernard]

Hi there,

I've been getting this exact message today when trying to map some really large/high resolution EBSD maps. I haven't cleaned my maps since exporting the CRC/CTF data from Aztec (and I'm not sure what TSL is). Do you have any ideas as to how I can fix this? Here's the exact error:

Warning: QH7074 qhull warning: more than 16777215 ridges.  ID field overflows and two ridges

may have the same identifier.  Otherwise output ok.

QH7074 qhull warning: more than 16777215 ridges.  ID field overflows and two ridges

may have the same identifier.  Otherwise output ok.

 

> In qhullmx

  In voronoin (line 107)

  In spatialDecomposition (line 28)

  In EBSD/calcGrains (line 26)

  In mtex5_mapsOnly_Sept2018 (line 59) 

[Rüdiger Kilian]

Hi,
this is a Matlab issue. Matlb uses an old version of qhull which only supports a 24-bit number in some ID field. There's not much one can do about it unless Matlab decides to use a more recent version of qhull.
You might be lucky and your grains might still be reasonable, or, to work around this issue, chop your ebsd into smaller parts.
Cheers,
Rüdiger

[Rachel Bernard]

Thank you for your response, Rüdiger. I found I was able to process the large (200+ MB) EBSD maps as long as I don't do anything involving calcGrains. That's inconvenient, so in the future I will probably split the map up into smaller pieces. Thanks again! Good to know it wasn't a problem with my laptop or software.