FindPoints searches a data set for peaks which exceed a threshold set in terms of an estimate of the data's standard deviation and mean. You can instruct the search process to automatically lower this threshold until a minimum number of points is found. To further constrain the search, you can load polygon data (typically from EditPolygon) and either have FindPoints assemble the polygons into volumes (objects) of interest or load an old-style object list from VolumeBuilder.
Once FindPoints has identified the peaks, you can also have it use the peaks as the starting point for region growing or for measurements of the points' intensity and their interrelationships.
Overview | Image data | 3D objects | Process mode | Image windows | Statistics | Peak finding | Region growing | Submit to queue | Results | Looping | Defaults
Priism | EditPolygon | VolumeBuilder
FindPoints requires either a Priism image file or window to determine the intensity at each volume element. If you use an image window, you can add or delete points found or select objects of interest using the right mouse button. See the section on picking for more details.
You can set which two dimensional cross-sections of the data set are used with the Z, T, and W controls on the main FindPoints dialog. For the z direction and time, the controls show the first section used, the maximum possible value for the last section used, and the amount by which the section index is adjusted when moving to an adjacent section whose data is used. Toggles allow you to set which wavelengths are used.
Overview | Image data | 3D objects | Picking | Statistics | Peak finding | Region growing | Submit to queue | Results | Looping
You can constrain FindPoints' operations by specifying volumes of interest (objects). To do so, you need to supply FindPoints with polygon data that represents cross-sections through the volumes; this data can either be in a file or, if you are working with an image window, the polygon data that has already been loaded into that window. EditPolygon can be used to generate either of these sources of data.
After loading the polygon data, it needs to be assembled into volumes. FindPoints can do this assembling for you if you press the Create button. When you do so, FindPoints works through the sections examining polygons in nearby sections; based on the amount of overlapping area, it associates those polygons into volumes. To limit what FindPoints considers a nearby section, set the max z gap; i.e. if you use a gap of 1, a polygon from section six in z can not be associated with a polygon in section eight unless there is a polygon in section seven which can be associated with the polygon in section six and the one in section eight.
The other option for assembling the polygons into volumes is to enter a filename into the object file field. The polygon file must already be loaded before entering this file name. The object file is an an existing file which specifies how the polygons are grouped. VolumeBuilder can be used to generate this file (it must be in the old-style format).
Overview | Image data | 3D objects | Picking | Statistics | Peak finding | Region growing | Submit to queue | Results | Looping
There are three modes for analyzing data with FindPoints. This setting will affect what portion of the data set will be used for the histogram statistics, peak finding and region growing.
Entire Data Set : is always used when there are no 3D objects. it can also be used when the data is broken down into 3D objects and all of the objects are to be processed at once. If region growing is done in this mode, the output mask data for all the objects will be written out to one image file, the size of the original data set.
Separate Objects: also processes all the objects in one run, but in region growing, a separate output mask file is written out for each object. In this case, the names of the files are the entered name, plus "-num", where num is the number of the object. This mode is helpful in speeding up the run time when a huge file is being processed, since breaking it down into smaller regions for processing will take up less memory.
Current Object: when there are 3D objects, a single object can be viewed in the histogram and the best set of parameters can be determined on a small region before processing the rest of the objects. When in this mode, either enter the object to analyze in the Current Wave, Time, Obj field or use the mouse to select the object in the window. See Picking.
Overview | Image data | 3D objects | Picking | Statistics | Peak finding | Region growing | Submit to queue | Results | Looping
Select Object: when there are 3D Objects loaded, the current object can be selected by clicking inside the object. The current object is only meaningful when the process mode is set to current object. When the object is selected, the polygons will turn blue and the Current Wave, Time, Obj field should update to the current object.
delete pts: in this mode, existing points can be deleted by clicking on them with the mouse
add pts: Points can be manually selected with the mouse. When this is done, the peak intensity in the local region is found. The local region is defined in using the search range fields in the peak finding menu. The box size is (2x + 1) of the search range. The point is then refined to the local center of mass if the Point Pos pulldown in the peak finding menu is set to Local COM or Local COM - Background. See Peak finding for more info on how the local center of mass is calculated.
Overview | Image data | 3D objects | Image windows | Statistics | Peak finding | Region growing | Submit to queue | Results | Looping
The Histogram menu displays a histogram of the data being analyzed, and shows three bars. The red bar is located at the mean of the intensities. the pink bar shows where the regions growing threshold is currently set and the white bar shows where the peak finding threshold is. The peak finding and region growing bars can be dragged to the position that seems appropriate according to the histogram. The value is reported as both threshold and multiples of the standard deviation in the histogram menu. Thresholds in FindPoints are set based on an estimate of the mean and standard deviation for the volume of interest. Three different methods can be used to estimate the mean and standard deviation:
Overview | Image data | 3D objects | Picking | Statistics | Peak finding | Region growing | Submit to queue | Results | Looping
The automatic peak finding algorithm uses pixels above the threshold value as starting positions for a local search for peaks. The threshold value is entered as number of standard deviations, or absolute threshold, depending on the Method setting in the main menu.
Once the list of peaks is determined, there are several criteria used to refine this list:
Overview | Image data | 3D objects | Picking | Statistics | Peak finding | Region growing | Submit to queue | Results | Looping
Region Growing starts from the points found with the peak finding or entered points, and grows out through the data using one of the following criteria to determine where to stop:
To further limit how the region grows, you may specify the following:
After the regions are grown, those which contain fewer pixels than the value shown in the "min pixels to accept point" field will be rejected.
The region growing process may generate two image data sets (if you use the "Separate Objects" processing mode in the Find Points dialog it is two data sets per object; in this case, the data set names have a dash and the number of the object appended). If a file name or window number is entered in the "Out Mask (opt)" field, a data set with that name will be generated. In it, the pixels that belong to a region will have an intensity equal to the region's number (a positive integer); all other pixels will have an intensity of zero. If a file name or window number is entered in the "Out Data (opt)" field, a data set with that name will be generated. In it, the pixels that belong to a region will have the intensity value from the input data set; all other pixels will have an intensity of zero.
Overview | Image data | 3D objects | Picking | Statistics | Peak finding | Region growing | Submit to queue | Results | Looping
Once parameters are chosen for the peaks finding and region growing, the job can be submitted to queue. Currently, both peak finding and region growing are run when FindPoints is run in batch mode, and the result is written to a pick points format file.
Submit to queue - select the queue to run on; if "Write script only" is selected, the command and parameter files will be created but the calculations will not be started.
Command File - contains the environment setup and starts FindPoints with the parameter file, directing output print statements to a log file.
Parameter File - contains the parameters selected by the user for the current run.
Output Pick File - point information will go to this file.
Log file - contains parameters used and tracks progress of run
Overview | Image data | 3D objects | Picking | Statistics | Peak finding | Region growing | Submit to queue | Results | Looping
Save Pick Points Format - output in this format contains the following
information:
Wave Time
L BEAD # - 3DObject num. will be just 1 object if
no polygons used.
mean, standard deviation and threshold used for
this object
Point Info: x,y,z position, number, integrated intensity,
total npts in region grow
Load Pick Points Format - an existing point file can be loaded back into FindPoints
Pt Data in Columns, Save Point Info - these are old, and no longer supported
Show Point Info - a table of point info on the screen.
object num, point num, intensity.
table only show info for 20 points at a time so buttons at bottom
let you look through
all the points. top starts at the first object, first point.
next moves forward through the
list, and back move backward through the list.
Overview | Image data | 3D objects | Picking | Statistics | Peak finding | Region growing | Submit to queue | Results | Looping
Looping lets you quickly test a range of thresholds for peak finding and/or region growing to determine optimal parameters. The entire data set or one single object can be tested depending on the setting of the process mode pulldown in the main menu.
output pt list file - this is the name for the output pick points file. point positions and integrated intensities are reported in this file.
peak nstd start, inc - enter the starting multiple of the standard deviation to use as the threshold for peak finding and the increment multiple for the successive rounds. it makes the most sense to increment either the peak finding or the region growing but usually not both at the same time. set inc to zero to use the same peak finding threshold for each loop.
reg grow nstd start, inc - enter the starting multiple of the standard deviation to use as the threshold for region growing and the increment multiple for the successive rounds.
number of increments - the number of times to set a new threshold and run peak finding and region growing.
Get Looped - do it.
Overview | Image data | 3D objects | Picking | Statistics | Peak finding | Region growing | Submit to queue | Results | Looping
Load Defaults - loads the defaults parameters back in.
Overview | Image data | 3D objects | Picking | Statistics | Peak finding | Region growing | Submit to queue | Results | Looping