option 1 changing nT context for shev

Created by: sophiaandaloro

What is the problem / what does the code in this PR do Given discussion in Slack (sensitive info left out.) we are looking to change veto abilities for the current runs planned. This code simply hard-codes settings for nT configuration, where if you aren't looking at tomorrow's planned data, you'll have to just add a line to the top of your code such as st.set_config(<disable hev>) at the top of analysis.

Can you briefly describe how it works? Threshold is set at 1500 PE for reasons discussed in TPC meeting (regarding upcoming runs), with a pass fraction of 1000, meaning virtually no peaks are passed once a high-energy S1 triggers the veto in place. This results in roughly a 6x factor of data reduction on previous runs, so will be slightly lower (though comparable) for upcoming runs.

Can you give a minimal working example (or illustrate with a figure)? Edit by Joran link to note: https://xenonnt.slack.com/archives/C01772B62JD/p1604505610388200?thread_ts=1604411750.343300&cid=C01772B62JD