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

Fix max channels #480

Conversation

amassiro
Copy link

Related to issue #478
Tests ongoing.
So far never reached 20k channels.

  • unpacked: left untouched
  • uncalibrechit: added protection
  • rechit: added protection

Does the unpacked require a protection?

@fwyzard fwyzard added the ECAL ECAL-related developments label Jun 11, 2020
@fwyzard
Copy link

fwyzard commented Jun 11, 2020

can you rebase it on top of the current CMSSW_11_1_X_Patatrack ?

@vkhristenko
Copy link

@amassiro, there are a couple of options

  • allocate for max num channels
  • deallocate and allocate 2x if reached the current max.

was not added since the beginning for simplicity. 2nd option is easy to add. i will add a pr for unpacker/uncalib separately

@amassiro
Copy link
Author

@amassiro, there are a couple of options

  • allocate for max num channels
  • deallocate and allocate 2x if reached the current max.

was not added since the beginning for simplicity. 2nd option is easy to add. i will add a pr for unpacker/uncalib separately

Thanks!
I will then do the same for the rechit part.

In the meanwhile I rebased.

@amassiro amassiro force-pushed the amassiro-ecal-rechit-11_1_0-PR-fix-max-channels branch from 485e727 to c03a4e5 Compare June 12, 2020 14:21
@fwyzard
Copy link

fwyzard commented Jul 6, 2020

@amassiro sorry, looks like I lost this one along the way... can you remind me if it was ready to go, or if there was anything pending ?

@amassiro
Copy link
Author

amassiro commented Jul 6, 2020

@amassiro sorry, looks like I lost this one along the way... can you remind me if it was ready to go, or if there was anything pending ?

it was ready to go, unless there was a more refined way to add these protections.

@vkhristenko : did you create the PR for the unpacker with the options you suggested?

@vkhristenko
Copy link

@amassiro , no did not create. i take my words back, please go ahead with whichever way you prefer for that.

@fwyzard
Copy link

fwyzard commented Jul 21, 2020

@amassiro what do you think we should do about this PR now that we merged #517 ?

@amassiro
Copy link
Author

I would close this PR.
The tiny changes, if needed, will be added in a separate clean PR.

@fwyzard
Copy link

fwyzard commented Jul 21, 2020

Mostly not necessary after #517, to be reimplemented if needed.

@fwyzard fwyzard closed this Jul 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ECAL ECAL-related developments
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants