You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cluster sequence utilities and reconstruction animation (#65)
* Add ranking of jets
Utility function that returns a ranking of initial jets according to some
value, by default p_T
Used to assign stable values to subsequently reconstructed jets based on
their constituents, e.g., for mapping to colours for plotting
* Add intermediate state and plotting
Add a method to retrieve the intermediate state of a reconstruction
(using a special struct, JetWithAncestors)
Plotter for this intermediate state, which preserves colours based on
a ranking of primary clusters (defaults to p_T ranking)
* Fix bug in reco_state
Use the jetp_index of the parent's history entry, instead of the history
entry index (which is wrong)
Add merge_steps method to count the number of meaningful
iterations in the reconstruction
process (used to get the number
of animation steps)
* Add reconstruction animation function
animatereco() calculates all of the intermediate states during the
reconstruction and plots them with meshplot, creating an
animation output
* Add feature to plot ancestors
Option to plot all ancestors of a growing jet, using the colour of
the jet they merge to
* Shifting perspective
Allow passing of tuple of two numbers for axis view options
that give the starting and ending points for the axis view
Code refomatted
* Wrap colormap values
When there are > length(colormap) starting clusters
the extra ones are clipped, so instead wrap back to the start
of the colormap
N.B. There is an assumption here that the colormap has 256
categorical values, which may not be true. However,
I can't currently find an easy way to inspect a colormap Symbol
and extract the length
* Use variable for colormap end
* Add title and end frames options
Title does what it says on the tin...
End frames extend the animation at the end
* Minor updates
Ignore video files in the example directory
Remove unneeded dependencies from jetreco.jl
* Improved documentation
Add Documenter setup to use @autodocs to generate
all public and internal documentation.
Use @ref links to refer to methods and types in
main documentation pages.
Move get_all_ancestors() method to ClusterSequence
(it is not visualisation).
Add logo for the package!
Copy file name to clipboardexpand all lines: docs/src/index.md
+18-23
Original file line number
Diff line number
Diff line change
@@ -16,17 +16,16 @@ inclusive ``k_\text{T}``.
16
16
17
17
## Reconstruction Interface
18
18
19
-
The main interface for reconstruction is:
19
+
The main interface for reconstruction is[`jet_reconstruct`](@ref), called as, e.g.,
20
20
21
-
```@docs
22
-
jet_reconstruct(particles; p = -1, R = 1.0, recombine = +, strategy = RecoStrategy.Best)
21
+
```julia
22
+
jet_reconstruct(particles; p =-1, R =1.0)
23
23
```
24
24
25
-
The object returned is a `ClusterSequence`, which internally tracks all merge steps.
25
+
Where `particles`is a collection of 4-vector objects to reconstruct.
26
26
27
-
```@docs
28
-
ClusterSequence
29
-
```
27
+
The object returned is a [`ClusterSequence`](@ref), which internally tracks all
28
+
merge steps.
30
29
31
30
## Strategy
32
31
@@ -38,9 +37,12 @@ Three strategies are available for the different algorithms:
38
37
|`RecoStrategy.N2Plain`| Global matching of particles at each interation (works well for low $N$) |`plain_jet_reconstruct`|
39
38
|`RecoStrategy.N2Tiled`| Use tiles of radius $R$ to limit search space (works well for higher $N$) |`tiled_jet_reconstruct`|
40
39
41
-
Generally one can use the `jet_reconstruct` interface, shown above, as the *Best* strategy safely as the overhead is extremely low. That interface supports a `strategy` option to switch to a different option.
40
+
Generally one can use the `jet_reconstruct` interface, shown above, as the
41
+
*Best* strategy safely as the overhead is extremely low. That interface supports
42
+
a `strategy` option to switch to a different option.
42
43
43
-
Another option, if one wishes to use a specific strategy, is to call that strategy's interface directly, e.g.,
44
+
Another option, if one wishes to use a specific strategy, is to call that
45
+
strategy's interface directly, e.g.,
44
46
45
47
```julia
46
48
# For N2Plain strategy called directly
@@ -54,19 +56,8 @@ Note that there is no `strategy` option in these interfaces.
54
56
To obtain final jets both inclusive (``p_T`` cut) and exclusive (``n_{jets}`` or
0 commit comments