Page Comparison

Present Enbridge implementation - https://mqidentity-my.sharepoint.com/:w:/g/personal/nkhadri_atomiton_com/ERo7AJWT0rNIv78t_72XPNwBBAANUTov0WtpikAcFRcvaQ?e=kOP3oE

7th May 2021

Config files:

1. present ini: Using Python builtin configparser module - without nested section and list… I have written lot of code to overcome these limitations

2. ConfigObj - third party: very similar to present ini, with minor syntax. This has nested and list features. Easy to generalize the config file.

3. JSON, XML - known to developer fraternity, but may not except layman. As config could be edited from operation and customer itself(not now, but sometime later)

4. Hydra.cc from Facebook - takes YAML as input bit has lot of features. With logging, debugging, and even it can change the config in command line.. It's way too powerful, the question is do we even need these complexities?

Config parser eg:

	keyword1 = value1
	keyword2 = value2

	[section 1]
	# with value as list
	keyword1 = value1, value2, value3 
	keyword2 = value2

# Sub section
		[[sub-section]]
		# this is in section 1
		keyword1 = value1
		keyword2 = value2

			[[[nested section]]]
			# this is in sub section
			keyword1 = value1
			keyword2 = value2

		[[sub-section2]]
		# this is in section 1 again
		keyword1 = value1
		keyword2 = value2

	[section 2]
	keyword1 = value1
	keyword2 = value2

So easy to access the values.

...

6th May 2021:

After defining the reusable functions, what else is needed for DAS users to implement feature engineering.

...