Skip to content

Rename HF tables, adjust index to V0#501

Merged
jgrosseo merged 2 commits into
AliceO2Group:masterfrom
jgrosseo:master
Feb 4, 2022
Merged

Rename HF tables, adjust index to V0#501
jgrosseo merged 2 commits into
AliceO2Group:masterfrom
jgrosseo:master

Conversation

@jgrosseo

@jgrosseo jgrosseo commented Feb 3, 2022

Copy link
Copy Markdown
Contributor

No description provided.

@jgrosseo

jgrosseo commented Feb 3, 2022

Copy link
Copy Markdown
Contributor Author

This is precondition to having the Run 2 -> 3 conversion produce these tables.

@vkucera @fgrosa @ginnocen

Please check and let me know...

@jgrosseo

jgrosseo commented Feb 3, 2022

Copy link
Copy Markdown
Contributor Author

For some reason clang started inserting spaces after comments, this makes the diff a bit cluttered.

Have a look how I reworked the index to V0, this is more than renaming.

Comment on lines +67 to +70
DECLARE_SOA_INDEX_COLUMN_FULL(Index0, index0, int, Tracks, "_0"); //! Index to first prong
DECLARE_SOA_INDEX_COLUMN_FULL(Index1, index1, int, Tracks, "_1"); //! Index to second prong
DECLARE_SOA_INDEX_COLUMN_FULL(Index2, index2, int, Tracks, "_2"); //! Index to third prong
DECLARE_SOA_INDEX_COLUMN(V0, v0); //! Index to V0 prong

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes the names of index columns inconsistent as only the track column names start with Index.
Actually, I would suggest to rename Index to Prong because when the column getter is called, one gets the prong table row itself, not its index (which is returned by Id). So my proposal is: Prong0,..., ProngV0.
@jgrosseo @ginnocen What do you think?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am fine with your proposal, as long as the branch names in the tree stay as they are (which they do with your proposal).

As you see I didn't touch the names of the track columns, they were like this already before.

Is it OK if we merge this and you make the modifications of the names in a subsequent PR?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Btw. the AliPhysics PR has been merged, so if you update the validation fw will produce the HF tables already. You have to add the wagon HFCandidateCreator before the converter, see https://alimonitor.cern.ch/trains/train.jsp?train_id=132

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am fine with your proposal, as long as the branch names in the tree stay as they are (which they do with your proposal).

As you see I didn't touch the names of the track columns, they were like this already before.

Is it OK if we merge this and you make the modifications of the names in a subsequent PR?

Yes, it is fine.

@jgrosseo jgrosseo Feb 4, 2022

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK. Merged.
DECLARE_SOA_INDEX_COLUMN(V0, v0); will then become DECLARE_SOA_INDEX_COLUMN_FULL(ProngV0, prongV0, int, V0, "");
(note the empty argument)
You may consider also making prongD0 for the D*

@jgrosseo jgrosseo enabled auto-merge (squash) February 4, 2022 13:19
@jgrosseo jgrosseo disabled auto-merge February 4, 2022 13:20
@jgrosseo jgrosseo merged commit 21bc759 into AliceO2Group:master Feb 4, 2022
fcolamar pushed a commit to fcolamar/O2Physics that referenced this pull request Feb 8, 2022
* add V0Link table to finder

* Rename HF tables, adjust index to V0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants