Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
M
MosaicSuite
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Sbalzarini Lab
Software
Bio-Imaging
MosaicSuite
Commits
da62c5e8
Commit
da62c5e8
authored
1 year ago
by
Krzysztof Gonciarz
Browse files
Options
Downloads
Patches
Plain Diff
Added info about running PT from macro (MSS, absolute value)
parent
0bd9db63
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/source/particleTrackerTutorial.rst
+18
-0
18 additions, 0 deletions
doc/source/particleTrackerTutorial.rst
with
18 additions
and
0 deletions
doc/source/particleTrackerTutorial.rst
+
18
−
0
View file @
da62c5e8
...
...
@@ -375,6 +375,24 @@ The expected columns are only: Frame, x, y, z. Optionally provided columns m0 an
Macros
======
How to run Particle Tracker from ImageJ macro
---------------------------------------------
Here are examples of run commands for Particle Tracker
.. code-block:: guess
run("Particle Tracker 2D/3D", "radius=3 cutoff=0.001 per/abs=0.501 link=2 displacement=10 dynamics=Brownian");
run("Particle Tracker 2D/3D", "radius=3 cutoff=0.001 per/abs=0.500 link=2 displacement=10 dynamics=Brownian saveMss");
run("Particle Tracker 2D/3D", "radius=3 cutoff=0.001 per/abs=50 absolute link=2 displacement=10 dynamics=Brownian");
While most parameters is self describing (same names as in Particle Trakcer dialog) here are exceptions:
1. **absolute** - add this argument to have 'Absolute' cutoff rather than percentile ('Absolute' checkbox)
#. **saveMss** - add this argument to save MSS to file (table that is accessible via "All MSS/MSD to Table' in GUI mode)
After running in macro mode ParticleTracker will save output files in same directory as input image file.
Postprocess "All Trajectories to Table"
---------------------------------------
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment