9.4. Marker Styles
Table of Contents
Marker types
Markers in ROOT are small symbols used to display individual data points on graphs and in some histogram styles. Choosing the right marker type makes your plots easier to read and interpret, especially when you compare several datasets on the same axes.
In ROOT, marker types are controlled by the marker style attribute, set with the method SetMarkerStyle(Int_t style). The style is an integer code that chooses which symbol is drawn at each point.
Some commonly used marker styles are summarized in the table below.
| Style code | Description | Typical use |
|---|---|---|
| 1 | No marker | Lines only, or invisible markers |
| 2 | Plus sign | Simple marker, good for dense points |
| 3 | Asterisk | Emphasized points, not too dense datasets |
| 4 | Small cross | Alternative to plus sign |
| 5 | Large dot | Prominent single points |
| 20 | Full circle | General purpose, common in publications |
| 21 | Full square | Distinguish one dataset from circles |
| 22 | Full triangle up | Data with an ordering or hierarchy |
| 23 | Full triangle down | Paired with triangle up for two datasets |
| 24 | Open circle | When you want to see overlapping points |
| 25 | Open square | Variant of square with hollow interior |
| 26 | Open triangle up | Combine with filled markers on same plot |
| 28 | Open triangle down | As above, for contrast |
To change the marker type of an object that supports markers, such as a TGraph or a histogram drawn with a marker style, you call
graph->SetMarkerStyle(20);or
hist->SetMarkerStyle(24);
You can check the current style with GetMarkerStyle() if needed.
There are two broad categories of marker styles. Filled markers have solid interiors, like style 20 or 21. Open markers have empty interiors with only an outline, like style 24 or 25. Filled markers are easier to see on printed plots and in presentations, especially when the points are small. Open markers are useful when points overlap heavily, since you can still see underlying information through the hollow center.
When plotting multiple datasets together, combine different marker types so that each dataset can be distinguished even if the figure is printed in grayscale. For example, use filled circles for one sample, open squares for another, and filled triangles for a third. Avoid using too many similar shapes such as several different kinds of triangles, unless you clearly explain the legend. The key idea is that the marker type itself encodes which dataset a point belongs to, independently of color.
Some draw options tell ROOT to use markers explicitly. For example, graphs drawn with graph->Draw("AP") will show both axes and markers, while a histogram drawn with hist->Draw("P") or hist->Draw("PE") will represent bin contents with markers at the bin centers. Knowing which draw option activates markers helps you understand when your chosen marker type will actually appear.
Important rule: Always combine marker types with a clear legend. Marker type alone is not enough if the legend does not document which dataset each symbol represents.
Marker size
Marker size controls how large each symbol appears on the plot. In ROOT, you set the marker size with
object->SetMarkerSize(Double_t size);
where size is a dimensionless scaling factor. A value of 1.0 is considered the default size. Smaller values create smaller markers, for example 0.7, and larger values, such as 1.2 or 1.5, produce bigger symbols.
You can read back the current size with
double s = object->GetMarkerSize();Marker size is relative to the axis and canvas dimensions, not in pixels directly. This means the same size value can appear slightly different on canvases with very different aspect ratios, or when exported to various formats. If you are preparing publication quality figures, you may need to fine tune the size parameter and check the result in the final output format, such as PDF.
Choosing a proper marker size depends on the density of your data and the intended audience:
If the plot has many points that are close to each other, relatively small markers help prevent the figure from becoming a solid black or colored band. In these cases, combining a small marker size around 0.7 with a thin line is often more readable.
If the plot has only a few points, you can increase the marker size to make each point stand out. Sizes of 1.2 to 1.5 are common for sparse data or key measurements that you want the reader to focus on.
If you will present the plot on a projector or in a slide deck, markers need to be larger than for a printed page so that people in the back of the room can still see them clearly.
Compare the qualitative effects in this reference table.
| Situation | Suggested marker size range |
|---|---|
| Very dense scatter plot | 0.5 to 0.7 |
| Typical ROOT graph on paper | 0.8 to 1.0 |
| Few points, emphasize each point | 1.2 to 1.5 |
| Conference slides or talk | 1.3 to 1.8 |
Be careful when changing both marker size and line width together. Very thick lines combined with very large markers can hide fine structure in the data and make it difficult to see uncertainties or shape details.
If you overlay several datasets, you can vary marker size slightly between them to increase contrast. For example, use size 1.0 for one dataset and 1.3 for another, together with different marker types. Do not overuse this effect, because too many different sizes in the same plot can be visually confusing.
Important rule: Adjust marker size according to data density and output medium. Markers must be large enough to see individually, but not so large that they cover important features or hide overlapping information.
Marker color
Marker color controls the color used to draw the symbol for each data point. In ROOT, the marker color is set with
object->SetMarkerColor(Color_t color);or equivalently
object->SetMarkerColorAlpha(Color_t color, Float_t alpha);
if you want transparency. The Color_t is usually given as an integer code. ROOT provides a default palette of color indices that you can use directly.
Some common predefined color codes are listed below.
| Color code | Color name |
|---|---|
| 1 | Black |
| 2 | Red |
| 3 | Green |
| 4 | Blue |
| 5 | Yellow |
| 6 | Magenta |
| 7 | Cyan |
| 8 | Dark green |
| 9 | Purple |
| 38 | Dark blue |
| 46 | Orange |
To set marker color to red, for example, use
graph->SetMarkerColor(kRed);or
graph->SetMarkerColor(2);
kRed, kBlue, kBlack and similar names are ROOT constants that correspond to the integer codes, and they make code more readable. There are many variants like kRed+1, kBlue-4, and so on, which create slightly different shades.
For more control, including transparency, you can use
graph->SetMarkerColorAlpha(kBlue, 0.7);Here, the alpha value ranges from 0 to 1.0, where 0 is fully transparent and 1.0 is fully opaque. Transparency can be useful when many points overlap.
When styling markers, remember that color should complement, not replace, differences in marker type. Many people will print your plots in black and white or view them on low quality projectors. If you rely only on color to distinguish datasets, some curves or point sets may become indistinguishable in such conditions. A robust strategy is to assign each dataset both a unique marker type and a distinct color.
Use high contrast colors for key datasets. For example, black filled circles, blue squares, and red triangles are easy to distinguish. Avoid very light colors for primary data points since they may become hard to see on a white background or when printed.
The background and axis themes also matter. If you draw on a white background, dark colors work best. On a dark background, which is less common in publications but may appear in presentations, you should pick light marker colors like yellow or light cyan so that the points stay visible.
If you plan to prepare figures that are friendly for color blind readers, avoid pairs of colors that are difficult to distinguish in common color vision deficiencies, such as pure red and green. Instead, combine choices such as blue and orange, or use different shapes and line styles to reinforce the distinction.
You can query the current marker color with
int c = object->GetMarkerColor();and then print or log this value if you want to verify your styling programmatically.
Important rules:
Use both marker color and marker type to distinguish datasets, so the plot remains readable in grayscale and for color blind viewers.
Avoid low contrast colors between markers and background, or between different datasets that must be compared directly.
Views: 0
Where to Move
Move chapter:
- ☰ 1. Introduction to ROOT
- ☰ 1.1. What Is ROOT?
- ☰ 1.2. Installing ROOT
- ☰ 1.3. Starting ROOT
- ☰ 1.4. Your First ROOT Session
-
- ☰ 2. C++ Basics for ROOT
- ☰ 2.1. Why ROOT Uses C++
- ☰ 2.2. Variables and Data Types
- ☰ 2.3. Operators
- ☰ 2.4. Conditional Statements
- ☰ 2.5. Loops
- ☰ 2.6. Functions
- ☰ 2.7. Arrays and Vectors
-
- ☰ 3. ROOT Macros
- ☰ 3.1. What Is a ROOT Macro?
- ☰ 3.2. Running ROOT Macros
- ☰ 3.3. Functions Inside ROOT Macros
- ☰ 3.4. Compiling ROOT Macros
- ☰ 3.5. Organizing a ROOT Project
-
- ☰ 4. ROOT Objects and the ROOT Object Model
- ☰ 4.1. Introduction to ROOT Classes
- ☰ 4.2. Object Names and Titles
- ☰ 4.3. ROOT Collections
- ☰ 4.4. Inspecting ROOT Objects
-
- ☰ 5. Histograms
- ☰ 5.1. Introduction to Histograms
- ☰ 5.2. Creating a 1D Histogram
- ☰ 5.3. Filling Histograms
- ☰ 5.4. Drawing Histograms
- ☰ 5.5. Histogram Properties
- ☰ 5.6. Accessing Histogram Bins
- ☰ 5.7. Histogram Errors
- ☰ 5.8. Normalizing Histograms
- ☰ 5.9. Combining Histograms
-
- ☰ 6. Two-Dimensional Histograms
- ☰ 6.1. Creating 2D Histograms
- ☰ 6.2. Filling 2D Histograms
- ☰ 6.3. Drawing 2D Histograms
- ☰ 6.4. Projections
- ☰ 6.5. Profiles
-
- ☰ 7. Graphs
- ☰ 7.1. Introduction to TGraph
- ☰ 7.2. Creating a TGraph
- ☰ 7.3. Graph Styling
- ☰ 7.4. TGraphErrors
- ☰ 7.5. TGraphAsymmErrors
- ☰ 7.6. MultiGraph
-
- ☰ 8. Canvases and Plotting
- ☰ 8.1. TCanvas
- ☰ 8.2. Dividing a Canvas
- ☰ 8.3. Drawing Multiple Objects
- ☰ 8.4. Legends
- ☰ 8.5. Text and Annotations
- ☰ 8.6. Logarithmic Axes
- ☰ 8.7. Saving Plots
-
- ☰ 9. Styling ROOT Plots
- ☰ 9.1. ROOT Plot Styles
- ☰ 9.2. Axis Configuration
- ☰ 9.3. Line Styles
- ☰ 9.4. Marker Styles
- ☰ 9.5. Publication-Quality Figures
-
- ☰ 10. Mathematical Functions
- ☰ 10.1. Introduction to TF1
- ☰ 10.2. Built-in Functions
- ☰ 10.3. Custom Functions
- ☰ 10.4. Evaluating Functions
- ☰ 10.5. Function Integrals
-
- ☰ 11. Curve Fitting
- ☰ 11.1. Introduction to Fitting
- ☰ 11.2. Gaussian Fits
- ☰ 11.3. Polynomial Fits
- ☰ 11.4. Custom Fit Functions
- ☰ 11.5. Fit Parameters
- ☰ 11.6. Goodness of Fit
- ☰ 11.7. Fit Residuals
- ☰ 11.8. Fitting Graphs
-
- ☰ 12. ROOT Files
- ☰ 12.1. Introduction to ROOT Files
- ☰ 12.2. Creating ROOT Files
- ☰ 12.3. Writing Objects
- ☰ 12.4. Reading ROOT Files
- ☰ 12.5. Exploring ROOT Files
- ☰ 12.6. Directories Inside ROOT Files
-
- ☰ 13. TTrees
- ☰ 13.1. Introduction to TTrees
- ☰ 13.2. Creating a TTree
- ☰ 13.3. Filling a TTree
- ☰ 13.4. Writing a TTree to a File
- ☰ 13.5. Reading a TTree
- ☰ 13.6. Inspecting TTrees
- ☰ 13.7. Drawing Data from TTrees
- ☰ 13.8. Applying Selection Cuts
- ☰ 13.9. Branch Addresses
-
- ☰ 14. Event-Based Data Analysis
- ☰ 14.1. Understanding Event Data
- ☰ 14.2. Event Loops
- ☰ 14.3. Event Selection
- ☰ 14.4. Derived Quantities
- ☰ 14.5. Analysis Workflow
-
- ☰ 15. Working with Real Experimental Data
- ☰ 15.1. Importing Text Data
- ☰ 15.2. Converting Data to ROOT
- ☰ 15.3. Data Cleaning
- ☰ 15.4. Data Calibration
- ☰ 15.5. Signal and Background
-
- ☰ 16. Random Numbers and Simulations
- ☰ 16.1. Random Number Generation
- ☰ 16.2. Common Distributions
- ☰ 16.3. Simple Monte Carlo Simulation
- ☰ 16.4. Detector Resolution Simulation
- ☰ 16.5. Efficiency Simulation
-
- ☰ 17. Statistical Analysis with ROOT
- ☰ 17.1. Basic Statistics
- ☰ 17.2. Probability Distributions
- ☰ 17.3. Statistical Uncertainties
- ☰ 17.4. Chi-Square Tests
- ☰ 17.5. Confidence Intervals
-
- ☰ 18. Modern ROOT with RDataFrame
- ☰ 18.1. Introduction to RDataFrame
- ☰ 18.2. Loading Data
- ☰ 18.3. Filtering Data
- ☰ 18.4. Defining New Columns
- ☰ 18.5. Creating Histograms
- ☰ 18.6. Statistical Operations
- ☰ 18.7. Saving Results
- ☰ 18.8. Multithreading
-
- ☰ 19. ROOT and Python
- ☰ 19.1. Introduction to PyROOT
- ☰ 19.2. ROOT Objects in Python
- ☰ 19.3. Reading ROOT Files with Python
- ☰ 19.4. PyROOT and NumPy
- ☰ 19.5. PyROOT and Matplotlib
- ☰ 19.6. Choosing Between C++ and Python
-
- ☰ 20. Advanced TTree Techniques
- ☰ 20.1. Trees with Multiple Branches
- ☰ 20.2. Storing std::vector Objects
- ☰ 20.3. TChain
- ☰ 20.4. Friends
- ☰ 20.5. Efficient TTree Analysis
-
- ☰ 21. ROOT for Particle and Nuclear Physics
- ☰ 21.1. Four-Vectors
- ☰ 21.2. Particle Kinematics
- ☰ 21.3. Invariant Mass
- ☰ 21.4. Angular Distributions
- ☰ 21.5. Detector Spectra
-
- ☰ 22. Debugging and Common ROOT Problems
- ☰ 22.1. ROOT Object Ownership
- ☰ 22.2. Null Pointers
- ☰ 22.3. Segmentation Faults
- ☰ 22.4. Missing Histograms
- ☰ 22.5. ROOT File Problems
- ☰ 22.6. TTree Branch Problems
- ☰ 22.7. Histogram Range Problems
- ☰ 22.8. Fit Failures
- ☰ 22.9. Debugging ROOT Macros
-
- ☰ 23. Writing Better ROOT Analysis Code
- ☰ 23.1. Separating Analysis and Plotting
- ☰ 23.2. Using Functions
- ☰ 23.3. Using Header Files
- ☰ 23.4. Naming Conventions
- ☰ 23.5. Avoiding Hard-Coded Values
- ☰ 23.6. Configuration Parameters
- ☰ 23.7. Reproducible Analysis
- ☰ 23.8. Version Control with Git
-
- ☰ 24. Final Project
- ☰ 24.1. Project Overview
- ☰ 24.2. Analyze a complete scientific dataset using ROOT.
- ☰ 24.3. Import the Data
- ☰ 24.4. Explore the Dataset
- ☰ 24.5. Apply Data Selection
- ☰ 24.6. Create Histograms
- ☰ 24.7. Fit the Data
- ☰ 24.8. Calculate Physical Quantities
- ☰ 24.9. Estimate Statistical Uncertainties
- ☰ 24.10. Create Publication-Quality Figures
- ☰ 24.11. Save the Analysis Results
- ☰ 24.12. Write a Short Analysis Report
-
- ☰ 25. Appendices
- ☰ 25.1. A. ROOT Command Cheat Sheet
- ☰ 25.2. B. ROOT Histogram Classes
- ☰ 25.3. C. ROOT Graph Classes
- ☰ 25.4. D. Common TTree Commands
- ☰ 25.5. E. Common Drawing Options
- ☰ 25.6. F. Common Fit Functions
- ☰ 25.7. G. ROOT C++ Cheat Sheet
- ☰ 25.8. H. PyROOT Cheat Sheet
- ☰ 25.9. I. Common ROOT Errors and Solutions
- ☰ 25.10. J. Recommended ROOT Analysis Workflow
-
Comments
Please login to add a comment.
Don't have an account? Register now!