Daily updates:

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

6th May 2021:

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

DAS user:

1. To get the Config values, is “.ini” the right format? - how to make config format standardize in reading and parsing

2. Passing the appropriate values to the corresponding function

3. Stich the previous batch data with this batch

4. Save intermediate data in CSV and png.

5. Read CSV with index_name, date format,

6. Way to get the command line arguments

Solution:

1. Configs can be in a different format, need not be a standard.

2. To carry forward episode duration from the previous batch to the present batch, we need some code to get them in the format which is required for the defined format.

3. As we need previous batch data, to take average of 3 mins, we need to change the API of SVC, DIV, RVF.

4. Intermediate files to be saved should be included in API.

5. read_file (fileName, index_col, isIndexColDate=False, removeDulplicateIndexWithKeep=None)

6. CLASS
   ArgumentClass(varName, help=None, defaultVal=None)
   Eg:
   arg1 = ArgClass("a")
   arg2 = ArgClass("--b","help bb")
   arg3 = ArgClass("--c")

   Function:
   argumentDefinition(ArgumentClass objects....)
   Eg:
   argumentDefinition(arg1,arg2,arg3)

   return dictionary with key od variable name and value passed in command line argument