Update README.md
Browse files
README.md
CHANGED
|
@@ -70,11 +70,13 @@ Columns (per point):
|
|
| 70 |
2. `y` coordinate (integer voxel index, 0 to 768)
|
| 71 |
3. `z` coordinate (integer voxel index, 0 to 768)
|
| 72 |
4. Voxel value (in MeV)
|
| 73 |
-
5. Energy
|
| 74 |
6. Absolute time in nanoseconds
|
| 75 |
7. Number of electrons
|
| 76 |
8. `dx` in millimeters
|
| 77 |
|
|
|
|
|
|
|
| 78 |
Example:
|
| 79 |
|
| 80 |
```python
|
|
@@ -120,9 +122,9 @@ Columns (per cluster):
|
|
| 120 |
|
| 121 |
1. Particle mass (from PDG)
|
| 122 |
2. Particle momentum (magnitude)
|
| 123 |
-
3. Particle vertex `x` coordinate
|
| 124 |
-
4. Particle vertex `y` coordinate
|
| 125 |
-
5. Particle vertex `z` coordinate
|
| 126 |
|
| 127 |
Example:
|
| 128 |
|
|
@@ -269,4 +271,18 @@ A [Colab notebook](https://colab.research.google.com/drive/1x8WatdJa5D7Fxd3sLX5X
|
|
| 269 |
doi={10.48550/arXiv.2502.02558},
|
| 270 |
url={https://arxiv.org/abs/2502.02558},
|
| 271 |
}
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 272 |
```
|
|
|
|
| 70 |
2. `y` coordinate (integer voxel index, 0 to 768)
|
| 71 |
3. `z` coordinate (integer voxel index, 0 to 768)
|
| 72 |
4. Voxel value (in MeV)
|
| 73 |
+
5. Energy deposited `dE` (in MeV)
|
| 74 |
6. Absolute time in nanoseconds
|
| 75 |
7. Number of electrons
|
| 76 |
8. `dx` in millimeters
|
| 77 |
|
| 78 |
+
To build pixel-level labels, we impose a priority ordering when multiple particles overlap in the same voxel such that the label is taken from the highest-priority particle. Under this convention, the `voxel value` field stores the energy contribution from the single particle that determines the voxel's label (that is, the winning particle in an overlap). By contrast, `energy deposited` stores the total energy deposited in the voxel, summed over all particles contributing to that voxel, regardless of which particle supplies the label. In practice, overlaps are rare, so for the vast majority of voxels `voxel value` and `dE` are identical, and we do not expect meaningful differences in downstream performance from using one versus the other.
|
| 79 |
+
|
| 80 |
Example:
|
| 81 |
|
| 82 |
```python
|
|
|
|
| 122 |
|
| 123 |
1. Particle mass (from PDG)
|
| 124 |
2. Particle momentum (magnitude)
|
| 125 |
+
3. Particle vertex `x` coordinate (currently broken)
|
| 126 |
+
4. Particle vertex `y` coordinate (currently broken)
|
| 127 |
+
5. Particle vertex `z` coordinate (currently broken)
|
| 128 |
|
| 129 |
Example:
|
| 130 |
|
|
|
|
| 271 |
doi={10.48550/arXiv.2502.02558},
|
| 272 |
url={https://arxiv.org/abs/2502.02558},
|
| 273 |
}
|
| 274 |
+
```
|
| 275 |
+
|
| 276 |
+
If using momentum values, please cite:
|
| 277 |
+
|
| 278 |
+
```bibtex
|
| 279 |
+
@misc{young2025pandaselfdistillationreusablesensorlevel,
|
| 280 |
+
title={Panda: Self-distillation of Reusable Sensor-level Representations for High Energy Physics},
|
| 281 |
+
author={Samuel Young and Kazuhiro Terao},
|
| 282 |
+
year={2025},
|
| 283 |
+
eprint={2512.01324},
|
| 284 |
+
archivePrefix={arXiv},
|
| 285 |
+
primaryClass={hep-ex},
|
| 286 |
+
url={https://arxiv.org/abs/2512.01324},
|
| 287 |
+
}
|
| 288 |
```
|