Skip to content

Conversation

@mcfatelin
Copy link
Contributor

@mcfatelin mcfatelin commented Feb 22, 2017

In order to not make things too complicated, I opened a new branch based on the modified branch.

The main functions for this update are following:

  1. Add the module for simulating s1&s2 with area correlated, based on an input of 2-D band: Log10(S2/S1) verse S1.
  2. Put the customized minitree generation under run_fax.sh so that we don't need to generate the library twice.

The syntax for batch "MidwayBatch_AreaCorrelatedS1S2.py":

python MidwayBatch_AreaCorrelatedS1S2.py ....
<Output path (abs.)>
< number of jobs>
< number of events in each job>
< enable PMT after pulses ?(0 for disable)>
< enable S2 after pulses ?(0 for disable)>
< 2D band for S1-S2 area correlation (abs.)>
< g1 value>
< g2 value>
< If use Public node (0 for no(xenon1t nodes); 1 for yes; 2 for kicp nodes)>

The input 2-D band is contained in pol file. The script MakePickleFromHistogram.py will help you convert one TH2D into the format required.

python MakePickleFromHistogram.py .....


Copy link
Contributor

@pdeperio pdeperio left a comment

Choose a reason for hiding this comment

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

This PR also includes TruthSorting_arrays.py in the full chain script montecarlo/run_sim.sh. @jhowl01, @mcfatelin Is it fully updated here with all the new truth info?

@@ -0,0 +1,153 @@
1
Copy link
Contributor

Choose a reason for hiding this comment

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

Remove this

@@ -0,0 +1,5 @@
FakeWaveform_XENON1T_000000_pax
Copy link
Contributor

Choose a reason for hiding this comment

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

Remove this

@JosephJHowlett
Copy link
Contributor

Sorry @pdeperio somehow I missed your most recent message, fixed the conflicts now. Note that my other pull request will update TruthSorting_arrays.py again, adding the option to not save afterpulse truth info. If that is merged first, this will have a conflict again.

@pietrodigangi
Copy link
Contributor

hi guys, how about this PR? Its' sitting here since months.
Is there any action required or should we close it?
@pdeperio @mcfatelin @jhowl01

@JosephJHowlett
Copy link
Contributor

@pietrodigangi @pdeperio @mcfatelin

My memory is that this was working (conflicts resolved) as of last message (March) but was for some reason (forgetfulness?) never merged. I think if the full-chain processing has survived without it this long, maybe it isn't necessary. We can keep the branch alive and close the PR?

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.

6 participants