Skip to content

Conversation

@kgilje
Copy link

@kgilje kgilje commented Oct 11, 2018

The majority of the oscillation commits are in: src/pdfz.cpp src/pdfz.h src/signal.cpp src/systematic.cpp src/systematic.h src/osctable.cpp src/osctable.h

I think this caught a few missing updates from synching with Andy's local commits rather than via the general sxmc on github

Copy link
Owner

@mastbaum mastbaum left a comment

Choose a reason for hiding this comment

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

Hi @kgilje! Thanks so much for putting this together, it looks great. I just had a couple of small questions/comments throughout. One overall question is whether it'd be possible to add a flag to use 1-Pee, to oscillate the numus? B8 numu ES isn't big (and the variations here are small, on top of that!) but it'd be nice to be consistent. Let me know what you think. Testing now and will let you know if I run into any issues!

// energy: min-8, max-9, nstep-10, step-11
double energy = fields[syst->obs];
// Skip crazy energies seen in setup.
if (energy > 40) return;
Copy link
Owner

Choose a reason for hiding this comment

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

Are there neutrinos with energies higher than the endpoint?

Copy link
Author

Choose a reason for hiding this comment

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

For the first setup of fake data I was getting segfaults. I tracked it down to dummy values being passed during the setup of the histograms. The easiest way for me to avoid was to add the energy > 40 remove.

int &reject_event, RNGState* rng) {
if (pee_osc_lut_size == 0) {
printf("pdfz::apply_systematic: Something is seriously wrong with the look up table!\n");
return;
Copy link
Owner

Choose a reason for hiding this comment

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

Since there are some really bad conditions here that return, I wonder if it'd be worth setting some error flag that gets checked when samples are periodically copied back to the host memory, and asserting at that point.

Copy link
Author

Choose a reason for hiding this comment

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

I'm no 100% sure how to do that? Do you have any sample code?


void EvalHist::EvalAsync(bool do_eval_pdf) {

// Create a random number generator to pass to oscillation systematic if needed.
Copy link
Owner

Choose a reason for hiding this comment

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

Does this need to happen for every call of EvalHist::EvalAsync, or just once e.g. in the EvalHist constructor?

Copy link
Author

Choose a reason for hiding this comment

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

I tried to do this, but got segfaults. I'm chalking that up to me not knowing how to code GPU style. This may be messy but it works...?

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