Clean up and organization

[psakievich]

I'm making this issue mainly to serve as a reminder and keep it on my radar.

This repository could be better organized. The directories are semi descriptively named, there is lots of redundant data and at least three different methods for launching the jobs.

I would suggest we employ a tree data structure for the repository where we organize based on attributes like, reference data (turbine model), simulation type, and use cases.

Ideally we will convert this into a performance test suite that can be run semi regularly on target platforms at some point in the future. Improved data management and uniformity will help with that.