Size: 851.73 KB
md5_file hash: 3d3a2feb2d49960b8c6c6b7410351ad1
First released: May 8, 2013 - 16:44
Last updated: May 14, 2013 - 17:00
GUIPHist and GUIPControls have been tested, and are in a fairly stable format. The help file sections on these is pretty much complete.
Size: 108.96 KB
md5_file hash: 52e53c4742f014ec3a056a7aa9885e3e
First released: October 7, 2011 - 03:56
This version fixes the following bug: the calculation of the 20-80% rise time was failing when the event rise time was one point only (which happens for example when detecting recorded trigger signals such as TTLs).
Now a separate calculation of RT20 and RT80 is performed when a one point transition accounts for more than 99% of the event amplitude.
Size: 109.34 KB
md5_file hash: cdc6172582027ea2efaafd6fb2710375
First released: September 21, 2010 - 08:14
Last updated: September 21, 2010 - 08:14
Changelog of version 1.05:
* This version focuses on saving/loading analysis independently of IGOR's experiments. It is now possible to save an analysis on the disk and to recall it later. In the files which are saved, IGOR puts everything it needs to recapitulate the same detection using the same traces and apply the same tags and tag labels (see below).
Size: 97.38 KB
md5_file hash: 26dcbcbf7e4c60a47e327a0bfd0766a4
First released: June 25, 2010 - 03:04
This new version comes with a number of new features. Here is the detailed changelog:
1. A long awaited function is finally implemented: an automatic fit (double exponential) of the decay of all tagged events. As the other fit functions, this new function is intended to be used with postsynaptic currents. It is launched using the "Fit all events" button in the "Kin." tab of the window DetectedEvents. It is necessary to calculate the average event first, since the function will use the fit parameters of the average as a first guess for individual events.
Use the function below to parse a string like one of the following into seconds:
If you have a date-time string and wish to parse it into seconds, use the Parse Date,Time and Date/Time Strings snippet.
To represent midnight (the beginning of a day), use
12:00:00 AM. Using
24:00:00 to represent midnight will not produce any kind of error, however the function will return 86400 seconds, which is probably not the result you expect.
Calculates histogram of facet slopes in atomic force microscopy (AFM) images. See Surface and Interface Analysis 25 (1997) 74.Posted April 15th, 2010 by clperkins
//Calculates a histogram of slopes of facets in AFM images. See Chatelier et al. in Surface and Interface Analysis 25 (1997) 741. //Similar to the output of Gwyddion image analysis software after selecting Data Process-->Statistics -->Slope Distribution --> Inclination (theta) //Assumes that the AFM image has been plane filtered, is loaded into a 2D wave, and has heights in nanometers Function slope_freq(w1) wave w1 variable X_index, Y_index, totalcycles=0, array_size, mini_wave_scaling=1
This is of interest to XOP function writers who have to parse string inputs.
If you have a function in an XOP that takes as a parameter a string containing a wave name or a full path to a wave (data folder path:wave name), the ParseWavePath function will help you parse the input into C strings containing wave name and data folder name.
The ParseWaveListPaths takes a a semicolon- or comma-separated list of wavenames or full paths to waves and returns an array of waveHandles.
Size: 51.03 KB
md5_file hash: 7e315778dea79a558f9d3a5e2470443a
First released: February 2, 2010 - 16:48
This is the alpha release. Probably useful only for people experienced both in Igor and with LaTeX. Pending interest in this project, further releases for a wider audience can be considered. Help from MacOS people for a cross-platform version would be greatly appreciated - contact me if you're interested in helping out.
Size: 9.13 KB
md5_file hash: 0c8b80d2de2bac5cdb104cee0c688e3a
First released: December 11, 2009 - 13:05
Last updated: December 11, 2009 - 13:05
Sometimes it is a hard learning curve to add an external window to an XOP. The WindowXOP example supplied in the XOP toolkit is great, but still takes a while to grok.
I was experimenting with Interface Builder as a way to add a window to an XOP. The XOP is responsible for opening and closing the window - IGOR doesn't know about it - and I destroy the window before control returns to IGOR. The attached files show the code that was created using Interface Builder and the C-code required in an XOP to display the window and update it, by drawing text in it.