Make inputs to nu_tuple be json file instead of hard coded lists.

[hschellman]

Sean suggests using json files as inputs instead of hardcoded lists. I suggest talking to him about exactly how to do it. Work with Sean on this - it will make your life easier but will take some explanation.

How you do this would look something like

'''
import json

config=json.load("configfilename.json")

tuplelist = config["tuplelist"]
if "limitfile" in config:
limitfile = config["limitfile"]
haslim=True

do the stuff to read in the limits info

else:
haslim=False

variables = config["variables"]

cuts = config["cuts"]

cutchoice = config["cutchoice"]

'''
and then your code does its stuff with all of this initialized

The config file would look like:

{
"variables":["var1","var2"],
"cuts":{"cut1":"whatever" ....},
"cutchoice":["cut1","cut2"],
"limitfile":"limits.txt"
}

[hschellman]

Ask questions here

[smgilligan]

The branch json_testing contains nu_cuts_v6.py, support files, and an updated readme.md.

[hschellman]

Phoebe, please try running nu_cuts_v6.py according to Sean's instructions

[hschellman]

And then make a new json file with many more variables and run v6 again.

[hschellman]

@smgilligan - how do we handle the ranges file name? Is it in the json file or is it still and argument.