Keep input and output in seperate and specific folders

[Betristor]

Discussed in #90

^{Originally posted by Betristor October 29, 2022}
With the expansion of coupled energy sectors, the inputs files and output files are getting more and messy. To keep the inputs in seperate folders like power, hsc and csc could help identify which file is used in which sector. And by subfolders seperating them, we could have identical file names for inputs and even identical column names for specific data, which will bring convenience while adding new sectors. And to keep the output files in seperate folders will have same effect in saving our time developing new sectors.

[Betristor]

@RuaridhMacd This feature and the ability to select zone from data will be the next two things I want to implement. Other features like change the name space may be left for nxet version. And the test examples could be put behind these two proposals in this issue and #96.

[RuaridhMacd]

@Betristor This sounds good. Let me know if you'd like to discuss it more.

[RuaridhMacd]

• Let's implement a simple solution with just input folders for now
• Test and check hard-coded input paths

[Betristor]

@RuaridhMacd I should implement this function after truck_index branch is merged. Changing this will cause some trouble for current users. I will upload an example case to guide users.

[RuaridhMacd]

@Betristor That sounds like a good plan. Thanks

[Betristor]

@RuaridhMacd This issue is a stale one and I will close it. Truck route index, zone selection and seperating inputs and outputs are three tasks identified for me to be solved. I reckon that truck route index is the most demanding one so I take that as propriety and leave this issue later.