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
I propose a consistent naming convention for MC simulation points / hits among detectors. Having consistent naming conventions improves the readability of the code. Since now AliceO2 has its own base class BasicHit I propose to use the name "Hit" as class name for detector hit classes. The name "Point" as class name for detector hit classes is in my opinion too general and might be even confusing as we might have different usages of Point objects in the future.
The text was updated successfully, but these errors were encountered:
mfasDa
added a commit
to mfasDa/AliceO2
that referenced
this issue
Apr 10, 2017
I propose a consistent naming convention for MC simulation points / hits among detectors. Having consistent naming conventions improves the readability of the code. Since now AliceO2 has its own base class BasicHit I propose to use the name "Hit" as class name for detector hit classes. The name "Point" as class name for detector hit classes is in my opinion too general and might be even confusing as we might have different usages of Point objects in the future.
The text was updated successfully, but these errors were encountered: