{"id":1463,"date":"2011-07-21T03:15:53","date_gmt":"2011-07-21T03:15:53","guid":{"rendered":"http:\/\/labrigger.com\/blog\/?p=1463"},"modified":"2011-07-18T12:16:06","modified_gmt":"2011-07-18T12:16:06","slug":"taro-tools-and-ppt-for-igor-pro","status":"publish","type":"post","link":"http:\/\/labrigger.com\/blog\/2011\/07\/21\/taro-tools-and-ppt-for-igor-pro\/","title":{"rendered":"Taro Tools and PPT for Igor Pro"},"content":{"rendered":"<p align=\"center\"><img decoding=\"async\" src=\"http:\/\/labrigger.com\/blog\/wp-content\/uploads\/2010\/11\/tarotools2.png\"><\/p>\n<p>Last Friday afternoon to Saturday morning I had a marathon data analysis session. It was almost completely in Igor Pro. I used <a href=\"https:\/\/sites.google.com\/site\/tarotoolsregister\/\">TaroTools<\/a> so heavily that I dropped Taro another thank you note. It&#8217;s really saved me so much programming and analysis time. I highly recommend checking it out. Prof. Ishikawa keeps it up to date (last update, May 2011), so it&#8217;s not abandonware.<\/p>\n<p>The <a href=\"http:\/\/labrigger.com\/blog\/2010\/11\/24\/igor-pro-and-electrophysiology\/\">last time Labrigger covered Igor Pro software for electrophysiology<\/a>, <a href=\"https:\/\/sites.google.com\/site\/tarotoolsregister\/\">TaroTools<\/a>, <a href=\"http:\/\/www.neuromatic.thinkrandom.com\/index.html\">Neuromatic<\/a> (last update was in 2008, but it has aged fine and is still very handy), and <a href=\"http:\/\/www.mpibpc.mpg.de\/groups\/neher\/index.php?page=software\">PPT<\/a> were all mentioned. However, there weren&#8217;t any PPT screenshots, nor was there much information. In this post, I&#8217;ll highlight it in a bit more detail.<\/p>\n<p>PPT (Patcher&#8217;s Power Tools) was developed in Neher&#8217;s lab (<a href=\"http:\/\/www.mpibpc.mpg.de\/groups\/neher\/index.php?page=software\">download<\/a>, <a href=\"http:\/\/www.mpibpc.mpg.de\/groups\/neher\/index.php?page=aboutppt\">about<\/a>). It&#8217;s development has perhaps slowed, but is still regularly updated (last update was March 2011). After installing, it adds a PPT menu to the Igor menu bar.<\/p>\n<p align=\"center\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/labrigger.com\/blog\/wp-content\/uploads\/2011\/07\/ppt0.png\" alt=\"\" title=\"PPT main menu\" width=\"220\" height=\"270\" class=\"aligncenter size-full wp-image-1464\" \/><\/p>\n<p>As you can see, it&#8217;s built to load in HEKA data files, but the later entries are very general purpose. &#8220;Wave Statistics&#8221;, despite the similarity in name, is actually not like the native command <em>WaveStats<\/em> at all. It&#8217;s actually a very fast and easy-to-use wave average function. Feed in some waves, and get the mean, SD, and SEM out.<\/p>\n<p>&#8220;Plot Waves&#8221; plots selected waves, but instead of Igor Pro&#8217;s default plotting with all the waves sharing the same y-axis, each wave is plotted on a separate y-axis, stacked vertically, against the same x-axis. &#8220;Slim Waves&#8221; downsamples waves, which I&#8217;ve learned is very important for making nice looking figures. If you have several seconds of data sampled at 50 kHz and then shrink it down to just an inch wide, you quickly run into resolution limits and data points that should be right next to each other end up on top of each other. Here&#8217;s what it looks like:<\/p>\n<p align=\"center\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/labrigger.com\/blog\/wp-content\/uploads\/2011\/07\/ds_z1.png\" alt=\"\" title=\"Top trace is the source sampled at 50 kHz. The bottom trace is the same data downsampled 10-fold. Note the improved appearance of the bottom trace.\" width=\"519\" height=\"369\" class=\"aligncenter size-full wp-image-1474\" srcset=\"http:\/\/labrigger.com\/blog\/wp-content\/uploads\/2011\/07\/ds_z1.png 519w, http:\/\/labrigger.com\/blog\/wp-content\/uploads\/2011\/07\/ds_z1-300x213.png 300w\" sizes=\"auto, (max-width: 519px) 100vw, 519px\" \/><\/p>\n<p>The top trace is at full resolution: 50 kHz sampling. The trace below it is down sampled 10-fold. Note that the non-downsampled trace looks strange and hairy. Now zoom in some more and select the traces.<\/p>\n<p align=\"center\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/labrigger.com\/blog\/wp-content\/uploads\/2011\/07\/ds_z2.png\" alt=\"\" title=\"Top trace is the source sampled at 50 kHz. The bottom trace is the same data downsampled 10-fold. Note that multiple datapoints in the top trace share the same x-location. This artifact does not happen in the downsampled trace.\" width=\"550\" height=\"539\" class=\"aligncenter size-full wp-image-1475\" srcset=\"http:\/\/labrigger.com\/blog\/wp-content\/uploads\/2011\/07\/ds_z2.png 550w, http:\/\/labrigger.com\/blog\/wp-content\/uploads\/2011\/07\/ds_z2-300x294.png 300w\" sizes=\"auto, (max-width: 550px) 100vw, 550px\" \/><\/p>\n<p>Note that the non-downsampled trace (top) has sample points sharing the same x-coordinate. This is because we&#8217;ve run into resolution limits. The downsampled trace looks fine. Downsampling is important for figure presentation not only because it makes the traces look nicer, but it makes the PDFs load faster too. If you ever grow annoyed at how long it takes your PDF reader to draw a figure with traces, it&#8217;s because the authors didn&#8217;t down sample when they should have. I&#8217;ve seen PDFs from journals that are over 30MB. BTW- the traces can easily be extracted from the PDF. So in way, it&#8217;s an inadvertent combination of publishing and data-sharing.<\/p>\n<p>The next four entries on the PPT menu are all very handy calculators. <\/p>\n<p align=\"center\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/labrigger.com\/blog\/wp-content\/uploads\/2011\/07\/ppt1.png\" alt=\"\" title=\"PPT&#039;s Patcher&#039;s Calculator\" width=\"363\" height=\"323\" class=\"aligncenter size-full wp-image-1465\" srcset=\"http:\/\/labrigger.com\/blog\/wp-content\/uploads\/2011\/07\/ppt1.png 363w, http:\/\/labrigger.com\/blog\/wp-content\/uploads\/2011\/07\/ppt1-300x266.png 300w\" sizes=\"auto, (max-width: 363px) 100vw, 363px\" \/><\/p>\n<p>A calculator for reversal potentials.<\/p>\n<p align=\"center\"><img loading=\"lazy\" decoding=\"async\" src=\"http:\/\/labrigger.com\/blog\/wp-content\/uploads\/2011\/07\/ppt2.png\" alt=\"\" title=\"PPT&#039;s Liquid Junction Potential calculator\" width=\"609\" height=\"557\" class=\"aligncenter size-full wp-image-1466\" srcset=\"http:\/\/labrigger.com\/blog\/wp-content\/uploads\/2011\/07\/ppt2.png 609w, http:\/\/labrigger.com\/blog\/wp-content\/uploads\/2011\/07\/ppt2-300x274.png 300w\" sizes=\"auto, (max-width: 609px) 100vw, 609px\" \/><\/p>\n<p>And here&#8217;s one for computing the liquid junction potential.<\/p>\n<p>There&#8217;s more too. In addition to the calcium imaging tools seen in the PPT menu above, there are also  utilities for Boltzmann fits, dose-response curves, Fura calibration, and more. All in all, this is a really handy set of utilities to have around. Even if you don&#8217;t typically use Igor Pro for analysis, PPT, NeuroMatic, and TaroTools may be handy enough to justify having a copy.<\/p>\n","protected":false},"excerpt":{"rendered":"<p align=\"center\">\n<p>Last Friday afternoon to Saturday morning I had a marathon data analysis session. It was almost completely in Igor Pro. I used <a href=\"https:\/\/sites.google.com\/site\/tarotoolsregister\/\">TaroTools<\/a> so heavily that I dropped Taro another thank you note. It&#8217;s really saved me so much programming and analysis time. I highly recommend checking it out. Prof. Ishikawa&#8230;<\/p>\n<div class=\"read-more\"><a href=\"http:\/\/labrigger.com\/blog\/2011\/07\/21\/taro-tools-and-ppt-for-igor-pro\/\">Read More<\/a><\/div><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[25,28],"class_list":["post-1463","post","type-post","status-publish","format-standard","hentry","category-software","tag-analysis","tag-electrophysiology"],"_links":{"self":[{"href":"http:\/\/labrigger.com\/blog\/wp-json\/wp\/v2\/posts\/1463","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/labrigger.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/labrigger.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/labrigger.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/labrigger.com\/blog\/wp-json\/wp\/v2\/comments?post=1463"}],"version-history":[{"count":11,"href":"http:\/\/labrigger.com\/blog\/wp-json\/wp\/v2\/posts\/1463\/revisions"}],"predecessor-version":[{"id":1479,"href":"http:\/\/labrigger.com\/blog\/wp-json\/wp\/v2\/posts\/1463\/revisions\/1479"}],"wp:attachment":[{"href":"http:\/\/labrigger.com\/blog\/wp-json\/wp\/v2\/media?parent=1463"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/labrigger.com\/blog\/wp-json\/wp\/v2\/categories?post=1463"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/labrigger.com\/blog\/wp-json\/wp\/v2\/tags?post=1463"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}