Only data about the GDSC plugin names were sent. No data currently open in ImageJ was sent. There is no information that uniquely identifies a person. No personal information was transmitted to Google. Each time a GDSC plugin was executed this event was recorded as if a user viewed a web page. The ImageJ instance acted as the web browser client. The code identified each plugin as a page. Usage data was collected as if performing anonymous tracking of web page views by a web browser. The information about use of the plugins was transmitted to and stored by Google on servers in the United States. To track usage we used Google Analytics, a web analytics service provided by Google, Inc. Thus we will continue to publish all plugins we develop in the hope that they are useful. It also showed that some plugins we do not regularly use in GDSC research work had an uptake of users in the community. Tracking provided us with usage numbers to add to research grant applications for work that included the GDSC software. You had to opt-in and could opt-out at any time. To understand how the GDSC SMLM plugins were being used around the world we previously added some code to track usage. What computer platform and software do we need to support? What plugins are frequently used together, and in what order? How many times people use different plugins in one ImageJ analysis session? How often people update to the latest version? Example questions that can be answered are: In the context of ImageJ plugins it would help to improve the plugins. Tracking allows a provider to understand its user base. It was a useful facility but non-essential we are grateful to those who participated. If your usage was tracked in a previous version then this was only because you provided consent (and after being provided with similar information to that shown below). A key feature is that tracking was disabled by default and had to be enabled. Tracking had to be enabled via a dialog in a similar way to a user preferences pop-up dialog in a web browser. It is maintained to describe what and how anonymous user tracking was performed. This section details the tracking code that was used in a previous version. No tracking is performed by the GDSC plugins. Plugins for Pair Correlation (PC) analysis.Įstimate PSF widths and allow calibration of the imaging camera noise and gain.įor install of the SMLM Toolset and configuration of the SMLM Tools window. Perform analysis on localisations for example blinking rate estimation, molecule tracing and Fourier image resolution. Results can be filtered to subsets and compared to a reference set, e.g. The plugins have been divided into the following sub-sets:įor identification of localisations on an image.Īllow loading and saving results in different formats. For example it is possible to read the following file formats for analysis: The localisations do not have to be computed by the SMLM fitting plugins and can be generated by another program. The plugins used to analyse a set of localisations only require that the localisations be loaded into memory. Tracing of fluorophore molecules through time Reconstructing an image from the list of localisationsĪnalysis of the blinking rate of fluorophores The various ImageJ plugins allow the processing of single-molecule light microscopy images and analysis of the results.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |