coresoftware icon indicating copy to clipboard operation
coresoftware copied to clipboard

Jet DST skimmer

Open Shuonli opened this issue 1 year ago • 10 comments

Types of changes

  • [ ] Bug fix (non-breaking change which fixes an issue)
  • [x] New feature (non-breaking change which adds functionality)
  • [ ] Breaking change (fix or feature that would cause existing functionality to not work for users)
  • [ ] Requiring change in macros repository (Please provide links to the macros pull request in the last section)
  • [x] I am a member of GitHub organization of sPHENIX Collaboration, EIC, or ECCE (contact Chris Pinkenburg to join)

What kind of change does this PR introduce? (Bug fix, feature, ...)

This is the initial commit to the module for making the slimed(skimmed?) DST. Where it will search for max Jet energy and EMCal cluster energy per event and only keep the event that contains high energy jets/clusters.

I think it will also good to have the background event (beam background) rejection implemented in this. I have left a place holder here.

TODOs (if applicable)

Implement the Beam background ID function.

Links to other PRs in macros and calibration repositories (if applicable)

Shuonli avatar Oct 04 '24 19:10 Shuonli

Can I suggest that we organize this differently? Let's have a directory structure that looks like offline -- packages ---- Skimmers ------- Jets ---------- JetSkimmer.cc/h/makefile/etc

Then we can make other directories for different types of skimmers

osbornjd avatar Oct 04 '24 19:10 osbornjd

@osbornjd Don't we want "slimmer" not "skimmer"? We are taking out events not removing information for each event.

bseidlit avatar Oct 04 '24 20:10 bseidlit

I don't think we ever decided on a specific name - every collaboration has their own but I don't think we came to a conclusion. Slimmer and skimmer could in principle refer to the same thing - either you slim the DST down to only include the events you want or you are skimming the larger DST to write out only the ones you want

osbornjd avatar Oct 04 '24 20:10 osbornjd

Sorry I missed the last software meeting. What ever name is decided, these DSTs are meant to skip events that don't meet a certain cut, e.g. jet pT etc...?

eumaka avatar Oct 04 '24 20:10 eumaka

They're intended to be used to write out smaller DSTs that meet certain criteria

osbornjd avatar Oct 04 '24 20:10 osbornjd

Okay, I don't have strong opinions. I think in phenix they called them mini DSTs.

bseidlit avatar Oct 04 '24 20:10 bseidlit

Build & test report

Report for commit d804907ccc4bf4e3c533853b3acc4a88972e8b4b: Jenkins passed


Automatically generated by sPHENIX Jenkins continuous integration sPHENIX             jenkins.io

sphenix-jenkins-ci[bot] avatar Oct 05 '24 03:10 sphenix-jenkins-ci[bot]

Build & test report

Report for commit dd41f849436fd9cb0e9b795716b3db2a224b3999: Jenkins passed


Automatically generated by sPHENIX Jenkins continuous integration sPHENIX             jenkins.io

sphenix-jenkins-ci[bot] avatar Oct 05 '24 03:10 sphenix-jenkins-ci[bot]

It was decided in the software meeting to call it a skimmer.

bseidlit avatar Oct 08 '24 21:10 bseidlit

Build & test report

Report for commit 2a957ad0a59de99de0306ddc99e240176e568af5: Jenkins passed


Automatically generated by sPHENIX Jenkins continuous integration sPHENIX             jenkins.io

sphenix-jenkins-ci[bot] avatar Oct 09 '24 06:10 sphenix-jenkins-ci[bot]

Build & test report

Report for commit afd5abaeccdd020ff751762df9ba0c85de313b63: Jenkins passed


Automatically generated by sPHENIX Jenkins continuous integration sPHENIX             jenkins.io

sphenix-jenkins-ci[bot] avatar Oct 09 '24 20:10 sphenix-jenkins-ci[bot]