Neighborhood analysis - Revision history

Raffaele Coray at 11:51, 29 April 2024

2024-04-29T11:51:55Z

2024-04-08T09:12:17Z

Example

2024-04-08T09:09:42Z

2024-03-27T12:58:38Z

Visualization

2024-03-27T12:47:39Z

Function call

2024-03-27T12:46:15Z

Function call

2024-03-27T12:43:36Z

Concept

2024-03-27T12:43:13Z

Concept

2024-03-27T12:40:51Z

Concept

2024-03-27T12:39:58Z

Concept

@@ Line 52: / Line 52: @@
 <pre>
 nbins=[50 50];
-[N,C]=hist3([analysisOfmyTable.coupleTable(:,24), analysisOfmyTable.coupleTable(:,25)],nbins);
+[N,C]=hist3([analysisOfmyTable.coupleTable(:,25), analysisOfmyTable.coupleTable(:,24)],nbins);
 contourf(C{1},C{2},N);
 xlabel('Relative pairwise X distance [px]');

← Older revision		Revision as of 09:12, 8 April 2024
Line 62:		Line 62:
	= Example=		= Example=

−	An in-depth walkthough on the use of the neighborhood ~~anaylsis~~ is [[Walkthrough on hexagonal lattice coherence through neighborhood analysis \| ~~available~~]].	+	An in-depth walkthough on the use of the neighborhood analysis is available at [[Walkthrough on hexagonal lattice coherence through neighborhood analysis \| this page]].

← Older revision		Revision as of 09:09, 8 April 2024
Line 59:		Line 59:
	axis equal;		axis equal;
	</pre>		</pre>
		+
		+	= Example=
		+
		+	An in-depth walkthough on the use of the neighborhood anaylsis is [[Walkthrough on hexagonal lattice coherence through neighborhood analysis \| available]].

@@ Line 41: / Line 41: @@
 [[File:dtview_GUI_1.png|centre|thumb|400px| The dtview GUI can be used to inspect any table. When inspecting neighborhood analysis tables the fields x, y and z indicate the relative distances of all pairs.]]
-<code>dtview</code> allow for the creations of lassos in 2D scatterplots. This tool can be access by right-clicking the 2D scatter figure. A lasso can then by manually drawn.
+<code>dtview</code> allows for the creations of lassos in 2D scatterplots. This tool can be access by right-clicking the 2D scatter figure. A lasso can then by manually drawn.
 [[File:dtview_GUI_3.png|centre|thumb|400px| The lassos can be used to extract the indices of the pairs that accumulate in a certain area. This information can than me paired with the <code>.couples</code> information to recover the information of each particle involved from the original table.]]

← Older revision		Revision as of 12:47, 27 March 2024
Line 33:		Line 33:


−	The output <code>analysisOfmyTable</code> is a structure. It contains three main fields: <code>.originalTable</code>, <code>.coupleTable</code> and <code>.couples</code>. <code>.originalTable</code> is merely a copy of the input table. <code>.coupleTable</code> is the table that records the geometric relationships between pairs of particles and in particular the distance vector is recorded in columns 24, 25 and 26 (x,y,z following the Dynamo table conventions). <code>.couples</code> records the indexes of the particles ~~that make a pair~~ in the original table. As such, <code>.coupleTable</code> will have the same number of rows as <code>.couples.tbl</code>.	+	The output <code>analysisOfmyTable</code> is a structure. It contains three main fields: <code>.originalTable</code>, <code>.coupleTable</code> and <code>.couples</code>. <code>.originalTable</code> is merely a copy of the input table. <code>.coupleTable</code> is the table that records the geometric relationships between pairs of particles and in particular the distance vector is recorded in columns 24, 25 and 26 (x,y,z following the Dynamo table conventions). <code>.couples</code> records for each pair the indexes of the corresponding particles in the original table. As such, <code>.coupleTable</code> will have the same number of rows as <code>.couples.tbl</code>.

	= Visualization=		= Visualization=

← Older revision		Revision as of 12:46, 27 March 2024
Line 33:		Line 33:


−	The output <code>analysisOfmyTable</code> is a structure. It contains three main fields: <code>.originalTable</code>, <code>.coupleTable</code> and <code>.couples</code>. <code>.originalTable</code> is merely a copy of the input table. <code>.coupleTable</code> is the table that records the geometric relationships between pairs of particles, in particular the distance vector is ~~recordes~~ in columns 24, 25 and 26 (x,y,z following the Dynamo table conventions). <code>.couples</code> records the indexes of the particles that make a pair in the original table. As such, <code>.coupleTable</code> will have the same number of rows as <code>.couples.tbl</code>.	+	The output <code>analysisOfmyTable</code> is a structure. It contains three main fields: <code>.originalTable</code>, <code>.coupleTable</code> and <code>.couples</code>. <code>.originalTable</code> is merely a copy of the input table. <code>.coupleTable</code> is the table that records the geometric relationships between pairs of particles and in particular the distance vector is recorded in columns 24, 25 and 26 (x,y,z following the Dynamo table conventions). <code>.couples</code> records the indexes of the particles that make a pair in the original table. As such, <code>.coupleTable</code> will have the same number of rows as <code>.couples.tbl</code>.

	= Visualization=		= Visualization=

@@ Line 17: / Line 17: @@
 [[File:neigh_fig5.png|centre|thumb|400px| If there is a repeating geometric relationship between close particles, then this would be reflected by the presence of concentrations points in the neighborhood plot.]]
-It is important to note that the pair (i,j) is not necessarily a sign flip of the the pair (j,i) even through they express the same distance vector (with opposite sign) in the tomogram. This is because the reference systems of i and j have different independent orientations to each other!
+It is important to note that the pair (i,j) is not necessarily a sign flip of the the pair (j,i), even through they express the same distance vector (with opposite sign) in the tomogram. This is because the reference systems of i and j have different independent orientations to each other!
 = Function call=