Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

include HCal Endcap in run_thetamodulemerged.py #31

Open
wants to merge 8 commits into
base: main
Choose a base branch
from

Conversation

mmlynari
Copy link
Contributor

@mmlynari mmlynari commented Jul 4, 2024

@giovannimarchiori
Copy link
Contributor

Hi @mmlynari ,
good to see the HCAL endcap digitisation coming to light!
Please bear in mind that we're phasing out the use of fccrun for the whole sim+reco, our default now is to use ddsim for sim and k4 run for digi+reco, so the changes here will have to be ported to https://github.com/HEP-FCC/FCC-config/blob/main/FCCee/FullSim/ALLEGRO/ALLEGRO_o1_v03/run_digi_reco.py, so you might have started directly from there. Anyway, if it's easier for you to test the geometry / segmentation / digitisation chain with the old setup, we can start like this and then we can help you migrate this script to FCC-config

@giovannimarchiori
Copy link
Contributor

hi @mmlynari you mentioned in the ALLEGRO meeting that you had implemented also the merging of the hcal endcap cells and tested with clustering, but I can't see these changes here - where are they? I am asking because I am working on an updated version of the digi+reco script for the calorimeters (with ddsim+kr4un) and I would like to include also the HCAL endcap

@mmlynari
Copy link
Contributor Author

mmlynari commented Sep 4, 2024

Hi @giovannimarchiori , sorry, I forgot to update the scripts with the most up-to-date changes. I committed it now

@giovannimarchiori
Copy link
Contributor

Thanks! I don't see where the name of 2nd endcap readout is defined but I assume it's the 2nd one in k4geo HCalEndcapReadout_phitheta ?

@mmlynari
Copy link
Contributor Author

mmlynari commented Sep 4, 2024

my bad. yes, it's HCalEndcapReadout_phitheta and I updated the code

@giovannimarchiori
Copy link
Contributor

Thanks! And about the SW clustering, should I pass the HCAL endcap collection to the tower tool via hcalExtBarrelCells or hcalEndcapCells? I'm currently going with the latter

@mmlynari
Copy link
Contributor Author

mmlynari commented Sep 4, 2024

hcalExtBarrelCells

I think hcalEndcapCells is more appropriate. just please double-check that it works. because I was only testing it for standalone hcal, and I am not 100% sure that it won't crash when we include also other subdetectors

@giovannimarchiori
Copy link
Contributor

giovannimarchiori commented Sep 4, 2024

Hi @mmlynari ,
for the hcal barrel, can we also switch to the new positioning tool with the layer data, i.e. move from

cellPositionHcalBarrelTool = CellPositionsHCalBarrelPhiThetaSegTool(

to

cellPositionHcalBarrelTool = CellPositionsHCalPhiThetaSegTool(

?

do we need to pass some extra parameters (detectorName and so on)?

@giovannimarchiori
Copy link
Contributor

giovannimarchiori commented Sep 4, 2024

thanks a lot @mmlynari!
You can see how the new digi+reco script to be used in the k4RecCalorimeter tests looks like: https://github.com/HEP-FCC/k4RecCalorimeter/blob/f9a11004c578938983496180caa4ec9cebe10e94/RecFCCeeCalorimeter/tests/options/ALLEGRO_o1_v03_digi_reco.py

I think I put the barrel and endcap HCal stuff in there correctly but it'd be good if you could have a look.

I ran over 100 events of 50-GeV pions at theta=90 and 100 events of 50-GeV pions at theta=160 and I get clusters of energies typically around 40-45 GeV in all the events so this looks pretty good to me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants