Time-Resolved Fluorescence Wiki

privacy_policy

Anonymous (anonymous@undisclosed.example.com) — 2019-12-03T15:49:17+00:00

2019/12/03 16:45		current
Line 198:		Line 198:

	Grundsätzlich besteht für die betroffene Person die Möglichkeit, einer Erfassung der durch den Matomo erzeugten, auf eine Nutzung dieser Internetseite bezogenen Daten zu widersprechen und eine solche zu verhindern. Hierzu muss die betroffene Person in Ihrem Browser "Do Not Track" einstellen.		Grundsätzlich besteht für die betroffene Person die Möglichkeit, einer Erfassung der durch den Matomo erzeugten, auf eine Nutzung dieser Internetseite bezogenen Daten zu widersprechen und eine solche zu verhindern. Hierzu muss die betroffene Person in Ihrem Browser "Do Not Track" einstellen.
-
-	Ferner besteht für die betroffene Person die Möglichkeit der anonymisierten Datenerhebung durch das Programm Matomo jederzeit mit Wirkung für die Zukunft zu widersprechen, indem sie auf den untenstehenden Link klicken. In diesem Fall wird ein sog. Opt-Out-Cookie im Browser der betroffenen Person abgelegt, was zur Folge hat, dass Matomo keinerlei Sitzungsdaten mehr erhebt. Wenn betroffene Person ihre Cookies löschen, so hat dies jedoch zur Folge, dass auch das Opt-Out-Cookie gelöscht wird und daher von den betroffene Person erneut aktiviert werden muss.

	Die Logs mit den Daten der betroffene Person werden nach spätestens 6 Monaten gelöscht.		Die Logs mit den Daten der betroffene Person werden nach spätestens 6 Monaten gelöscht.
