Time-Resolved Fluorescence Wiki

supported_mt200_pc_configuration_for_symphotime_32

Anonymous (anonymous@undisclosed.example.com) — 2016-08-25T11:24:41+00:00

2015/10/28 10:37		current
Line 1:		Line 1:
-	{{tag> SymPhoTime MT200 MicroTime SPT32}}	+	{{tag> SymPhoTime MT200 MicroTime SPT32 PC}}
	~~TOC~~		~~TOC~~

syntax

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

2026/04/23 18:41	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~~

supported_mt200_pc_configuration_for_symphotime_64

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

2023/02/17 13:44		current
Line 1:		Line 1:
-	{{tag>SymPhoTime MicroTime200 MicroTime100 Scanner PI Physik_Instrumente E725 E710 MadCityLabs Mad_City_Labs PC}}	+	{{tag>SymPhoTime MicroTime200 Scanner PI Physik_Instrumente E725 E710 MadCityLabs Mad_City_Labs PC}}
	~~TOC~~		~~TOC~~

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 ======

configuring_symphotime64_after_installation

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

2015/01/22 16:45		current
Line 1:		Line 1:
-		+	{{tag> SymPhoTime software howto}}
-	{{tag> SPT64 SymPhoTime software howto}}	+
	~~TOC~~		~~TOC~~
	====== Configuring SymPhoTime64 ======		====== Configuring SymPhoTime64 ======

start

Anonymous (anonymous@undisclosed.example.com) — 2021-06-17T14:47:30+00:00

2020/05/04 14:11		current
Line 11:		Line 11:


