"self-describing" output data

• MERIC should name the output data files according set parameters (THRD_CF_UnCF) not only if the MERIC_OUTPUT_FILENAME is set, user may add APP parameters.
• MERIC should generate measurementInfo.json for each test if MERIC_OUTPUT_DIR is specified.
• MERIC configuration file should contain information for which metric the configuration is optimal and what baseline was used for the analysis. Together with this information we may also add information about subset of regions that user wants to include to RADAR report. If it is not part of the config file, RADAR assumes that all the regions are included.
• Check measurementInfo.json not to store to a single directory various parameters list, which would make the measurementInfo.json not valid.
• Create a script to merge several directories, each created by MERIC for a unique list of tuned parameters.
• NEW option to specify in advance which parameters will be tuned to avoid creating several directories under a single analysis when having various list of tuned parameters.

Format:

Add a description file measurementInfo.json to your output data folder. This step is not compulsory but this file helps us for data analysis.

{
    "Execution ID": "2",
    "Timestamp"   : "13.6. 2017 14:59",
    "System"      : "IT4I Salomon",
    "DataFormat"  : "node_CF_UnCF_config",
    "Note"        : ""
}

Add information into MERIC's configuration file - new "@RADAR" section:

{
	"a.out_static" : {
		"FREQUENCY" : 1200000000,
		"UNCORE_FREQUENCY" : 1200000000,
		"NUM_THREADS" : 2
	}
	,
	"B":{ 
		"FREQUENCY" : 2500000000, 
		"UNCORE_FREQUENCY" : 2500000000
	},
	
	"@RADAR" : {
		"@METRIC" : { 
			"# COUNTERS - HDEEM:" : "Energy consumption [J]", 
			"# COUNTERS - NVML:" : "Energy consumption [J]"
			},
		"@BASELINE" : 0
	}
}

Relates to #28 (closed) due to change in MERIC's config format.