Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
E
eicd
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
EIC
eicd
Commits
c4817724
Commit
c4817724
authored
Mar 1, 2022
by
Sylvester Joosten
Browse files
Options
Downloads
Patches
Plain Diff
Enable getters/setters
parent
83051345
Branches
Branches containing commit
No related tags found
1 merge request
!80
Resolve "Move closer to EDM4hep (part 2)"
Pipeline
#28628
failed
Mar 1, 2022
Stage: config
Stage: build
Stage: deploy
Changes
1
Pipelines
2
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
eic_data.yaml
+2
-1
2 additions, 1 deletion
eic_data.yaml
with
2 additions
and
1 deletion
eic_data.yaml
+
2
−
1
View file @
c4817724
---
---
options
:
options
:
# should getters / setters be prefixed with get / set?
# should getters / setters be prefixed with get / set?
getSyntax
:
Fals
e
getSyntax
:
Tru
e
# should POD members be exposed with getters/setters in classes that have them as members?
# should POD members be exposed with getters/setters in classes that have them as members?
exposePODMembers
:
False
exposePODMembers
:
False
includeSubfolder
:
True
includeSubfolder
:
True
...
@@ -251,6 +251,7 @@ datatypes:
...
@@ -251,6 +251,7 @@ datatypes:
## sense. Needs some discussion, note that PID is more emphasized in NP than
## sense. Needs some discussion, note that PID is more emphasized in NP than
## HEP).
## HEP).
-
int32_t PDG // PDG code for this particle
-
int32_t PDG // PDG code for this particle
## @TODO: Do we need timing info? Or do we rely on the start vertex time?
OneToOneRelations
:
OneToOneRelations
:
-
eicd::Vertex startVertex // Start vertex associated to this particle
-
eicd::Vertex startVertex // Start vertex associated to this particle
-
eicd::ParticleID particleIDUsed // particle ID used for the kinematics of this particle
-
eicd::ParticleID particleIDUsed // particle ID used for the kinematics of this particle
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment