Skip to content

Commit

Permalink
Merge pull request #30 from melvingelbard/main
Browse files Browse the repository at this point in the history
Added filter param to Measurement Exporter
  • Loading branch information
petebankhead committed Oct 19, 2021
2 parents aff6805 + ff7fa1e commit 565eb5e
Showing 1 changed file with 4 additions and 3 deletions.
7 changes: 4 additions & 3 deletions docs/tutorials/exporting_measurements.rst
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ There are 3 different ways to export measurements within QuPath, via:
Which one to use is up to you and depends on what you want to do.

.. note::

As a rule of thumb, if you have:

* **a single image**: use the measurement table
Expand All @@ -22,7 +22,7 @@ Which one to use is up to you and depends on what you want to do.
============
Step-by-step
============

Via the measurement table
=========================

Expand All @@ -43,7 +43,7 @@ After choosing the objects you wish to export (e.g. detections, annotations), a
You can then save your measurement by pressing **Save** and choosing an appropriate name for your output ``.txt`` file.

.. note::

This method creates a table with different columns, which all depend on the objects (and measurements) present in your image.

If your analysis involves combining measurements from different images, it is recommended to use the Measurement Exporter, detailed in the next subsection.
Expand Down Expand Up @@ -127,6 +127,7 @@ The following script demonstrates a standard pipeline for exporting cell measure
.separator(separator) // Character that separates values
.includeOnlyColumns(columnsToInclude) // Columns are case-sensitive
.exportType(exportType) // Type of objects to export
.filter(obj -> obj.getPathClass() == getPathClass("Tumor")) // Keep only objects with class 'Tumor'
.exportMeasurements(outputFile) // Start the export process
print "Done!"

0 comments on commit 565eb5e

Please sign in to comment.