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

CICADA-Calo Layer 1 Packer #45863

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

aloeliger
Copy link
Contributor

PR description:

This PR adds a packer for the CICADA data as transmitted by the Calo Layer 1 system. This should be the counterpart to the Calo Layer 1 Unpacker added as a part of #45293.

@slaurila @eyigitba FYI.

PR validation:

All code compiles and has had formatting appllied. The DIGI2RAW step has been checked on MC, and the packer is called appropriately, and produces the expected output for input scores:

image

If this PR is a backport please specify the original PR and why you need to backport that PR. If this PR will be backported please specify to which release cycle the backport is meant for:

This PR is not a backport, but will likely require backports all the way to CMSSW_14_0.

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 3, 2024

cms-bot internal usage

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 3, 2024

-code-checks

Logs: https://cmssdt.cern.ch/SDT/code-checks/cms-sw-PR-45863/41608

Code check has found code style and quality issues which could be resolved by applying following patch(s)

@aloeliger
Copy link
Contributor Author

thought I applied code-format anyways.

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 3, 2024

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 3, 2024

A new Pull Request was created by @aloeliger for master.

It involves the following packages:

  • EventFilter/L1TRawToDigi (l1)

@aloeliger, @cmsbuild, @epalencia can you please review it and eventually sign? Thanks.
@Martin-Grunewald, @dinyar, @eyigitba, @missirol, @mmusich, @thomreis this is something you requested to watch as well.
@antoniovilela, @mandrenguyen, @rappoccio, @sextonkennedy you are the release manager for this.

cms-bot commands are listed here

@aloeliger
Copy link
Contributor Author

please test

@cmsbuild
Copy link
Contributor

cmsbuild commented Sep 4, 2024

-1

Failed Tests: RelVals
Size: This PR adds an extra 12KB to repository
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-41d386/41280/summary.html
COMMIT: 1479f35
CMSSW: CMSSW_14_2_X_2024-09-04-1100/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/45863/41280/install.sh to create a dev area with all the needed externals and cmssw changes.

RelVals

  • 7.3A fatal system signal has occurred: segmentation violation
  • 1306.0A fatal system signal has occurred: segmentation violation
  • 1330.0A fatal system signal has occurred: segmentation violation
Expand to see more relval errors ...

@aloeliger
Copy link
Contributor Author

I have lost access to the test results to help me debug the segfault here. Just going to try and get access to those again.

@aloeliger
Copy link
Contributor Author

please test

@cmsbuild
Copy link
Contributor

-1

Failed Tests: RelVals
Size: This PR adds an extra 12KB to repository
Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-41d386/41558/summary.html
COMMIT: 1479f35
CMSSW: CMSSW_14_2_X_2024-09-17-1100/el8_amd64_gcc12
User test area: For local testing, you can use /cvmfs/cms-ci.cern.ch/week1/cms-sw/cmssw/45863/41558/install.sh to create a dev area with all the needed externals and cmssw changes.

RelVals

  • 7.3A fatal system signal has occurred: segmentation violation
  • 1306.0A fatal system signal has occurred: segmentation violation
  • 1330.0A fatal system signal has occurred: segmentation violation
Expand to see more relval errors ...

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

Successfully merging this pull request may close these issues.

2 participants