the triple points of a boundary: the vertices where three grains meet, each with its three grains, their phases, the three boundary segments and the angles between them
Syntax
tP = grains.triplePoints
tP('Iron bcc', 'Iron bcc', 'Iron bcc')
Input
V |
array of triple-point coordinates in the map plane |
grainId |
three grain ids at each junction |
phaseId |
three phase-list indices at each junction |
boundaryId |
indices of the three incident boundary segments |
angles |
three enclosed angles at each junction, in radians |
CSList |
phase frames |
plane |
coordinate system of the map plane |
frame |
specimen reference frame |
vertexId |
optional ids into the full boundary vertex table |
Signature
triplePointList(V, grainId, phaseId, boundaryId, angles, CSList, plane, frame, vertexId=None)
MATLAB’s triplePointList.triplePointList
source
Citing this page.
This page is part of the documentation of
MTEX, a free and open
source MATLAB toolbox for analyzing and modeling crystallographic textures.
It was written by The MTEX Developers and is published at
https://mtex-toolbox.github.io/triplePointList.triplePointList_py.html.
If you use MTEX, or reuse text or figures from this page, in your research,
please cite
F. Bachmann, R. Hielscher, H. Schaeben: Texture Analysis with MTEX - Free and Open Source Software Toolbox, Solid State Phenomena 160 (2010), 63-68. 10.4028/www.scientific.net/SSP.160.63
BibTeX
@article{bachmann2010mtex,
author = {F. Bachmann and R. Hielscher and H. Schaeben},
title = {Texture Analysis with MTEX - Free and Open Source Software Toolbox},
journal = {Solid State Phenomena},
volume = {160},
pages = {63-68},
year = {2010},
doi = {10.4028/www.scientific.net/SSP.160.63},
url = {https://doi.org/10.4028/www.scientific.net/SSP.160.63}
}
Other papers describing specific MTEX methods are listed under Publications — please cite the one that best fits your application. The MTEX source code is licensed under the GNU General Public License v2.0; the text and figures of this documentation are licensed under CC BY 4.0, which permits reuse — including by automated systems — provided The MTEX Developers and this page are credited.