Running the Adapter

The adapter can be run with following command line options:

ProfileAdapter [‑adjDefaults] [‑dbname <dbname>] [-clean] [‑partial] [‑createPvOnly] [‑debug number] [‑verbose]

Option	Description
-adjDefaults	This option will force the adapter to adjust any default data associated to a load profile. When beginning to use temperature based profiles, it may take a significant amount of time to obtain all of the sampled data for different day type, temperature, and hour combinations. By running with this option, the adapter will adjust the defaulted data associated with each transformer profile to be more in line with actual data received. The processing will find the average scale factor for the different temperature bands that have received actual data for each hour. That average will then be applied to any temperature band for the same corresponding hour that has not yet received actual data and is still using a default. This helps to fill in any discrepancies where actual data is smaller or larger than the defaults. It is recommended this procedure be run once or twice per month to manage the defaulted data. This processing can be run standalone, and CSV files do not need to be present in the staging directory.
-clean	This option will clean all non default load profiles and load profile history before loading a new CSV file. The adapter will first truncate tables pf_loads_profile_samples and pf_loads_profile_override. It will then copy all distributed generation and default load profiles from table pf_load_interval_data to table pf_load_interval_data_tmp to preserve the default profiles. The entire contents of pf_load_interval_data will then be truncated and the defaults will be copied back from the tmp table. After the tables are cleaned up it will then process the new CSV file which essentially does a fresh load.
-dbname <dbname>	This option allows projects to use a separate DBService instance to handle all database requests from the adapter. To use this parameter, the LPDBService will need to be set up in the system.dat file. The value provided for <dbname> will be the name provided in the system.dat for the -service parameter for LPDBService. It is recommend that customers run with this parameter.
-partial	Used when doing a partial load of profiles. (for example, the entire data set is not being loaded).
-createPvOnly	Force the adapter to create PV profiles only, non processing of load profiles will be conducted.
-debug number	Required debug level (0-3).
-verbose	Turn on verbose output for adapter.

The following assumptions apply:

1. Location of the Load Profile Data

• The load profile CSV files should be placed in the directory configured by the PA_ProfileDir SRS rule.

2. Processing the Load Profile Data

• Once the CSV files have been processed by the adapter, they will be moved to the parsed_csvs subdirectory in the directory pointed to by SRS rule PA_ProfileDir

3. Once the data is validated, the load profile data will be written to the following tables:

• PF_LOAD_INTERVAL_DATA: Stores the load profile curves.

• PF_LOADS_PROFILE_SAMPLES: Stores the number of time each data points has been sampled.

• PF_LOADS_PROFILE_OVERRIDE: Manages a record of which loads have device specific load profiles.

4. All Load Profile Adapter specific logs will be placed in a subdirectory labeled logs of the directory pointed to by the PA_ProfileDir SRS rule.