-	<WRAP center round box 60%>
-	===== News from the community=====
-	* 29.04.20 [[https://www.fret.community/announcement-protein-folding-and-dynamics-webinar/\|Protein folding and dynamics Webinar-Series.]]
-	* 14.04.20 [[https://analyticalscience.wiley.com/do/10.1002/was.00050003/full/bioimagedataanalysis.pdf\|Bioimage Data Analysis.]] New Expanded version of a nice open-source introduction. \\ \\
-	* 14.04.20 [[https://science.sciencemag.org/content/368/6486/78\|De novo design of protein logic gates.]] Exciting fundamental enzymology work. Chen et al. describe the design of logic gates that can regulate protein association. \\ \\
-
-
-
-	[[general:community_news\|...see more...]]
-	</WRAP>

tcspc_external_markers

Anonymous (anonymous@undisclosed.example.com) — 2020-09-14T16:01:28+00:00

2020/09/14 18:01		current
Line 31:		Line 31:
	* PI Controller: E725		* PI Controller: E725
	* PI Controller: E710 \\		* PI Controller: E710 \\
-	* Controller: E727 \\	+	* PI Controller: E727 \\
	* Controller: C867.2U2 (PI wide range scanner)		* Controller: C867.2U2 (PI wide range scanner)
	* Controller: C867.262 (PI wide range scanner)		* Controller: C867.262 (PI wide range scanner)

support_plane_analysis

Anonymous (anonymous@undisclosed.example.com) — 2014-01-21T16:46:58+00:00

2014/01/21 17:46		current
Line 13:		Line 13:
	===== References =====		===== References =====

-	Lakowicz JR (1999)// Principles of Fluorescence Spectroscopy//, 2nd edn. Kluver Academic/Plenum Publishers, New York (available in room C202)*	+	*Lakowicz JR (1999)// Principles of Fluorescence Spectroscopy//, 2nd edn. Kluver Academic/Plenum Publishers, New York

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]]

welcome

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

2026/04/23 18:41	current
Line 1:	Line 1:
	+	====== Welcome to your new DokuWiki ======
	+
	+	Congratulations, your wiki is now up and running. Here are a few more tips to get you started.
	+
	+	Enjoy your work with DokuWiki,\\
	+	-- the developers
	+
	+	===== Create your first pages =====
	+
	+	Your wiki needs to have a start page. As long as it doesn't exist, this link will be red: [[:start]].
	+
	+	Go on, follow that link and create the page. If you need help with using the syntax you can always refer to the [[wiki:syntax\|syntax page]].
	+
	+	You might also want to use a sidebar. To create it, just edit the [[:sidebar]] page. Everything in that page will be shown in a margin column on the side. Read our [[doku>faq:sidebar\|FAQ on sidebars]] to learn more.
	+
	+	Please be aware that not all templates support sidebars.
	+
	+	===== Customize your Wiki =====
	+
	+	Once you're comfortable with creating and editing pages you might want to have a look at the [[this>doku.php?do=admin&page=config\|configuration settings]] (be sure to login as superuser first).
	+
	+	You may also want to see what [[doku>plugins\|plugins]] and [[doku>templates\|templates]] are available at DokuWiki.org to extend the functionality and looks of your DokuWiki installation.
	+
	+	===== Join the Community =====
	+
	+	DokuWiki is an Open Source project that thrives through user contributions. A good way to stay informed on what's going on and to get useful tips in using DokuWiki is subscribing to the [[doku>newsletter]].
	+
	+	The [[https://forum.dokuwiki.org\|DokuWiki User Forum]] is an excellent way to get in contact with other DokuWiki users and is just one of the many ways to get [[doku>faq:support\|support]].
	+
	+	Of course we'd be more than happy to have you [[doku>teams:getting_involved\|getting involved]] with DokuWiki.

how_to_reinstall_symphotime

Anonymous (anonymous@undisclosed.example.com) — 2025-04-09T10:56:18+00:00

2025/04/09 12:55		current
Line 3:		Line 3:

	Updating from Windows 10 to Windows 11 should work smoothly, and all software should stay as it is. However it is a good idea to back-up the files mentioned below.		Updating from Windows 10 to Windows 11 should work smoothly, and all software should stay as it is. However it is a good idea to back-up the files mentioned below.
		+
	Please note: The Framegrabber MOU camera is not compatible with Windows 11 Windows 11 works with the newer USB MOU camera.		Please note: The Framegrabber MOU camera is not compatible with Windows 11 Windows 11 works with the newer USB MOU camera.
	==== Getting everything from the old computer ====		==== Getting everything from the old computer ====

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~~

asymptotic_standard_errors

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

2014/04/09 22:41		current
Line 5:		Line 5:
	The asymptotic standard errors (ASE) are used for analyzing fitting parameter error intervals. For illustration let's start at the best fit parameter set, which can be regarded as a single point in the parameter space. Now we remove the parameter for which we want to calculate the error intervals from this location, that is, we take a single step parallel to its parameter axis. We then calculate the reduced X<sup>2</sup> for this new paramter set. By iterating this procedure we get X<sup>2</sup> as a function of the parameter of interest. The intersection points of this function with a given X<sup>2</sup> confidence limit define the boundaries of the confidence interval of the parameter.		The asymptotic standard errors (ASE) are used for analyzing fitting parameter error intervals. For illustration let's start at the best fit parameter set, which can be regarded as a single point in the parameter space. Now we remove the parameter for which we want to calculate the error intervals from this location, that is, we take a single step parallel to its parameter axis. We then calculate the reduced X<sup>2</sup> for this new paramter set. By iterating this procedure we get X<sup>2</sup> as a function of the parameter of interest. The intersection points of this function with a given X<sup>2</sup> confidence limit define the boundaries of the confidence interval of the parameter.

-	At PQ the asymptotic standard errors are supported by [[products:FluoFit]] and the [[products:SymPhoTime]] software.	+	At PQ the asymptotic standard errors are supported by [[software:FluoFit]] and the [[software:SymPhoTime]] software.

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.

exchange_dichroic_mt200

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

2021/06/25 11:19		current
Line 1:		Line 1:
-		+	{{tag>howto MicroTime200 dichroic microscopy}}
-	{{tag>howto MicroTime200 dichroic microscopy MT200}}	+

	====== How to exchange the main dichroic of the MicroTime 200 ======		====== How to exchange the main dichroic of the MicroTime 200 ======

supported_th260_pc

Anonymous (anonymous@undisclosed.example.com) — 2017-09-20T15:42:57+00:00

2017/07/24 10:03		current
Line 1:		Line 1:
		+	/*
	{{tag> PC TH260 Harps TCSPC}}		{{tag> PC TH260 Harps TCSPC}}
	~~TOC~~		~~TOC~~
Line 37:		Line 38:
	\|HP ENVY 700-056 \|AMD A75 FCH\| \|		\|HP ENVY 700-056 \|AMD A75 FCH\| \|
	\|Dell Precision T3400 \|Intel X38 \| Installed in SLOT 3 , PCIe 8x(4,1)\|		\|Dell Precision T3400 \|Intel X38 \| Installed in SLOT 3 , PCIe 8x(4,1)\|
		+	\|Dell Optiplex 990 \|Intel X38 \| PCIe 8x \| /* See ticket 828080*\

	===== not-working mainboards / computer =====		===== not-working mainboards / computer =====
Line 48:		Line 50:
	\|HP 200-G1 (Model L5L54US#ABA) \| \| \|		\|HP 200-G1 (Model L5L54US#ABA) \| \| \|
	\|Lenovo ThinkServer TS140 \| \| \|		\|Lenovo ThinkServer TS140 \| \| \|
		+
		+	*/

bifl

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

2014/04/09 22:38		current
Line 3:		Line 3:
	BIFL stands for Burst Integrated Fluorescence Lifetime: The photon events of a complete burst are accumulated into a [[TCSPC]] histogram which is used for lifetime analysis methods afterwards. Usually a burst is defined as a time interval for which the intensity of a time trace or [[MCS]] measurement is above a chosen threshold. Evaluation of all bursts present in an [[MCS]] trace, for example, results in a lifetime histogram.		BIFL stands for Burst Integrated Fluorescence Lifetime: The photon events of a complete burst are accumulated into a [[TCSPC]] histogram which is used for lifetime analysis methods afterwards. Usually a burst is defined as a time interval for which the intensity of a time trace or [[MCS]] measurement is above a chosen threshold. Evaluation of all bursts present in an [[MCS]] trace, for example, results in a lifetime histogram.

-	BIFL is supported by the [[products:SymPhoTime]] software, alongside with a variety of burst related techniques.	+	BIFL is supported by the [[software:SymPhoTime]] software, alongside with a variety of burst related techniques.

bootstrap

Anonymous (anonymous@undisclosed.example.com) — 2014-01-21T16:41:23+00:00

2014/01/21 17:41		current
Line 4:		Line 4:

	Specifically, the bootstrap analysis takes a subset of N randomly chosen points out of the experimental data set, which itself consists of N data points. Since the points are chosen randomly, some of the points will be selected more than once; others will not be selected at all. Thus the 'simulated' data set is not identical to the original one, while the statistical properties of the original data set are maintained (since the number of data points remains the same).		Specifically, the bootstrap analysis takes a subset of N randomly chosen points out of the experimental data set, which itself consists of N data points. Since the points are chosen randomly, some of the points will be selected more than once; others will not be selected at all. Thus the 'simulated' data set is not identical to the original one, while the statistical properties of the original data set are maintained (since the number of data points remains the same).
-
-	At PQ the bootstrap method is exclusively used in [[FluoFit]]. For ensemble fitting as in [[FLIM]] it is -alas!- way too slow.
-

	===== Advantages and disadvantages =====		===== Advantages and disadvantages =====

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]]
-

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 =====

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 =====

easytau

Anonymous (anonymous@undisclosed.example.com) — 2016-03-01T09:41:03+00:00

2016/03/01 10:40		current
Line 10:		Line 10:
	The easiest way to start with scripting measurements in EasyTau is to acquire a measurement with a wizard and then create a script from this measurement.		The easiest way to start with scripting measurements in EasyTau is to acquire a measurement with a wizard and then create a script from this measurement.

-	- Create a data set using a wizard of your choice	+	* Create a data set using a wizard of your choice
-	- Right click on the data set	+	* Right click on the data set
-	- Select ''Transfer script to customised mode, script page''	+	* Select ''Transfer script to customised mode, script page''
	{{ :software:create_script.png?600 \|}}		{{ :software:create_script.png?600 \|}}
-	- Adjust to your liking	+	* Adjust to your liking

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 ======

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]].

supported_mt200_pc_configuration_for_symphotime_32

Anonymous (anonymous@undisclosed.example.com) — 2014-05-23T07:36:46+00:00

2026/04/23 18:41		current
Line 1:		Line 1:
		+	This page is redirected to [[:software:supported_mt200_pc_configuration_for_symphotime_32]].

supported_mt200_pc_configuration_for_symphotime_64

Anonymous (anonymous@undisclosed.example.com) — 2014-05-23T07:33:10+00:00

2026/04/23 18:41		current
Line 1:		Line 1:
		+	This page is redirected to [[:software:supported_mt200_pc_configuration_for_symphotime_64]].

dokuwiki

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

2026/04/23 18:41	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]].

old_dongles_drivers_for_fluofit_symphotime_32

Anonymous (anonymous@undisclosed.example.com) — 2025-03-14T10:04:27+00:00

2025/03/14 11:02		current
Line 40:		Line 40:
	Our team successfully tested this setup using VMware Workstation Player 15.5.1, where both FluoFit and SPT32 dongles worked on an emulated Windows 7 (x64). Consider the following points:		Our team successfully tested this setup using VMware Workstation Player 15.5.1, where both FluoFit and SPT32 dongles worked on an emulated Windows 7 (x64). Consider the following points:

-	You will need valid licenses for both Windows 10/8 (host system) and Windows 7 (guest system).	+	You will need valid licenses for both newer Windows version (host system) and Windows 7 (guest system).

	VMware Workstation Player is free for non-commercial use, but the VM setup must be done by the user.		VMware Workstation Player is free for non-commercial use, but the VM setup must be done by the user.

2026/04/23 18:41	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]].