Shadow prices file locations for input and output need to be specified

[PeterVermont]

This is important because current system means that sometimes two different configuration file refer to the same working directory. This will cause regression to throw an error. Adding this feature will enable the different configuration files to use totally separate directories.

Right now shadow_prices.txt is hard_coded and is written to and read from the working directory.

Instead we need to have three new configuration settings for each type of ShadowPrices (since ParkAndRide has separate that means 2 x 3 = 6)

used for either input or output if not specified

ShadowPricingPathDefault=.\working\shadow_prices.txt

ShadowPricingPathInput=.\working_workschool\shadow_prices.txt ShadowPricingPathOutput=.\working\shadow_prices.txt

I learned from Nagendra that for Nashville the configuration_workschool.xml and configuration.xml DO have the same working directory because the generated shadow_prices from workschool are used as inputs to the third/last run of the model using configuration.xml.