Reference Talk:Potential Pattern - Revision history

Jholsenback: completed mark up

2016-12-20T11:20:00Z

completed mark up

Clipka at 18:22, 19 December 2016

2016-12-19T18:22:13Z

Clipka at 18:13, 19 December 2016

2016-12-19T18:13:19Z

Clipka: edited the wrong pattern, sorry

2016-12-19T18:06:58Z

edited the wrong pattern, sorry

Clipka at 18:05, 19 December 2016

2016-12-19T18:05:56Z

Clipka at 18:03, 19 December 2016

2016-12-19T18:03:29Z

Clipka: Created page with " copied from the povray.beta-test newsgroup: ---- This version adds a new pigment pattern: pigment { user_defined { function { RED_FUNCTION }, funct..."

2016-12-19T18:02:55Z

Created page with " copied from the povray.beta-test newsgroup: ---- This version adds a new pigment pattern: pigment { user_defined { function { RED_FUNCTION }, funct..."

New page

copied from the povray.beta-test newsgroup:
----
This version adds a new pigment pattern:

pigment {
user_defined {
function { RED_FUNCTION },
function { GREEN_FUNCTION },
function { BLUE_FUNCTION },
function { FILTER_FUNCTION },
function { TRANSMIT_FUNCTION }
}
}

Each function is optional, in which case the corresponding component is
set to 0. For example, the following sets the colour to rgbft <x,y,0,0,z>:

pigment {
user_defined {
function { x },
function { y },
,,
function { z }
}
}

Aside from that, the version also includes the data container update as
well as the transmission-based highlights/reflections knockout update.
----

@@ Line 1: / Line 1: @@
-Copied from a post in povray.binaries.images:
+<p>{{New}} in version 3.7.1 a <code>potential</code> pattern has been added to define a pattern based on the <em>potential</em> field of a <code>blob</code> or <code>isosurface</code> object.</p>
------
+<pre>
-Syntax for the new pattern is as follows (using pigment as an example):
+pigment {
-    pigment {
+<p>With <code>threshold on</code> the pattern will take the <code>blob</code> or <code>isosurface</code> object's <em>potential minus the threshold</em>; otherwise it will take the <em>raw potential</em> which is the default behavior.</p>
-With `threshold` set to `on`, the pattern will take the blob or
+<p>The <em>isosurface's</em> container has no effect on the <code>potential</code> pattern.</p>
-The pattern value is _not_ bound to the [0..1] range (unless you
+<p>The pattern value is <em>not</em> bound to the [0..1] range, unless you explicitly specify a <code>wave_type</code>.</p>
-Applying the "inverse" keyword to the object will cause the pattern to
+<p>Applying the <code>inverse</code> keyword to the object will cause the pattern to be reversed as well; so, when using <code>threshold on</code> for blobs, positive pattern values always indicate inside, while negative values indicate outside.</p>
-Note that by default this is just the other way round for isosurfaces
+<pre>
-(which had annoyed me multiple times already); for easier use, the new
+isosurface {
-pattern is therefore accompanied by an extension to the isosurface syntax:
+  ...
-    isosurface {
+<p>Setting <code>polarity</code> to a positive value causes above-threshold values to be interpreted as inside, and below-threshold values as outside, rather than the other way round</p>
-Setting `polarity` to a positive value causes above-threshold values to
+<p>See also: [[Reference:Blob|Blob]] and [[Reference:Isosurface|Isosurface]]</p>

← Older revision		Revision as of 18:22, 19 December 2016
Line 37:		Line 37:
	than the other way round.		than the other way round.
	----		----
		+
		+	Another thing that might be worth mentioning is that an isosurface's container has no effect on the potential pattern.

← Older revision	Revision as of 18:13, 19 December 2016
Line 1:	Line 1:
	+	Copied from a post in povray.binaries.images:

	+	-----
	+	Syntax for the new pattern is as follows (using pigment as an example):
	+
	+	pigment {
	+	potential { BLOB \| ISOSURFACE }
	+	[ threshold BOOL ]
	+	[ PIGMENT_MODIFIERS... ]
	+	}
	+
	+	With `threshold` set to `on`, the pattern will take the blob or
	+	isosurface object's potential minus the threshold; otherwise it will
	+	take the raw potential (the default).
	+
	+	The pattern value is _not_ bound to the [0..1] range (unless you
	+	explicitly specify a `wave_type`).
	+
	+	Applying the "inverse" keyword to the object will cause the pattern to
	+	be reversed as well; thus, when using `threshold on`, for blobs positive
	+	pattern values always indicate inside, while negative values indicate
	+	outside.
	+
	+
	+	Note that by default this is just the other way round for isosurfaces
	+	(which had annoyed me multiple times already); for easier use, the new
	+	pattern is therefore accompanied by an extension to the isosurface syntax:
	+
	+	isosurface {
	+	...
	+	polarity FLOAT
	+	...
	+	}
	+
	+	Setting `polarity` to a positive value causes above-threshold values to
	+	be interpreted as inside, and below-threshold values as outside, rather
	+	than the other way round.
	+	----

← Older revision		Revision as of 18:06, 19 December 2016
Line 1:		Line 1:

−	~~copied from the povray.beta-test newsgroup:~~
−	~~----~~
−	~~This version adds a new pigment pattern:~~
−
−	~~pigment {~~
−	~~user_defined {~~
−	~~function { RED_FUNCTION },~~
−	~~function { GREEN_FUNCTION },~~
−	~~function { BLUE_FUNCTION },~~
−	~~function { FILTER_FUNCTION },~~
−	~~function { TRANSMIT_FUNCTION }~~
−	}
−	}
−
−	~~Each function is optional, in which case the corresponding component is~~
−	~~set to 0. For example, the following sets the colour to rgbft <x,y,0,0,z>:~~
−
−	~~pigment {~~
−	~~user_defined {~~
−	~~function { x },~~
−	~~function { y },~~
−	,,
−	~~function { z }~~
−	}
−	}
−	~~----~~
−
−	~~The pattern is similar to `image_map` in that it directly specifies colours, rather than using a `colour_map` or `pigment_map`.~~

← Older revision		Revision as of 18:05, 19 December 2016
Line 26:		Line 26:
	}		}
	----		----
		+
		+	The pattern is similar to `image_map` in that it directly specifies colours, rather than using a `colour_map` or `pigment_map`.

@@ Line 25: / Line 25: @@
+       }
+     }
 ----