db2

** Run Group is defined in shuo_analysis/run_info/runnumberclassify**.cxx. All runs with same Q2,x,z belongs to one rungroup(all means different targets, pos/neg polarities). Then the run group number is ordered in the first run number in each group. 
*ratio_run_group**.json
   ordered by run group, includes kin variables, all the runs in one run group
*run_info_group.json
  ordered by run numbers, some kin variables and run_group info in each run number
*run_list.json,run_list*.json
  generated when the experiment is running, includes many scalar info
*rungroup_info.json
   ordered by run group, includes simc normfacs from different processes
*simc.json
   ordered by run number, includes efficiencies, normfac
*sim_rungroup.json
   ordered by run group, includes only simc normfacs from different processes
*kin_group**.json
   if is q2xz, then it's ordered by Q2 at the first level, then x at the second level, z at the third level. Then all the run numbers in one group are listed in the object. 
     !combined means, for the Q2 setting, some are set to be 3.98, some are set to be 4, I combined these similar Q2 setting, finally 3 Q2 setting remains
*standard.kinematics/spring_standard.kinematics
   Generated during the runs, some basic information
*all_cut*.json
   I summerized all the cuts that I used
*PID_test.json
   The cuts used in some detector efficiency study