-	{{url>https://www.picoquant.com/piwik/index.php?module=CoreAdminHome&action=optOut&language=en&backgroundColor=&fontColor=&fontSize=&fontFamily=}}

	Weitere Informationen und die geltenden Datenschutzbestimmungen von Matomo können unter [[https://matomo.org/privacy/]] abgerufen werden.		Weitere Informationen und die geltenden Datenschutzbestimmungen von Matomo können unter [[https://matomo.org/privacy/]] abgerufen werden.

syntax

Anonymous (anonymous@undisclosed.example.com) — 2026-04-23T08:17:27+00:00

2026/04/23 20:33	current
Line 1:	Line 1:
	+	====== Formatting Syntax ======
	+
	+	[[doku>DokuWiki]] supports some simple markup language, which tries to make the datafiles to be as readable as possible. This page contains all possible syntax you may use when editing the pages. Simply have a look at the source of this page by pressing "Edit this page". If you want to try something, just use the [[playground:playground\|playground]] page. The simpler markup is easily accessible via [[doku>toolbar\|quickbuttons]], too.
	+
	+	===== Basic Text Formatting =====
	+
	+	DokuWiki supports bold, //italic//, __underlined__ and ''monospaced'' texts. Of course you can __//''combine''//__ all these.
	+
	+	DokuWiki supports bold, //italic//, __underlined__ and ''monospaced'' texts.
	+	Of course you can __//''combine''//__ all these.
	+
	+	You can use <sub>subscript</sub> and <sup>superscript</sup>, too.
	+
	+	You can use <sub>subscript</sub> and <sup>superscript</sup>, too.
	+
	+	You can mark something as <del>deleted</del> as well.
	+
	+	You can mark something as <del>deleted</del> as well.
	+
	+	Paragraphs are created from blank lines. If you want to force a newline without a paragraph, you can use two backslashes followed by a whitespace or the end of line.
	+
	+	This is some text with some linebreaks\\ Note that the
	+	two backslashes are only recognized at the end of a line\\
	+	or followed by\\ a whitespace \\this happens without it.
	+
	+	This is some text with some linebreaks\\ Note that the
	+	two backslashes are only recognized at the end of a line\\
	+	or followed by\\ a whitespace \\this happens without it.
	+
	+	You should use forced newlines only if really needed.
	+
	+	===== Links =====
	+
	+	DokuWiki supports multiple ways of creating links.
	+
	+	==== External ====
	+
	+	External links are recognized automagically: http://www.google.com or simply www.google.com - You can set the link text as well: [[http://www.google.com\|This Link points to google]]. Email addresses like this one: <andi@splitbrain.org> are recognized, too.
	+
	+	DokuWiki supports multiple ways of creating links. External links are recognized
	+	automagically: http://www.google.com or simply www.google.com - You can set
	+	link text as well: [[http://www.google.com\|This Link points to google]]. Email
	+	addresses like this one: <andi@splitbrain.org> are recognized, too.
	+
	+	==== Internal ====
	+
	+	Internal links are created by using square brackets. You can either just give a [[pagename]] or use an additional [[pagename\|link text]].
	+
	+	Internal links are created by using square brackets. You can either just give
	+	a [[pagename]] or use an additional [[pagename\|link text]].
	+
	+	[[doku>pagename\|Wiki pagenames]] are converted to lowercase automatically, special characters are not allowed.
	+
	+	You can use [[some:namespaces]] by using a colon in the pagename.
	+
	+	You can use [[some:namespaces]] by using a colon in the pagename.
	+
	+	For details about namespaces see [[doku>namespaces]].
	+
	+	Linking to a specific section is possible, too. Just add the section name behind a hash character as known from HTML. This links to [[syntax#internal\|this Section]].
	+
	+	This links to [[syntax#internal\|this Section]].
	+
	+	Notes:
	+
	+	* Links to [[syntax\|existing pages]] are shown in a different style from [[nonexisting]] ones.
	+	* DokuWiki does not use [[wp>CamelCase]] to automatically create links by default, but this behavior can be enabled in the [[doku>config]] file. Hint: If DokuWiki is a link, then it's enabled.
	+	* When a section's heading is changed, its bookmark changes, too. So don't rely on section linking too much.
	+
	+	==== Interwiki ====
	+
	+	DokuWiki supports [[doku>Interwiki]] links. These are quick links to other Wikis. For example this is a link to Wikipedia's page about Wikis: [[wp>Wiki]].
	+
	+	DokuWiki supports [[doku>Interwiki]] links. These are quick links to other Wikis.
	+	For example this is a link to Wikipedia's page about Wikis: [[wp>Wiki]].
	+
	+	==== Windows Shares ====
	+
	+	Windows shares like [[\\server\share\|this]] are recognized, too. Please note that these only make sense in a homogeneous user group like a corporate [[wp>Intranet]].
	+
	+	Windows Shares like [[\\server\share\|this]] are recognized, too.
	+
	+	Notes:
	+
	+	* For security reasons direct browsing of windows shares only works in Microsoft Internet Explorer per default (and only in the "local zone").
	+	* For Mozilla and Firefox it can be enabled through different workaround mentioned in the [[http://kb.mozillazine.org/Links_to_local_pages_do_not_work\|Mozilla Knowledge Base]]. However, there will still be a JavaScript warning about trying to open a Windows Share. To remove this warning (for all users), put the following line in ''conf/lang/en/lang.php'' (more details at [[doku>localization#changing_some_localized_texts_and_strings_in_your_installation\|localization]]): <code - conf/lang/en/lang.php>
	+	<?php
	+	/**
	+	* Customization of the english language file
	+	* Copy only the strings that needs to be modified
	+	*/
	+	$lang['js']['nosmblinks'] = '';
	+	</code>
	+
	+	==== Image Links ====
	+
	+	You can also use an image to link to another internal or external page by combining the syntax for links and [[#images_and_other_files\|images]] (see below) like this:
	+
	+	[[http://php.net\|{{wiki:dokuwiki-128.png}}]]
	+
	+	[[http://php.net\|{{wiki:dokuwiki-128.png}}]]
	+
	+	Please note: The image formatting is the only formatting syntax accepted in link names.
	+
	+	The whole [[#images_and_other_files\|image]] and [[#links\|link]] syntax is supported (including image resizing, internal and external images and URLs and interwiki links).
	+
	+	===== Footnotes =====
	+
	+	You can add footnotes ((This is a footnote)) by using double parentheses.
	+
	+	You can add footnotes ((This is a footnote)) by using double parentheses.
	+
	+	===== Sectioning =====
	+
	+	You can use up to five different levels of headlines to structure your content. If you have more than three headlines, a table of contents is generated automatically -- this can be disabled by including the string ''<nowiki>~~NOTOC~~</nowiki>'' in the document.
	+
	+	==== Headline Level 3 ====
	+	=== Headline Level 4 ===
	+	== Headline Level 5 ==
	+
	+	==== Headline Level 3 ====
	+	=== Headline Level 4 ===
	+	== Headline Level 5 ==
	+
	+	By using four or more dashes, you can make a horizontal line:
	+
	+	----
	+
	+	===== Media Files =====
	+
	+	You can include external and internal [[doku>images\|images, videos and audio files]] with curly brackets. Optionally you can specify the size of them.
	+
	+	Real size: {{wiki:dokuwiki-128.png}}
	+
	+	Resize to given width: {{wiki:dokuwiki-128.png?50}}
	+
	+	Resize to given width and height((when the aspect ratio of the given width and height doesn't match that of the image, it will be cropped to the new ratio before resizing)): {{wiki:dokuwiki-128.png?200x50}}
	+
	+	Resized external image: {{https://www.php.net/images/php.gif?200x50}}
	+
	+	Real size: {{wiki:dokuwiki-128.png}}
	+	Resize to given width: {{wiki:dokuwiki-128.png?50}}
	+	Resize to given width and height: {{wiki:dokuwiki-128.png?200x50}}
	+	Resized external image: {{https://www.php.net/images/php.gif?200x50}}
	+
	+
	+	By using left or right whitespaces you can choose the alignment.
	+
	+	{{ wiki:dokuwiki-128.png}}
	+
	+	{{wiki:dokuwiki-128.png }}
	+
	+	{{ wiki:dokuwiki-128.png }}
	+
	+	{{ wiki:dokuwiki-128.png}}
	+	{{wiki:dokuwiki-128.png }}
	+	{{ wiki:dokuwiki-128.png }}
	+
	+	Of course, you can add a title (displayed as a tooltip by most browsers), too.
	+
	+	{{ wiki:dokuwiki-128.png \|This is the caption}}
	+
	+	{{ wiki:dokuwiki-128.png \|This is the caption}}
	+
	+	For linking an image to another page see [[#Image Links]] above.
	+
	+	==== Supported Media Formats ====
	+
	+	DokuWiki can embed the following media formats directly.
	+
	+	\| Image \| ''gif'', ''jpg'', ''png'' \|
	+	\| Video \| ''webm'', ''ogv'', ''mp4'' \|
	+	\| Audio \| ''ogg'', ''mp3'', ''wav'' \|
	+	\| Flash \| ''swf'' \|
	+
	+	If you specify a filename that is not a supported media format, then it will be displayed as a link instead.
	+
	+	By adding ''?linkonly'' you provide a link to the media without displaying it inline
	+
	+	{{wiki:dokuwiki-128.png?linkonly}}
	+
	+	{{wiki:dokuwiki-128.png?linkonly}} This is just a link to the image.
	+
	+	==== Fallback Formats ====
	+
	+	Unfortunately not all browsers understand all video and audio formats. To mitigate the problem, you can upload your file in different formats for maximum browser compatibility.
	+
	+	For example consider this embedded mp4 video:
	+
	+	{{video.mp4\|A funny video}}
	+
	+	When you upload a ''video.webm'' and ''video.ogv'' next to the referenced ''video.mp4'', DokuWiki will automatically add them as alternatives so that one of the three files is understood by your browser.
	+
	+	Additionally DokuWiki supports a "poster" image which will be shown before the video has started. That image needs to have the same filename as the video and be either a jpg or png file. In the example above a ''video.jpg'' file would work.
	+
	+	===== Lists =====
	+
	+	Dokuwiki supports ordered and unordered lists. To create a list item, indent your text by two spaces and use a ''*'' for unordered lists or a ''-'' for ordered ones.
	+
	+	* This is a list
	+	* The second item
	+	* You may have different levels
	+	* Another item
	+
	+	- The same list but ordered
	+	- Another item
	+	- Just use indention for deeper levels
	+	- That's it
	+
	+	<code>
	+	* This is a list
	+	* The second item
	+	* You may have different levels
	+	* Another item
	+
	+	- The same list but ordered
	+	- Another item
	+	- Just use indention for deeper levels
	+	- That's it
	+	</code>
	+
	+	Also take a look at the [[doku>faq:lists\|FAQ on list items]].
	+
	+	===== Text Conversions =====
	+
	+	DokuWiki can convert certain pre-defined characters or strings into images or other text or HTML.
	+
	+	The text to image conversion is mainly done for smileys. And the text to HTML conversion is used for typography replacements, but can be configured to use other HTML as well.
	+
	+	==== Text to Image Conversions ====
	+
	+	DokuWiki converts commonly used [[wp>emoticon]]s to their graphical equivalents. Those [[doku>Smileys]] and other images can be configured and extended. Here is an overview of Smileys included in DokuWiki:
	+
	+	* 8-) %% 8-) %%
	+	* 8-O %% 8-O %%
	+	* :-( %% :-( %%
	+	* :-) %% :-) %%
	+	* =) %% =) %%
	+	* :-/ %% :-/ %%
	+	* :-\ %% :-\ %%
	+	* :-? %% :-? %%
	+	* :-D %% :-D %%
	+	* :-P %% :-P %%
	+	* :-O %% :-O %%
	+	* :-X %% :-X %%
	+	* :-\| %% :-\| %%
	+	* ;-) %% ;-) %%
	+	* ^_^ %% ^_^ %%
	+	* m( %% m( %%
	+	* :?: %% :?: %%
	+	* :!: %% :!: %%
	+	* LOL %% LOL %%
	+	* FIXME %% FIXME %%
	+	* DELETEME %% DELETEME %%
	+
	+	==== Text to HTML Conversions ====
	+
	+	Typography: [[DokuWiki]] can convert simple text characters to their typographically correct entities. Here is an example of recognized characters.
	+
	+	-> <- <-> => <= <=> >> << -- --- 640x480 (c) (tm) (r)
	+	"He thought 'It's a man's world'..."
	+
	+	<code>
	+	-> <- <-> => <= <=> >> << -- --- 640x480 (c) (tm) (r)
	+	"He thought 'It's a man's world'..."
	+	</code>
	+
	+	The same can be done to produce any kind of HTML, it just needs to be added to the [[doku>entities\|pattern file]].
	+
	+	There are three exceptions which do not come from that pattern file: multiplication entity (640x480), 'single' and "double quotes". They can be turned off through a [[doku>config:typography\|config option]].
	+
	+	===== Quoting =====
	+
	+	Some times you want to mark some text to show it's a reply or comment. You can use the following syntax:
	+
	+	<code>
	+	I think we should do it
	+
	+	> No we shouldn't
	+
	+	>> Well, I say we should
	+
	+	> Really?
	+
	+	>> Yes!
	+
	+	>>> Then lets do it!
	+	</code>
	+
	+	I think we should do it
	+
	+	> No we shouldn't
	+
	+	>> Well, I say we should
	+
	+	> Really?
	+
	+	>> Yes!
	+
	+	>>> Then lets do it!
	+
	+	===== Tables =====
	+
	+	DokuWiki supports a simple syntax to create tables.
	+
	+	^ Heading 1 ^ Heading 2 ^ Heading 3 ^
	+	\| Row 1 Col 1 \| Row 1 Col 2 \| Row 1 Col 3 \|
	+	\| Row 2 Col 1 \| some colspan (note the double pipe) \|\|
	+	\| Row 3 Col 1 \| Row 3 Col 2 \| Row 3 Col 3 \|
	+
	+	Table rows have to start and end with a ''\|'' for normal rows or a ''^'' for headers.
	+
	+	^ Heading 1 ^ Heading 2 ^ Heading 3 ^
	+	\| Row 1 Col 1 \| Row 1 Col 2 \| Row 1 Col 3 \|
	+	\| Row 2 Col 1 \| some colspan (note the double pipe) \|\|
	+	\| Row 3 Col 1 \| Row 3 Col 2 \| Row 3 Col 3 \|
	+
	+	To connect cells horizontally, just make the next cell completely empty as shown above. Be sure to have always the same amount of cell separators!
	+
	+	Vertical tableheaders are possible, too.
	+
	+	\| ^ Heading 1 ^ Heading 2 ^
	+	^ Heading 3 \| Row 1 Col 2 \| Row 1 Col 3 \|
	+	^ Heading 4 \| no colspan this time \| \|
	+	^ Heading 5 \| Row 2 Col 2 \| Row 2 Col 3 \|
	+
	+	As you can see, it's the cell separator before a cell which decides about the formatting:
	+
	+	\| ^ Heading 1 ^ Heading 2 ^
	+	^ Heading 3 \| Row 1 Col 2 \| Row 1 Col 3 \|
	+	^ Heading 4 \| no colspan this time \| \|
	+	^ Heading 5 \| Row 2 Col 2 \| Row 2 Col 3 \|
	+
	+	You can have rowspans (vertically connected cells) by adding ''%%:::%%'' into the cells below the one to which they should connect.
	+
	+	^ Heading 1 ^ Heading 2 ^ Heading 3 ^
	+	\| Row 1 Col 1 \| this cell spans vertically \| Row 1 Col 3 \|
	+	\| Row 2 Col 1 \| ::: \| Row 2 Col 3 \|
	+	\| Row 3 Col 1 \| ::: \| Row 2 Col 3 \|
	+
	+	Apart from the rowspan syntax those cells should not contain anything else.
	+
	+	^ Heading 1 ^ Heading 2 ^ Heading 3 ^
	+	\| Row 1 Col 1 \| this cell spans vertically \| Row 1 Col 3 \|
	+	\| Row 2 Col 1 \| ::: \| Row 2 Col 3 \|
	+	\| Row 3 Col 1 \| ::: \| Row 2 Col 3 \|
	+
	+	You can align the table contents, too. Just add at least two whitespaces at the opposite end of your text: Add two spaces on the left to align right, two spaces on the right to align left and two spaces at least at both ends for centered text.
	+
	+	^ Table with alignment ^^^
	+	\| right\| center \|left \|
	+	\|left \| right\| center \|
	+	\| xxxxxxxxxxxx \| xxxxxxxxxxxx \| xxxxxxxxxxxx \|
	+
	+	This is how it looks in the source:
	+
	+	^ Table with alignment ^^^
	+	\| right\| center \|left \|
	+	\|left \| right\| center \|
	+	\| xxxxxxxxxxxx \| xxxxxxxxxxxx \| xxxxxxxxxxxx \|
	+
	+	Note: Vertical alignment is not supported.
	+
	+	===== No Formatting =====
	+
	+	If you need to display text exactly like it is typed (without any formatting), enclose the area either with ''%%<nowiki>%%'' tags or even simpler, with double percent signs ''<nowiki>%%</nowiki>''.
	+
	+	<nowiki>
	+	This is some text which contains addresses like this: http://www.splitbrain.org and formatting, but nothing is done with it.
	+	</nowiki>
	+	The same is true for %%//__this__ text// with a smiley ;-)%%.
	+
	+	<nowiki>
	+	This is some text which contains addresses like this: http://www.splitbrain.org and formatting, but nothing is done with it.
	+	</nowiki>
	+	The same is true for %%//__this__ text// with a smiley ;-)%%.
	+
	+	===== Code Blocks =====
	+
	+	You can include code blocks into your documents by either indenting them by at least two spaces (like used for the previous examples) or by using the tags ''%%<code>%%'' or ''%%<file>%%''.
	+
	+	This is text is indented by two spaces.
	+
	+	<code>
	+	This is preformatted code all spaces are preserved: like <-this
	+	</code>
	+
	+	<file>
	+	This is pretty much the same, but you could use it to show that you quoted a file.
	+	</file>
	+
	+	Those blocks were created by this source:
	+
	+	This is text is indented by two spaces.
	+
	+	<code>
	+	This is preformatted code all spaces are preserved: like <-this
	+	</code>
	+
	+	<file>
	+	This is pretty much the same, but you could use it to show that you quoted a file.
	+	</file>
	+
	+	==== Syntax Highlighting ====
	+
	+	[[wiki:DokuWiki]] can highlight sourcecode, which makes it easier to read. It uses the [[http://qbnz.com/highlighter/\|GeSHi]] Generic Syntax Highlighter -- so any language supported by GeSHi is supported. The syntax uses the same code and file blocks described in the previous section, but this time the name of the language syntax to be highlighted is included inside the tag, e.g. ''<nowiki><code java></nowiki>'' or ''<nowiki><file java></nowiki>''.
	+
	+	<code java>
	+	/**
	+	* The HelloWorldApp class implements an application that
	+	* simply displays "Hello World!" to the standard output.
	+	*/
	+	class HelloWorldApp {
	+	public static void main(String[] args) {
	+	System.out.println("Hello World!"); //Display the string.
	+	}
	+	}
	+	</code>
	+
	+	The following language strings are currently recognized: //4cs 6502acme 6502kickass 6502tasm 68000devpac abap actionscript3 actionscript ada aimms algol68 apache applescript apt_sources arm asm asp asymptote autoconf autohotkey autoit avisynth awk bascomavr bash basic4gl batch bf biblatex bibtex blitzbasic bnf boo caddcl cadlisp ceylon cfdg cfm chaiscript chapel cil c_loadrunner clojure c_mac cmake cobol coffeescript c cpp cpp-qt cpp-winapi csharp css cuesheet c_winapi dart dcl dcpu16 dcs delphi diff div dos dot d ecmascript eiffel email epc e erlang euphoria ezt f1 falcon fo fortran freebasic freeswitch fsharp gambas gdb genero genie gettext glsl gml gnuplot go groovy gwbasic haskell haxe hicest hq9plus html html4strict html5 icon idl ini inno intercal io ispfpanel java5 java javascript jcl j jquery julia kixtart klonec klonecpp kotlin latex lb ldif lisp llvm locobasic logtalk lolcode lotusformulas lotusscript lscript lsl2 lua m68k magiksf make mapbasic mathematica matlab mercury metapost mirc mk-61 mmix modula2 modula3 mpasm mxml mysql nagios netrexx newlisp nginx nimrod nsis oberon2 objc objeck ocaml-brief ocaml octave oobas oorexx oracle11 oracle8 oxygene oz parasail parigp pascal pcre perl6 perl per pf phix php-brief php pic16 pike pixelbender pli plsql postgresql postscript povray powerbuilder powershell proftpd progress prolog properties providex purebasic pycon pys60 python qbasic qml q racket rails rbs rebol reg rexx robots roff rpmspec rsplus ruby rust sas sass scala scheme scilab scl sdlbasic smalltalk smarty spark sparql sql sshconfig standardml stonescript swift systemverilog tclegg tcl teraterm texgraph text thinbasic tsql twig typoscript unicon upc urbi uscript vala vbnet vb vbscript vedit verilog vhdl vim visualfoxpro visualprolog whitespace whois winbatch wolfram xbasic xml xojo xorg_conf xpp yaml z80 zxbasic//
	+
	+	There are additional [[doku>syntax_highlighting\|advanced options]] available for syntax highlighting, such as highlighting lines or adding line numbers.
	+
	+	==== Downloadable Code Blocks ====
	+
	+	When you use the ''%%<code>%%'' or ''%%<file>%%'' syntax as above, you might want to make the shown code available for download as well. You can do this by specifying a file name after language code like this:
	+
	+	<code>
	+	<file php myexample.php>
	+	<?php echo "hello world!"; ?>
	+	</file>
	+	</code>
	+
	+	<file php myexample.php>
	+	<?php echo "hello world!"; ?>
	+	</file>
	+
	+	If you don't want any highlighting but want a downloadable file, specify a dash (''-'') as the language code: ''%%<code - myfile.foo>%%''.
	+
	+	===== RSS/ATOM Feed Aggregation =====
	+	[[DokuWiki]] can integrate data from external XML feeds. For parsing the XML feeds, [[http://simplepie.org/\|SimplePie]] is used. All formats understood by SimplePie can be used in DokuWiki as well. You can influence the rendering by multiple additional space separated parameters:
	+
	+	^ Parameter ^ Description ^
	+	\| any number \| will be used as maximum number items to show, defaults to 8 \|
	+	\| reverse \| display the last items in the feed first \|
	+	\| author \| show item authors names \|
	+	\| date \| show item dates \|
	+	\| description\| show the item description. All HTML tags will be stripped \|
	+	\| nosort \| do not sort the items in the feed \|
	+	\| //n//[dhm] \| refresh period, where d=days, h=hours, m=minutes. (e.g. 12h = 12 hours). \|
	+
	+	The refresh period defaults to 4 hours. Any value below 10 minutes will be treated as 10 minutes. [[wiki:DokuWiki]] will generally try to supply a cached version of a page, obviously this is inappropriate when the page contains dynamic external content. The parameter tells [[wiki:DokuWiki]] to re-render the page if it is more than //refresh period// since the page was last rendered.
	+
	+	By default the feed will be sorted by date, newest items first. You can sort it by oldest first using the ''reverse'' parameter, or display the feed as is with ''nosort''.
	+
	+	Example:
	+
	+	{{rss>http://slashdot.org/index.rss 5 author date 1h }}
	+
	+	{{rss>http://slashdot.org/index.rss 5 author date 1h }}
	+
	+
	+	===== Control Macros =====
	+
	+	Some syntax influences how DokuWiki renders a page without creating any output it self. The following control macros are availble:
	+
	+	^ Macro ^ Description \|
	+	\| %%~~NOTOC~~%% \| If this macro is found on the page, no table of contents will be created \|
	+	\| %%~~NOCACHE~~%% \| DokuWiki caches all output by default. Sometimes this might not be wanted (eg. when the %%<php>%% syntax above is used), adding this macro will force DokuWiki to rerender a page on every call \|
	+
	+	===== Syntax Plugins =====
	+
	+	DokuWiki's syntax can be extended by [[doku>plugins\|Plugins]]. How the installed plugins are used is described on their appropriate description pages. The following syntax plugins are available in this particular DokuWiki installation:
	+
	+	~~INFO:syntaxplugins~~

symphotime_tips_and_tricks

Anonymous (anonymous@undisclosed.example.com) — 2020-04-03T14:54:26+00:00

2020/04/03 16:54		current
Line 1:		Line 1:

-	~~TOC~~

	{{tag>Howto Analysis Tutorial SymPhoTime Tips&Tricks}}		{{tag>Howto Analysis Tutorial SymPhoTime Tips&Tricks}}
Line 7:		Line 6:

	====== SymPhoTime 64 Analysis Tips and Tricks ======		====== SymPhoTime 64 Analysis Tips and Tricks ======
		+
		+	~~TOC~~
		+
	===== Summary =====		===== Summary =====

software

Anonymous (anonymous@undisclosed.example.com) — 2025-05-28T07:47:47+00:00

2025/05/28 09:18		current
Line 1:		Line 1:
	{{tag> software acquisition analysis}}		{{tag> software acquisition analysis}}

-	~~TOC~~

	====== Software ======		====== Software ======

how_can_i_analyze_my_data_using_non-picoquant_software

Anonymous (anonymous@undisclosed.example.com) — 2025-02-14T15:49:47+00:00

2025/01/31 10:01		current
Line 1:		Line 1:
	====== How can I analyze my data using non-PicoQuant software? ======		====== How can I analyze my data using non-PicoQuant software? ======

-	{{tag> faq file_format ptu open_source analysis}}	+	{{tag> faq file_format ptu open_source analysis software}}

	The PicoQuant raw-data format is freely accessible. PicoQuant has published some demo scripts for reading the different TCSPC/TTTR data formats on Github:		The PicoQuant raw-data format is freely accessible. PicoQuant has published some demo scripts for reading the different TCSPC/TTTR data formats on Github:

calculate_ratiometric_single_pair_fret_distributions_using_the_pie-fret_script

Anonymous (anonymous@undisclosed.example.com) — 2015-11-03T14:12:40+00:00

2014/06/18 18:06		current
Line 15:		Line 15:
	Note: The script requires a time trace containing the fluorescence of two spectrally separated channels, one channel mainly detecting the fluorescence of the donor dye and the other channel detecting mainly the fluorescence of the acceptor dye.\\		Note: The script requires a time trace containing the fluorescence of two spectrally separated channels, one channel mainly detecting the fluorescence of the donor dye and the other channel detecting mainly the fluorescence of the acceptor dye.\\
	The time traces can be acquired from single molecule events in a diluted solution, where the passages of single molecules are registered as "bursts". Alternatively, traces obtained from a stationary single FRET pair can be analyzed, e.g. to observe conformational changes.\\		The time traces can be acquired from single molecule events in a diluted solution, where the passages of single molecules are registered as "bursts". Alternatively, traces obtained from a stationary single FRET pair can be analyzed, e.g. to observe conformational changes.\\
-	To record such traces, usually single molecule sensitive detectors as [[glossary:spad\|SPAD]] or Hybrid-PMA are necessary to successfully detect single molecule fluorescence.\\	+	To record such traces, usually single molecule sensitive detectors as [[glossary:spad\|SPAD]] or [[glossary: Hybrid PMT]]s are necessary to successfully detect single molecule fluorescence.\\
	For the pulsed interleaved excitation ([[glossary:pie\|PIE]]) analysis of the script, pulsed excitation using two lasers is required, one laser exciting the donor, the other the acceptor dye. Usually, this is achieved using the multichannel laser driver PDL828 “Sepia II” in combination with two pulsed diode lasers.		For the pulsed interleaved excitation ([[glossary:pie\|PIE]]) analysis of the script, pulsed excitation using two lasers is required, one laser exciting the donor, the other the acceptor dye. Usually, this is achieved using the multichannel laser driver PDL828 “Sepia II” in combination with two pulsed diode lasers.

pycorrfit

Anonymous (anonymous@undisclosed.example.com) — 2016-03-07T11:00:06+00:00

2015/11/03 14:59		current
Line 4:		Line 4:
	"[...] PyCorrFit is a general-purpose FCS evaluation software that, amongst other formats, supports the established Zeiss ConfoCor3 ~.fcs file format. PyCorrFit comes with several built-in model functions, covering a wide range of applications in standard confocal FCS. In addition, it contains equations dealing with different excitation geometries like total internal reflection (TIR)."		"[...] PyCorrFit is a general-purpose FCS evaluation software that, amongst other formats, supports the established Zeiss ConfoCor3 ~.fcs file format. PyCorrFit comes with several built-in model functions, covering a wide range of applications in standard confocal FCS. In addition, it contains equations dealing with different excitation geometries like total internal reflection (TIR)."

-	[[http://paulmueller.github.io/PyCorrFit/]]	+	[[http://pycorrfit.craban.de/]]

	GitHub:[[https://github.com/paulmueller/PyCorrFit]]		GitHub:[[https://github.com/paulmueller/PyCorrFit]]

calculate_ratiometric_single_pair_fret_distributions

Anonymous (anonymous@undisclosed.example.com) — 2015-11-03T14:17:54+00:00

2014/06/18 17:56		current
Line 15:		Line 15:
	Note: The script requires a time trace containing the fluorescence of two spectrally separated channels, one channel mainly detecting the fluorescence of the donor dye and the other channel detecting mainly the fluorescence of the acceptor dye.\\		Note: The script requires a time trace containing the fluorescence of two spectrally separated channels, one channel mainly detecting the fluorescence of the donor dye and the other channel detecting mainly the fluorescence of the acceptor dye.\\
	The time traces can be acquired from single molecule events in a diluted solution, where the passages of single molecules are registered as "bursts". Alternatively, traces obtained from a stationary single FRET pair can be analyzed, e.g. to observe conformational changes.\\		The time traces can be acquired from single molecule events in a diluted solution, where the passages of single molecules are registered as "bursts". Alternatively, traces obtained from a stationary single FRET pair can be analyzed, e.g. to observe conformational changes.\\
-	To record such traces, usually single molecule sensitive detectors as SPAD or Hybrid PMA are necessary to successfully detect single molecule fluorescence.\\	+	To record such traces, usually single molecule sensitive detectors as [[glossary:SPAD]] or [[glossary:Hybrid PMT]]s are necessary to successfully detect single molecule fluorescence.\\

	\\		\\

lifetime_component_decomposition_phasor_plot_analysis

Anonymous (anonymous@undisclosed.example.com) — 2025-06-16T07:17:47+00:00

2025/06/16 09:17		current
Line 11:		Line 11:

	* Sample information:		* Sample information:
-	* Daisy Pollen	+	* Daisy pollen
		+
		+	---

	* Software information: NIS-Elements version 5.42.06 with PicoQuant FLIM-FCS full integration		* Software information: NIS-Elements version 5.42.06 with PicoQuant FLIM-FCS full integration
	{{:lifetime_component_decomposition_in_phasor_plot.mp4?1000\|}}		{{:lifetime_component_decomposition_in_phasor_plot.mp4?1000\|}}
-		+
	* Sample information:		* Sample information:
	* Glial Fibrillary Acidic Protein (GFAP) — labeled with BDP-TMR		* Glial Fibrillary Acidic Protein (GFAP) — labeled with BDP-TMR
	* Mitochondria (via TOM20) — labeled with CY3		* Mitochondria (via TOM20) — labeled with CY3

fluorescence_correlation_spectroscopy-_a_short_introduction

Anonymous (anonymous@undisclosed.example.com) — 2024-10-11T08:30:57+00:00

2023/02/17 13:43		current
Line 1:		Line 1:
	{{tag>MicroTime LSM Theory SymPhoTime FCS Correlation}}		{{tag>MicroTime LSM Theory SymPhoTime FCS Correlation}}

-	~~TOC~~	+

	====== Introduction to Fluorescence Correlation Spectroscopy ======		====== Introduction to Fluorescence Correlation Spectroscopy ======

calculate_and_fit_fcs_traces_with_the_fcs_script

Anonymous (anonymous@undisclosed.example.com) — 2015-11-03T14:11:17+00:00

2014/06/18 11:22		current
Line 17:		Line 17:
	* The diffusion coefficient of ATTO488 carboxilic acid has been measured to be 400 µm²/s at 25°C. Published diffusion coefficients of various fluorophores are summarized in the Technical Note "Absolute Diffusion Coefficients: Compilation of Reference Data for FCS Calibration" available from PicoQuant [see http://www.picoquant.com/images/uploads/page/files/7353/appnote_diffusioncoefficients.pdf ]. This list is extensive, but does not claim to be complete.		* The diffusion coefficient of ATTO488 carboxilic acid has been measured to be 400 µm²/s at 25°C. Published diffusion coefficients of various fluorophores are summarized in the Technical Note "Absolute Diffusion Coefficients: Compilation of Reference Data for FCS Calibration" available from PicoQuant [see http://www.picoquant.com/images/uploads/page/files/7353/appnote_diffusioncoefficients.pdf ]. This list is extensive, but does not claim to be complete.
	* Note that the diffusion coefficients of all dyes are temperature dependent.		* Note that the diffusion coefficients of all dyes are temperature dependent.
-	* FCS measurements are usually point measurements acquired with very sensitive detectors (typically SPAD or Hybrid PMT detectors).	+	* FCS measurements are usually point measurements acquired with very sensitive detectors (typically [[glossary:SPAD]] or [[glossary:Hybrid PMT]] detectors).
	* FCS is a technique that can be used over a wide range of concentrations, but ideal FCS concentrations are usually between 1 nM and 20 nM.		* FCS is a technique that can be used over a wide range of concentrations, but ideal FCS concentrations are usually between 1 nM and 20 nM.

Line 65:		Line 65:
	{{ calculate_and_fit_fcs_traces_with_the_fcs_script_Image_7.png?600 }}		{{ calculate_and_fit_fcs_traces_with_the_fcs_script_Image_7.png?600 }}

-	Note: A possibility to remove the afterpulsing when working with cw excitation is splitting the light onto two detectors and calculate a cross correlation. Some detectors (mainly Hybrid PMTs) also have so low afterpulsing that the problem does not occur.	+	Note: A possibility to remove the afterpulsing when working with cw excitation is splitting the light onto two detectors and calculate a cross correlation. Some detectors (mainly [[glossary:Hybrid PMT]]s) also have so low afterpulsing that the problem does not occur.

	* If the sample has beenexcited with cw light, we would now save the data by clicking "Save Result" and press afterwards "Transfer to Fit" (both in the "File" dropdown panel). As our sample has been excited with a pulsed laser, we can apply one additional step to increase data quality.		* If the sample has beenexcited with cw light, we would now save the data by clicking "Save Result" and press afterwards "Transfer to Fit" (both in the "File" dropdown panel). As our sample has been excited with a pulsed laser, we can apply one additional step to increase data quality.

visualizing_dynamics_using_the_multiframe-flim_script

Anonymous (anonymous@undisclosed.example.com) — 2023-02-17T12:41:10+00:00

2021/10/19 21:59		current
Line 1:		Line 1:
-	{{tag>howto FLIM multi-frame imaging analysis dynamics tutorial LSM_upgrade SPT SymPhoTime}}	+	{{tag>howto FLIM multi-frame imaging analysis dynamics tutorial LSM_upgrade SymPhoTime}}

	====== Visualizing Dynamics Using the Multi Frame FLIM Analysis (updated for SymPhoTime v2.5 and above) ======		====== Visualizing Dynamics Using the Multi Frame FLIM Analysis (updated for SymPhoTime v2.5 and above) ======

phasor_plot_structure_separation

Anonymous (anonymous@undisclosed.example.com) — 2025-06-16T08:36:34+00:00

2025/06/16 10:36		current
Line 1:		Line 1:
	{{tag> FLIM acquisition Nikon AX Phasor video LSM_upgrade howto}}		{{tag> FLIM acquisition Nikon AX Phasor video LSM_upgrade howto}}

-	====== Phasor-Based Structural Separation Using FLIM ======	+	====== Nikon AX: Phasor-Based Structural Separation Using FLIM ======

	Introduction		Introduction

imprint

Anonymous (anonymous@undisclosed.example.com) — 2018-05-23T08:30:11+00:00

2018/05/23 10:29		current
Line 11:		Line 11:
	https://www.picoquant.com\\		https://www.picoquant.com\\

-	Vertretungsberechtiger Geschäftsführer/General Manager: Rainer Erdmann	+	Vertretungsberechtiger Geschäftsführer/General Manager: Rainer Erdmann\\
-	HRB 60901 Berlin-Charlottenburg	+	HRB 60901 Berlin-Charlottenburg\\
-	VAT ID: DE 812140373	+	VAT ID: DE 812140373\\
-	WEEE-Reg.-Nr. DE 96457402	+	WEEE-Reg.-Nr. DE 96457402\\
-	Tax-ID.: 37/098/45817	+	Tax-ID.: 37/098/45817\\

calculate_ratiometric_fret-images

Anonymous (anonymous@undisclosed.example.com) — 2015-02-25T14:00:57+00:00

2014/06/18 11:24		current
Line 3:		Line 3:
	~~NOTOC~~		~~NOTOC~~

-	====== Calculate ratiometric FRET-Images ======	+	====== Calculate Ratiometric FRET Images ======

pattern_matching

Anonymous (anonymous@undisclosed.example.com) — 2014-06-18T13:26:07+00:00

2014/05/23 09:39		current
Line 10:		Line 10:

	Pattern Matching Analysis by decomposing a recorded image into different user-defined patterns. Display of the calculated data using an RGB false color model. The calculated amplitudes of the first three defined patterns are depicted in three different colors for each pixel.		Pattern Matching Analysis by decomposing a recorded image into different user-defined patterns. Display of the calculated data using an RGB false color model. The calculated amplitudes of the first three defined patterns are depicted in three different colors for each pixel.
		+
		+	{{ youtube>L68IgRbNSLE?large }}

	==== Open an Image ====		==== Open an Image ====

using_the_flcs_script_for_spectral_crosstalk_removal_via_flccs

Anonymous (anonymous@undisclosed.example.com) — 2015-02-25T14:00:13+00:00

2014/06/19 10:09		current
Line 2:		Line 2:
	~~NOTOC~~		~~NOTOC~~

-	====== Spectral crosstalk removal via FLCCS ======	+	====== Spectral Crosstalk Removal via FLCCS ======

basics

Anonymous (anonymous@undisclosed.example.com) — 2024-10-11T08:23:47+00:00

2021/09/23 14:59		current
Line 1:		Line 1:
	{{tag> basics introduction FCS fluorescence microscopy objective resolution NA tutorials}}		{{tag> basics introduction FCS fluorescence microscopy objective resolution NA tutorials}}
-	===== Basics =====	+	====== Basics ======

	* [[video_tutorials\|Fluorescence and Fluorescence Microscopy by Nico Stuurman]]		* [[video_tutorials\|Fluorescence and Fluorescence Microscopy by Nico Stuurman]]

t3-mode

Anonymous (anonymous@undisclosed.example.com) — 2015-02-10T16:27:57+00:00

2015/02/10 17:27		current
Line 12:		Line 12:
	- the arrival time of the event pair on the overall experiment time scale (the time tag).		- the arrival time of the event pair on the overall experiment time scale (the time tag).

-	The latter was originally obtained from an independent asynchronous clock. This made it difficult to combine the start-stop timing with the time tag or to know the sync period the event belonged to. For the PicoHarp's T3 Mode a smarter approach was chosen:\\	+	The latter was originally obtained from an independent asynchronous clock. This made it difficult to combine the start-stop timing with the time tag or to know the sync period the event belonged to. For the *Harp's T3 Mode a smarter approach was chosen:\\
	The time tag is now obtained by simply counting sync pulses. From the T3 Mode event records it is therefore possible to precisely determine which sync period a photon event belongs to. Since the sync period is also known precisely, this furthermore allows to reconstruct the arrival time of the photon with respect to the overall experiment time.		The time tag is now obtained by simply counting sync pulses. From the T3 Mode event records it is therefore possible to precisely determine which sync period a photon event belongs to. Since the sync period is also known precisely, this furthermore allows to reconstruct the arrival time of the photon with respect to the overall experiment time.

calculate_fccs_trace_with_the_grouped_fcs_script

Anonymous (anonymous@undisclosed.example.com) — 2020-04-01T15:05:26+00:00

2015/02/25 15:01		current
Line 2:		Line 2:
	~~NOTOC~~		~~NOTOC~~

-	====== Calculate Multiple FCCS Traces with the Grouped FCS Script ======	+	====== Calculate FCCS Traces with the Grouped FCS Script ======

	===== Summary =====		===== Summary =====

flim_fret_calculation_for_multi_exponential_donors

Anonymous (anonymous@undisclosed.example.com) — 2023-11-21T10:33:47+00:00

2020/05/12 14:44		current
Line 3:		Line 3:
	~~NOTOC~~		~~NOTOC~~

-	====== FLIM FRET Calculation for Multi Exponential Donors ======	+	====== FLIM-FRET Calculation for Multi Exponential Donors ======

flim-fret_calculation_for_single_exponential_donors

Anonymous (anonymous@undisclosed.example.com) — 2020-05-06T09:38:57+00:00

2020/05/06 11:19		current
Line 85:		Line 85:

	Response: In the image, only pixels with higher photon counts are highlighted. Adapt the intensity maximum to see the highlighted pixels more clearly.		Response: In the image, only pixels with higher photon counts are highlighted. Adapt the intensity maximum to see the highlighted pixels more clearly.
-	{{ :howto:flim-fret-1expd_roi_from_thresh_2_v2.png?400 \|}}	+	{{ :howto:flim-fret-1expd_roi_from_thresh_2_v3.png?400 \|}}

	* In the lifetime fitting panel, keep the default Fitting model "Mono-Exp. Donor".		* In the lifetime fitting panel, keep the default Fitting model "Mono-Exp. Donor".

phasor_analysis

Anonymous (anonymous@undisclosed.example.com) — 2019-08-28T16:15:15+00:00

2019/08/28 18:15		current
Line 1:		Line 1:
-	{{tag> FLIM howto phasor bin-export binexport analysis tutorial SymPhoTime Globals software}}	+	{{tag> FLIM howto phasor bin-export bin_export analysis tutorial SymPhoTime Globals software}}

	~~TOC~~		~~TOC~~

start

Anonymous (anonymous@undisclosed.example.com) — 2026-02-11T14:19:03+00:00

2024/12/19 16:57		current
Line 8:		Line 8:
	{{topic>howto -FT300 -sample -analysis -draft &nodate&nouser}}		{{topic>howto -FT300 -sample -analysis -draft &nodate&nouser}}

-	===== NovaFLIM / Analysis =====
-
-	{{topic>howto +tutorial +novaflim -draft &nodate&nouser}}

	===== SymPhoTime64 / Analysis =====		===== SymPhoTime64 / Analysis =====

microtime

Anonymous (anonymous@undisclosed.example.com) — 2015-11-03T14:24:05+00:00

2015/11/03 15:23		current
Line 19:		Line 19:
	* Turn-key diode lasers for multicolor excitation from 375 nm to 900 nm		* Turn-key diode lasers for multicolor excitation from 375 nm to 900 nm
	* Up to 4 truly parallel detection channels using application-optimized detection with [[glossary:SPAD]]s, [[glossary:PMT]]s or [[glossary:Hybrid PMT]]s		* Up to 4 truly parallel detection channels using application-optimized detection with [[glossary:SPAD]]s, [[glossary:PMT]]s or [[glossary:Hybrid PMT]]s
-	* Time-Correlated-Single Photon Counting ([[glossary:TCSPC]]) and [[glossary:TTTR]] mode for investigation of fast dynamics in FCS and FLIM	+	* Time-Correlated-Single Photon Counting ([[glossary:TCSPC]]) and [[glossary:TTTR]] mode for investigation of fast dynamics in [[glossary:FCS]] and [[glossary:FLIM]]
	* Piezo scanning for 2D- and 3D-lifetime imaging and accurate point positioning		* Piezo scanning for 2D- and 3D-lifetime imaging and accurate point positioning
	* Two optional exit ports for additional hardware, e.g. spectrographs		* Two optional exit ports for additional hardware, e.g. spectrographs

flimfit

Anonymous (anonymous@undisclosed.example.com) — 2014-05-23T09:04:11+00:00

2014/05/23 11:02		current
Line 1:		Line 1:
-	{{tag> software analysis FLIM }}	+	{{tag> software analysis FLIM open_source}}

	====== FLIMfit ======		====== FLIMfit ======

legal_information

Anonymous (anonymous@undisclosed.example.com) — 2019-02-15T14:29:59+00:00

2026/04/23 20:33		current
Line 1:		Line 1:
		+	This page is redirected to [[:fluotime250:legal_information]].

measurement_hardware_instrumentation

Anonymous (anonymous@undisclosed.example.com) — 2018-06-25T07:18:07+00:00

2018/06/25 09:17		current
Line 32:		Line 32:
	[[video_tutorials#Kurt Thorn: Optical Sectioning and Confocal Microscopy\|Confocal microscoy and optical sectioning by Kurt Thorn]]		[[video_tutorials#Kurt Thorn: Optical Sectioning and Confocal Microscopy\|Confocal microscoy and optical sectioning by Kurt Thorn]]

-	[[technical docs:Beampath of the Zeiss LSM880]]	+	[[Beampath of the Zeiss LSM880]]

	[[howto:check_overlap_of_different_color_confocal_volumes\|How to check the overlap of different color confocal volumes]]		[[howto:check_overlap_of_different_color_confocal_volumes\|How to check the overlap of different color confocal volumes]]

contributing

Anonymous (anonymous@undisclosed.example.com) — 2018-02-19T08:06:13+00:00

2018/02/19 09:04		current
Line 11:		Line 11:
	Links that don't have an article yet will be shown in red. This makes it easy for others to just start this article.		Links that don't have an article yet will be shown in red. This makes it easy for others to just start this article.

-	====== Most wanted pages ======	+	====== Most searched words ======
	~~SEARCHCLOUD~~		~~SEARCHCLOUD~~

cfd

Anonymous (anonymous@undisclosed.example.com) — 2015-09-23T14:55:11+00:00

2013/08/06 16:37		current
Line 5:		Line 5:
	[{{ glossary:constantfraction.png?400\|Comparison of threshold activation (left) to CFD activation (right) }}]		[{{ glossary:constantfraction.png?400\|Comparison of threshold activation (left) to CFD activation (right) }}]

-	The CFD is used to extract precise timing information from electrical detector pulses that may vary in amplitude. Thereby the overall system IRF can be narrowed and some of the random background signal can be suppressed. This cannot not be achieved with a simple threshold detector (comparator). Constant fraction discrimination is very important, especially in the case of [[PMTs]], because their pulse amplitudes vary significantly.	+	The CFD is used to extract precise timing information from electrical detector pulses that may vary in amplitude. Thereby the overall system IRF can be narrowed and some of the random background signal can be suppressed. This cannot not be achieved with a simple threshold detector (comparator). Constant fraction discrimination is very important, especially in the case of [[PMT]]s, because their pulse amplitudes vary significantly.

	A CFD compares the original detector signal with an amplified and delayed version of itself. The signal derived from this comparison changes polarity exactly when a constant fraction of the detector pulse height is reached. The zero crossing point of this signal is therefore suitable to derive a timing signal independent from the amplitude of the input pulse. This is done by comparing this signal to a zero cross level. This level should be adjusted to remove events that originate from signal noise. CFDs furthermore permit to set a discriminator threshold for the pulse amplitude.		A CFD compares the original detector signal with an amplified and delayed version of itself. The signal derived from this comparison changes polarity exactly when a constant fraction of the detector pulse height is reached. The zero crossing point of this signal is therefore suitable to derive a timing signal independent from the amplitude of the input pulse. This is done by comparing this signal to a zero cross level. This level should be adjusted to remove events that originate from signal noise. CFDs furthermore permit to set a discriminator threshold for the pulse amplitude.

deconvolution

Anonymous (anonymous@undisclosed.example.com) — 2013-08-06T14:41:19+00:00

2013/08/06 16:13		current
Line 1:		Line 1:
	====== Deconvolution ======		====== Deconvolution ======
-
-	===== What is "Deconvolution"? =====

	Deconvolution is used in time domain data analysis for removal of broadening effects due to instrumental resolution. In this context deconvolution is mainly concerned with the [[IRF]] (or lamp function) including the finite light source pulse width and other broadening effects (e.g. electronics). The effects caused by the [[IRF]] are dominant in the onset of a decay curve.		Deconvolution is used in time domain data analysis for removal of broadening effects due to instrumental resolution. In this context deconvolution is mainly concerned with the [[IRF]] (or lamp function) including the finite light source pulse width and other broadening effects (e.g. electronics). The effects caused by the [[IRF]] are dominant in the onset of a decay curve.
Line 8:		Line 6:
	===== How deconvolution should be done =====		===== How deconvolution should be done =====

-	Best, not at all ;-). At PQ we use [[reconvolution]] instead, for a variety of good reasons (see [[IRF]]). If one cannot resist applying deconvolution, the best way of doing it (at least for time domain data) would be via Fourier transform. Fourier transform is a slow process (even with [[FFT]]) and it has to be done twice, since the deconvoultion itself is performed on the transformed data set, which has to be retransformed afterwards.	+	Best, not at all ;-). At PicoQuant, for a variety of good reasons (see [[IRF]]) we use [[reconvolution]] instead. If one cannot resist applying deconvolution, the best way of doing it (at least for time domain data) would be via Fourier transform. Fourier transform is a slow process (even with [[FFT]]) and it has to be done twice, since the deconvoultion itself is performed on the transformed data set, which has to be retransformed afterwards.


Line 14:		Line 12:

	The most prominent application of deconvolution techniques is imaging. Usually one tries to remove blurring by deconvolution (or deconvolution-like) techniques. What holds for time domain data, also holds for imaging: Deconvolution has a disturbingly high potential for producing artefacts - and there is no way of telling apart artefacts and effects. The images may look nicer (which undoubtedly is valuable especially for publication purposes), but the content of information has not necessarily improved.		The most prominent application of deconvolution techniques is imaging. Usually one tries to remove blurring by deconvolution (or deconvolution-like) techniques. What holds for time domain data, also holds for imaging: Deconvolution has a disturbingly high potential for producing artefacts - and there is no way of telling apart artefacts and effects. The images may look nicer (which undoubtedly is valuable especially for publication purposes), but the content of information has not necessarily improved.
-

flim

Anonymous (anonymous@undisclosed.example.com) — 2015-11-03T14:28:34+00:00

2015/11/03 15:28		current
Line 1:		Line 1:
-	~~TOC~~	+
	{{tag>FLIM}}		{{tag>FLIM}}
		+
		+	~~TOC~~
	====== FLIM ======		====== FLIM ======

t2-mode

Anonymous (anonymous@undisclosed.example.com) — 2015-02-10T16:24:41+00:00

2015/02/10 17:22		current
Line 1:		Line 1:
	====== T2-mode ======		====== T2-mode ======

-	A special measurement mode of the [[Products:PicoHarp 300]]	+	A special measurement mode of the [[Products:PicoHarp 300]], [[Products:HydraHarp 400]] and [[Products:TimeHarp 260]]


Line 7:		Line 7:
	In T2 Mode both signal inputs of the PicoHarp 300 are functionally identical. There is no dedication of input channel 0 to a [[SYNC]] signal. Usually both inputs are used to connect photon detectors. The events from both channels are recorded independently and treated equally. In each case an event record is generated that contains information about the channel it came from and the arrival time of the event with respect to the overall measurement start. The timing is recorded with 4 ps resolution. Each T2 Mode event record consists of 32 bits. There are 4 bits for the channel number and 28 bits for the time-tag. Routing is not supported. If the time tag overflows, a special overflow marker record is inserted in the data stream, so that upon processing of the data stream a theoretically infinite time span can be recovered at full resolution. [[Dead time]]s exist only within each channel (95 ns typ.) but not across the channels. Therefore, cross correlations can be calculated down to zero lag time. This allows powerful new application such as [[FCS]] with lag times from picoseconds to hours. Autocorrelations can also be calculated at the full resolution but of course only starting from lag times larger than the [[dead time]].		In T2 Mode both signal inputs of the PicoHarp 300 are functionally identical. There is no dedication of input channel 0 to a [[SYNC]] signal. Usually both inputs are used to connect photon detectors. The events from both channels are recorded independently and treated equally. In each case an event record is generated that contains information about the channel it came from and the arrival time of the event with respect to the overall measurement start. The timing is recorded with 4 ps resolution. Each T2 Mode event record consists of 32 bits. There are 4 bits for the channel number and 28 bits for the time-tag. Routing is not supported. If the time tag overflows, a special overflow marker record is inserted in the data stream, so that upon processing of the data stream a theoretically infinite time span can be recovered at full resolution. [[Dead time]]s exist only within each channel (95 ns typ.) but not across the channels. Therefore, cross correlations can be calculated down to zero lag time. This allows powerful new application such as [[FCS]] with lag times from picoseconds to hours. Autocorrelations can also be calculated at the full resolution but of course only starting from lag times larger than the [[dead time]].

-	The 32 bit event records are queued in a [[FIFO]] (First In First Out) buffer capable of holding up to 256 k event records. The FIFO input is fast enough to accept records at the full speed of the time-to-digital converters (up to 10 Mcps each). This means, even during a fast burst no events will be dropped except those lost in the [[dead time]] anyhow. The FIFO output is continuously read by the host PC, thereby making room for fresh incoming events. Even if the average read rate of the host PC is limited, bursts with much higher rate can be recorded for some time. Only if the average count rate over a long period of time exceeds the readout speed of the PC, a FIFO overrun could occur. In case of a FIFO overrun the measurement must be aborted because data integrity cannot be maintained. However, on a modern and well configured PC with Windows 2000 or XP a sustained average count rate over 4 Mcps is possible. This total transfer rate must be shared by the two input channels. For all practically relevant fluorescence detection applications the effective rate per channel is more than sufficient.	+	The 32 bit event records are queued in a [[FIFO]] (First In First Out) buffer capable of holding up to 256 k event records. The FIFO input is fast enough to accept records at the full speed of the time-to-digital converters (up to 10 Mcps each). This means, even during a fast burst no events will be dropped except those lost in the [[dead time]] anyhow. The FIFO output is continuously read by the host PC, thereby making room for fresh incoming events. Even if the average read rate of the host PC is limited, bursts with much higher rate can be recorded for some time. Only if the average count rate over a long period of time exceeds the readout speed of the PC, a FIFO overrun could occur. In case of a FIFO overrun the measurement must be aborted because data integrity cannot be maintained. However, on a modern and well configured PC a sustained average count rate over 4 Mcps is possible. This total transfer rate must be shared by the two input channels. For all practically relevant fluorescence detection applications the effective rate per channel is more than sufficient.

-	For maximum throughput, T2 Mode data streams are normally written directly to disk. The current PicoHarp software 1.2 does not provide any immediate data visualization during a T2 Mode measurement, except count rate and progress display. However, using custom software it is also possible to analyze incoming data "on the fly". Even on-line correlation can be implemented. Obviously this requires efficient processing and possible restrictions in average count rate. The PicoHarp software installation CD contains demo programs to show how T2 Mode files can be read by custom software. The implementation of custom measurement programs requires the PicoHarp programming library, which is available as a separate option.	+	For maximum throughput, T2 Mode data streams are normally written directly to disk. The current Harp software does not provide any immediate data visualization during a T2 Mode measurement, except count rate and progress display. However, using custom software it is also possible to analyze incoming data "on the fly". Even on-line correlation can be implemented. Obviously this requires efficient processing and possible restrictions in average count rate. The PicoHarp software installation CD contains demo programs to show how T2 Mode files can be read by custom software. The implementation of custom measurement programs requires the Harp programming library, which is available as a separate option.

	Note: From a mathematical point of view, the T2 mode should be able to store 28 bit = 228 = 268435456 time bin data before need to "wrap around". However, the real wrap around time as shown in the demo code is only 210698240. This discrepancy is due to the design of the TDCs. Briefly, the [[TDCs]] include a coarse scaler and an interpolator for the the short times. This interpolator is not working in a binary fashion, which finally leads to the fact that not the full available memory is used. This does not lead to any data loss. To reconstruct the full temporal time trace one only needs to follow the procedures shown in the demo code		Note: From a mathematical point of view, the T2 mode should be able to store 28 bit = 228 = 268435456 time bin data before need to "wrap around". However, the real wrap around time as shown in the demo code is only 210698240. This discrepancy is due to the design of the TDCs. Briefly, the [[TDCs]] include a coarse scaler and an interpolator for the the short times. This interpolator is not working in a binary fashion, which finally leads to the fact that not the full available memory is used. This does not lead to any data loss. To reconstruct the full temporal time trace one only needs to follow the procedures shown in the demo code

	see also [[.:t3-mode]]		see also [[.:t3-mode]]
-

tttr

Anonymous (anonymous@undisclosed.example.com) — 2015-02-10T16:42:50+00:00

2015/02/10 17:42		current
Line 6:		Line 6:
	The [[Products:TimeHarp 200]] (also the [[Products:TimeHarp 100]]), the [[Products:PicoHarp 300]] [[Products:HydraHarp 400]] support TTTR mode measurements. With the the [[Products:PicoHarp 300]] a slight shift in the nomenclature was introduced. Due to its capability of simultaneously recording both signal inputs (in interactive mode used as 'Start' and 'Stop') as two separate TTTR traces with a time resolution of 4ps, a new TTTR mode was introduced, the so called T2-mode. The traditional recording as with the [[Products:TimeHarp 200]] / [[Products:TimeHarp 100]] is called [[T3-mode]]. In [[T2-mode]] both signal inputs are functionally identical.		The [[Products:TimeHarp 200]] (also the [[Products:TimeHarp 100]]), the [[Products:PicoHarp 300]] [[Products:HydraHarp 400]] support TTTR mode measurements. With the the [[Products:PicoHarp 300]] a slight shift in the nomenclature was introduced. Due to its capability of simultaneously recording both signal inputs (in interactive mode used as 'Start' and 'Stop') as two separate TTTR traces with a time resolution of 4ps, a new TTTR mode was introduced, the so called T2-mode. The traditional recording as with the [[Products:TimeHarp 200]] / [[Products:TimeHarp 100]] is called [[T3-mode]]. In [[T2-mode]] both signal inputs are functionally identical.

-	Today recording of [[glossary:T3-mode]] and T2 mode files is possible with all recent PicoQuant TCSPC devices ([[Products:TimeHarp 260]], [[Products:PicoHarp 300]] and [[Products:HydraHarp 400]] and their included software, analysis is supported mainly by the [[software:SymPhoTime]] software package.	+	Today recording of [[glossary:T3-mode]] and [[glossary:T2-mode]] files is possible with all recent PicoQuant TCSPC devices ([[Products:TimeHarp 260]], [[Products:PicoHarp 300]] and [[Products:HydraHarp 400]] and their included software, analysis is supported mainly by the [[software:SymPhoTime]] software package.

	Due to its capability of including external TTL pulses as markers in the stream of photon events TTTR mode is suitable for [[FLIM]] measurements. The markers are used to synchronise the photon events with a scanning process allowing to sort the photons into image pixels.		Due to its capability of including external TTL pulses as markers in the stream of photon events TTTR mode is suitable for [[FLIM]] measurements. The markers are used to synchronise the photon events with a scanning process allowing to sort the photons into image pixels.

calibrate_the_confocal_volume_for_fcs_using_the_fcs_calibration_script

Anonymous (anonymous@undisclosed.example.com) — 2019-02-07T12:16:52+00:00

2019/02/07 13:13		current
Line 17:		Line 17:
	Note: Calibration is a necessary task for FCS measurements. In a calibration procedure, the confocal volume VEff as well as the structural parameter κ (the ratio of z to xy extension) is determined using a reference dye. This is the prerequisite to determine correct diffusion coefficients and concentrations for the sample of interest.\\		Note: Calibration is a necessary task for FCS measurements. In a calibration procedure, the confocal volume VEff as well as the structural parameter κ (the ratio of z to xy extension) is determined using a reference dye. This is the prerequisite to determine correct diffusion coefficients and concentrations for the sample of interest.\\
	ATTO488 (ATTO-Tec, Germany) is a suited dye to calibrate the confocal microscope at ~470 – 490 nm excitation and detection around 500 – 540 nm.\\		ATTO488 (ATTO-Tec, Germany) is a suited dye to calibrate the confocal microscope at ~470 – 490 nm excitation and detection around 500 – 540 nm.\\
-	The diffusion coefficient of ATTO488 carboxilic acid has been measured to be 400 µm²/s at 25°C. Published diffusion coefficients of various fluorophores are summarized in the Technical Note "Absolute Diffusion Coefficients: Compilation of Reference Data for FCS Calibration" available from PicoQuant [see [[https://www.picoquant.com/images/uploads/page/files/7353/appnote_diffusioncoefficients.pdf]]]. This list is extensive, but does not claim to be complete.\\	+	The diffusion coefficient of ATTO488 carboxilic acid has been measured to be 400 µm²/s at 25°C. Published diffusion coefficients of various fluorophores are summarized in the Technical Note "Absolute Diffusion Coefficients: Compilation of Reference Data for FCS Calibration" available from PicoQuant (see [[https://www.picoquant.com/images/uploads/page/files/7353/appnote_diffusioncoefficients.pdf]]). This list is extensive, but does not claim to be complete.\\
	Note that the diffusion coefficients of all dyes are temperature dependent.\\		Note that the diffusion coefficients of all dyes are temperature dependent.\\
	FCS measurements are usually point measurements acquired with very sensitive detectors ([[glossary:spad\|SPAD]] or [[glossary:Hybrid PMT]] detectors).\\		FCS measurements are usually point measurements acquired with very sensitive detectors ([[glossary:spad\|SPAD]] or [[glossary:Hybrid PMT]] detectors).\\

how_to_work_with_the_instrument_response_function_irf

Anonymous (anonymous@undisclosed.example.com) — 2023-02-17T12:41:49+00:00

2021/03/23 11:49		current
Line 1:		Line 1:
-	{{tag>howto IRF tutorial analysis MT LSM_upgrade}}	+	{{tag>howto IRF tutorial analysis MicroTime LSM_upgrade}}

lifetime-fitting_using_the_rapid_reconvolution_algorithm

Anonymous (anonymous@undisclosed.example.com) — 2023-02-17T12:40:42+00:00

2021/06/12 07:05		current
Line 1:		Line 1:
-		+	{{tag>howto tutorial FLIM analysis SymPhoTime MT LSM_upgrade reconvolution fitting}}
-	{{tag>howto tutorial FLIM analysis SPT SymPhoTime MT LSM_upgrade reconvolution fitting}}	+

roi_fitting_using_the_flim_script

Anonymous (anonymous@undisclosed.example.com) — 2023-02-23T07:08:46+00:00

2020/05/13 11:42		current
Line 9:		Line 9:


-	This tutorial shows step-by-step, how the [[glossary:flim\|FLIM]] script of [[products:SymPhoTime64\|SymPhoTime 64]] can be used to fit several regions of interest (ROIs), and how to extract and interpret the results. In detail, the FLIM script is started using a daisy pollen image from the "Samples" – workspace, then three regions of interest are defined which are finally fitted.	+	This tutorial shows step-by-step, how the [[glossary:flim\|FLIM]] script of [[products:SymPhoTime64\|SymPhoTime 64]] can be used to fit several regions of interest (ROIs), and how to extract and interpret the results. In details, the FLIM script is started using a daisy pollen image from the "Samples" – workspace, then three regions of interest are defined which are finally fitted.

	{{ youtube>g6uyvLQW4nY?large }}		{{ youtube>g6uyvLQW4nY?large }}

separation_of_2_species_with

Anonymous (anonymous@undisclosed.example.com) — 2014-06-18T12:22:45+00:00

2014/06/18 12:57		current
Line 1:		Line 1:
	{{tag> howto tutorial FCS FLCS analysis SymPhoTime}}		{{tag> howto tutorial FCS FLCS analysis SymPhoTime}}

-	~~TOC~~	+	~~NOTOC~~

	====== Separation of 2 Species with Different Lifetimes Using FLCS ======		====== Separation of 2 Species with Different Lifetimes Using FLCS ======
Line 11:		Line 11:
	This tutorial shows step-by-step, how the FLCS analysis can be used to calculate separate autocorrelation curves for the two components of a mixture of ATTO655 and Cy5 based on their different lifetimes.		This tutorial shows step-by-step, how the FLCS analysis can be used to calculate separate autocorrelation curves for the two components of a mixture of ATTO655 and Cy5 based on their different lifetimes.

		+	{{ youtube>xx-WzT5TgqA?large }}

	===== Background Information =====		===== Background Information =====
Line 218:		Line 218:
	* Click on "Save result" to save this curve. Rename the generated file as "Cy5-FLCS".		* Click on "Save result" to save this curve. Rename the generated file as "Cy5-FLCS".
	* These curves can now be fitted by selecting "Transfer to fit". The process of how to fit a FCS curve is explained in the tutorial [[howto:Calculate and Fit FCS Traces with the FCS Script]].		* These curves can now be fitted by selecting "Transfer to fit". The process of how to fit a FCS curve is explained in the tutorial [[howto:Calculate and Fit FCS Traces with the FCS Script]].
-

using_the_antibunching_script

Anonymous (anonymous@undisclosed.example.com) — 2014-06-19T07:40:32+00:00

2014/06/19 09:36		current
Line 1:		Line 1:
	{{tag> antibunching howto tutorial correlation analysis SymPhoTime}}		{{tag> antibunching howto tutorial correlation analysis SymPhoTime}}
-	~~TOC~~	+	~~NOTOC~~

	====== Antibunching Analysis ======		====== Antibunching Analysis ======
Line 9:		Line 9:

	This tutorial shows step-by-step, how to calculate an antibunching curve from a fluorescence time trace of a single emitter, in this example a nanodiamond NV center, excited with a pulsed 530 nm laser.		This tutorial shows step-by-step, how to calculate an antibunching curve from a fluorescence time trace of a single emitter, in this example a nanodiamond NV center, excited with a pulsed 530 nm laser.
		+
		+	{{ youtube>bEyhuWnmFC4?large }}

	===== Background Information =====		===== Background Information =====
Line 77:		Line 79:

	* Here it is impossible to determine the number of emitters. In this measurement the luminescence stems from several emitters.		* Here it is impossible to determine the number of emitters. In this measurement the luminescence stems from several emitters.
-

visualizing_dynamics_with_the_multi_frame_flim_analysis

Anonymous (anonymous@undisclosed.example.com) — 2020-05-13T09:39:06+00:00

2015/11/03 15:33		current
Line 3:		Line 3:
	~~NOTOC~~		~~NOTOC~~

-	====== Visualizing Dynamics with the Multi Frame FLIM Analysis ======	+	====== Visualizing Dynamics Using the Multi Frame FLIM Analysis ======

	===== Summary =====		===== Summary =====

hydraharp_400

Anonymous (anonymous@undisclosed.example.com) — 2015-09-23T11:43:51+00:00

2015/09/23 13:43		current
Line 3:		Line 3:
	The HydraHarp 400 is a high-end, easy to use, plug and play Time Interval Analyzer (TIA) and Time-Correlated Single Photon Counting (TCSPC) system with scalability for multiple channels. It is connected to a PC through a USB 3.0 high speed interface.		The HydraHarp 400 is a high-end, easy to use, plug and play Time Interval Analyzer (TIA) and Time-Correlated Single Photon Counting (TCSPC) system with scalability for multiple channels. It is connected to a PC through a USB 3.0 high speed interface.

-	See [[http://www.picoquant.com/products/category/tcspc-and-time-tagging-modules/hydraharp-400-multichannel-picosecond-event-timer-tcspc-module\|here]] for more information	+	See the [[http://www.picoquant.com/products/category/tcspc-and-time-tagging-modules/hydraharp-400-multichannel-picosecond-event-timer-tcspc-module\|picoquant.com website]] for more information.

	===== Software =====		===== Software =====

fcs_viewer

Anonymous (anonymous@undisclosed.example.com) — 2015-02-25T16:51:37+00:00

2014/05/23 11:04		current
Line 4:		Line 4:


-	[[https://github.com/dwaithe/FCS_viewer]]	+	[[https://github.com/paulmueller/FCS_viewer]]

	Contains a port of the PicoQuant Matlab demo code to Python.		Contains a port of the PicoQuant Matlab demo code to Python.

symphotime64

Anonymous (anonymous@undisclosed.example.com) — 2015-01-22T14:39:59+00:00

2014/05/23 09:34		current
Line 5:		Line 5:


-	The [[http://www.picoquant.com\|PicoQuant]] SymPhoTime 64 software package is an integrated solution for data acquisition and analysis using PicoQuant's time-resolved confocal microscope MicroTime 200, LSM upgrade kits or [[glossary:TCSPC]] electronics. Its clearly structured layout and powerful analysis routines allows the user to focus on the results rather than on the data processing. The software is designed for a 64 bit operation system and features a graphical user interface (GUI), which guides the user through all necessary steps for an individual analysis or measurement process. Data dependencies are directly visible in the underlying workspace concept. An integrated scripting language ("STUPSLANG") even puts the user in a position to freely add new analysis procedures or customize existing ones.	+	The [[http://www.picoquant.com\|PicoQuant]] SymPhoTime 64 software package is an integrated solution for data acquisition and analysis using PicoQuant's time-resolved confocal microscope [[products:MicroTime]], LSM upgrade kits or [[glossary:TCSPC]] electronics. Its clearly structured layout and powerful analysis routines allows the user to focus on the results rather than on the data processing. The software is designed for a 64 bit operation system and features a graphical user interface (GUI), which guides the user through all necessary steps for an individual analysis or measurement process. Data dependencies are directly visible in the underlying workspace concept. An integrated scripting language ("STUPSLANG") even puts the user in a position to freely add new analysis procedures or customize existing ones.

	For more information, latest version and download link see [[http://www.picoquant.com/products/category/software/symphotime-64-fluorescence-lifetime-imaging-and-correlation-software\|SymPhoTime64]].		For more information, latest version and download link see [[http://www.picoquant.com/products/category/software/symphotime-64-fluorescence-lifetime-imaging-and-correlation-software\|SymPhoTime64]].

dokuwiki

Anonymous (anonymous@undisclosed.example.com) — 2026-04-23T08:17:27+00:00

2026/04/23 20:33	current
Line 1:	Line 1:
	+	====== DokuWiki ======
	+
	+	[[doku>wiki:dokuwiki\|{{wiki:dokuwiki-128.png }}]] DokuWiki is a simple to use and highly versatile Open Source [[wp>wiki]] software that doesn't require a database. It is loved by users for its clean and readable [[wiki:syntax]]. The ease of maintenance, backup and integration makes it an administrator's favorite. Built in [[doku>acl\|access controls]] and [[doku>auth\|authentication connectors]] make DokuWiki especially useful in the enterprise context and the large number of [[doku>plugins]] contributed by its vibrant community allow for a broad range of use cases beyond a traditional wiki.
	+
	+	Read the [[doku>manual\|DokuWiki Manual]] to unleash the full power of DokuWiki.
	+
	+	===== Download =====
	+
	+	DokuWiki is available at https://download.dokuwiki.org/
	+
	+
	+	===== Read More =====
	+
	+	All documentation and additional information besides the [[syntax\|syntax description]] is maintained in the DokuWiki at [[doku>\|www.dokuwiki.org]].
	+
	+	About DokuWiki
	+
	+	* [[doku>features\|A feature list]] :!:
	+	* [[doku>users\|Happy Users]]
	+	* [[doku>press\|Who wrote about it]]
	+	* [[doku>blogroll\|What Bloggers think]]
	+	* [[https://www.wikimatrix.org/show/DokuWiki\|Compare it with other wiki software]]
	+
	+	Installing DokuWiki
	+
	+	* [[doku>requirements\|System Requirements]]
	+	* [[https://download.dokuwiki.org/\|Download DokuWiki]] :!:
	+	* [[doku>changes\|Change Log]]
	+	* [[doku>Install\|How to install or upgrade]] :!:
	+	* [[doku>config\|Configuration]]
	+
	+	Using DokuWiki
	+
	+	* [[doku>syntax\|Wiki Syntax]]
	+	* [[doku>manual\|The manual]] :!:
	+	* [[doku>FAQ\|Frequently Asked Questions (FAQ)]]
	+	* [[doku>glossary\|Glossary]]
	+
	+	Customizing DokuWiki
	+
	+	* [[doku>tips\|Tips and Tricks]]
	+	* [[doku>Template\|How to create and use templates]]
	+	* [[doku>plugins\|Installing plugins]]
	+	* [[doku>development\|Development Resources]]
	+
	+	DokuWiki Feedback and Community
	+
	+	* [[doku>newsletter\|Subscribe to the newsletter]] :!:
	+	* [[doku>mailinglist\|Join the mailing list]]
	+	* [[https://forum.dokuwiki.org\|Check out the user forum]]
	+	* [[doku>irc\|Talk to other users in the IRC channel]]
	+	* [[https://github.com/splitbrain/dokuwiki/issues\|Submit bugs and feature wishes]]
	+	* [[doku>thanks\|Some humble thanks]]
	+
	+
	+	===== Copyright =====
	+
	+	2004-2020 (c) Andreas Gohr <andi@splitbrain.org>((Please do not contact me for help and support -- use the [[doku>mailinglist]] or [[https://forum.dokuwiki.org\|forum]] instead)) and the DokuWiki Community
	+
	+	The DokuWiki engine is licensed under [[https://www.gnu.org/licenses/gpl.html\|GNU General Public License]] Version 2. If you use DokuWiki in your company, consider [[doku>donate\|donating]] a few bucks ;-).
	+
	+	Not sure what this means? See the [[doku>faq:license\|FAQ on the Licenses]].

2026/04/23 20:33	current
Line 1:	Line 1:
	+	====== DokuWiki ======
	+
	+	[[doku>wiki:dokuwiki\|{{wiki:dokuwiki-128.png }}]] DokuWiki is a simple to use and highly versatile Open Source [[wp>wiki]] software that doesn't require a database. It is loved by users for its clean and readable [[wiki:syntax]]. The ease of maintenance, backup and integration makes it an administrator's favorite. Built in [[doku>acl\|access controls]] and [[doku>auth\|authentication connectors]] make DokuWiki especially useful in the enterprise context and the large number of [[doku>plugins]] contributed by its vibrant community allow for a broad range of use cases beyond a traditional wiki.
	+
	+	Read the [[doku>manual\|DokuWiki Manual]] to unleash the full power of DokuWiki.
	+
	+	===== Download =====
	+
	+	DokuWiki is available at https://download.dokuwiki.org/
	+
	+
	+	===== Read More =====
	+
	+	All documentation and additional information besides the [[syntax\|syntax description]] is maintained in the DokuWiki at [[doku>\|www.dokuwiki.org]].
	+
	+	About DokuWiki
	+
	+	* [[doku>features\|A feature list]] :!:
	+	* [[doku>users\|Happy Users]]
	+	* [[doku>press\|Who wrote about it]]
	+	* [[doku>blogroll\|What Bloggers think]]
	+	* [[https://www.wikimatrix.org/show/DokuWiki\|Compare it with other wiki software]]
	+
	+	Installing DokuWiki
	+
	+	* [[doku>requirements\|System Requirements]]
	+	* [[https://download.dokuwiki.org/\|Download DokuWiki]] :!:
	+	* [[doku>changes\|Change Log]]
	+	* [[doku>Install\|How to install or upgrade]] :!:
	+	* [[doku>config\|Configuration]]
	+
	+	Using DokuWiki
	+
	+	* [[doku>syntax\|Wiki Syntax]]
	+	* [[doku>manual\|The manual]] :!:
	+	* [[doku>FAQ\|Frequently Asked Questions (FAQ)]]
	+	* [[doku>glossary\|Glossary]]
	+
	+	Customizing DokuWiki
	+
	+	* [[doku>tips\|Tips and Tricks]]
	+	* [[doku>Template\|How to create and use templates]]
	+	* [[doku>plugins\|Installing plugins]]
	+	* [[doku>development\|Development Resources]]
	+
	+	DokuWiki Feedback and Community
	+
	+	* [[doku>newsletter\|Subscribe to the newsletter]] :!:
	+	* [[doku>mailinglist\|Join the mailing list]]
	+	* [[https://forum.dokuwiki.org\|Check out the user forum]]
	+	* [[doku>irc\|Talk to other users in the IRC channel]]
	+	* [[https://github.com/splitbrain/dokuwiki/issues\|Submit bugs and feature wishes]]
	+	* [[doku>thanks\|Some humble thanks]]
	+
	+
	+	===== Copyright =====
	+
	+	2004-2020 (c) Andreas Gohr <andi@splitbrain.org>((Please do not contact me for help and support -- use the [[doku>mailinglist]] or [[https://forum.dokuwiki.org\|forum]] instead)) and the DokuWiki Community
	+
	+	The DokuWiki engine is licensed under [[https://www.gnu.org/licenses/gpl.html\|GNU General Public License]] Version 2. If you use DokuWiki in your company, consider [[doku>donate\|donating]] a few bucks ;-).
	+
	+	Not sure what this means? See the [[doku>faq:license\|FAQ on the Licenses]].