Skip to content

Recon steering file for hit killing/smearing studies#1113

Merged
bloodyyugo merged 2 commits intomasterfrom
mgignac-recon-steering-pass-3
Jun 30, 2025
Merged

Recon steering file for hit killing/smearing studies#1113
bloodyyugo merged 2 commits intomasterfrom
mgignac-recon-steering-pass-3

Conversation

@mgignac
Copy link
Collaborator

@mgignac mgignac commented Jun 27, 2025

Add kinks/residuals
Save all collections
Update vertex positions (not important for this study)

@bloodyyugo
Copy link
Contributor

This will only save only events passing the V0 skim cuts. I think this is probably good but I don't think it's how I did this in the past. I added Elizabeth to the reviewers list...comments?

@mgignac
Copy link
Collaborator Author

mgignac commented Jun 27, 2025

This will only save only events passing the V0 skim cuts. I think this is probably good but I don't think it's how I did this in the past. I added Elizabeth to the reviewers list...comments?

Ah, for the purpose of validating the skimming, we should save both. How is that toggled?

<targetConMollerVerticesColName>TargetConstrainedMollerVertices_KF</targetConMollerVerticesColName>
</driver>
<driver name="StripEvent" type="org.hps.recon.skims.MultiSkimDriver">
<skimV0>true</skimV0>
Copy link
Contributor

Choose a reason for hiding this comment

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

I think the V0 skimming is toggled here. We didn't have this in previous versions of the steering files that were used for the hit killing/smearing studies, but it should be okay if we want to leave it (validation of the MC-data comparison will require some basic selections anyway).

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Thanks. Indeed -- however, for the purpose of this small pass, I'd also like to validate the skimming closes, so I'd like to save both skimmed and unskimmed outputs. @bloodyyugo was able to do this in the past, not sure which flag allows for that.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I just tested this steering file -- I do see two slcio outputs, one v0skim and the nominal output of all events.

Copy link
Contributor

Choose a reason for hiding this comment

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

This is because this is also doing the LCIOWriter at the end. The skimmer is writing the streams while LCIO writer is writing every event.

<targetConMollerVerticesColName>TargetConstrainedMollerVertices_KF</targetConMollerVerticesColName>
</driver>
<driver name="StripEvent" type="org.hps.recon.skims.MultiSkimDriver">
<skimV0>true</skimV0>
Copy link
Contributor

Choose a reason for hiding this comment

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

This is because this is also doing the LCIOWriter at the end. The skimmer is writing the streams while LCIO writer is writing every event.

@bloodyyugo bloodyyugo merged commit 43be511 into master Jun 30, 2025
1 check passed
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.

4 participants