Skip to content

Conversation

@mark-grimes
Copy link

I've not tested these yet. I put the pull request in first to aid discussion.
This doesn't overwrite the old triggers but it makes the new ones the default - only xml menu files can use non-default versions and the fit doesn't work with xml files. As such I would not recommend merging until a full comparison has been made.

@blwiner
Copy link
Contributor

blwiner commented Mar 31, 2014

Mark,
The TTI group also applies a minimum Pt cut to the jets. Would it be possible to add that feature as well?

@mark-grimes
Copy link
Author

Yes, should be quite trivial. Testing will be more work than making the change.

@mark-grimes
Copy link
Author

Added pT cuts. Still needs testing. Also, the pT cut can currently only be set using an input XML menu file. The menu fit currently can't use those though. The pT cut can be set with a "ptCut" parameter, e.g.:

<Trigger formatVersion="0">
    <name>L1_HTT</name>
    <version>1</version>
    <parameter name="threshold1">150</parameter>
    <parameter name="regionCut">5</parameter>
    <parameter name="ptCut">20</parameter>
</Trigger>

Note the "formatVersion" attribute is a flag to allow the information layout to change. The "version" tag sets the version of the trigger used.

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