-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PU tool has hardcoded 2016 information #51
Comments
I will add commented lines for where did they come from, and make arguments for year. It doesn't take long time. |
Can you put the origin information also on the wiki? |
Yep, sure. I will put as commented lines. |
is this finished? can we close? |
no one has done 2017 as far as Im aware. |
yebin and dongjun, can u check this and also add in 2017 samples |
I made a description for the origin of the numbers in the tool; see here. I think we can make the table for 2017 in a similar way. |
This is a left-over from CATTools as I understood it. Where are these numbers from? Is there a nice way to be able to choose based on run conditions.
More generally, we should think how we will run 2016 and 2017 data together when it comes time to do that.
The text was updated successfully, but these errors were encountered: