Tops data pull method

[mlbelobraydi]

We currently have two versions of the code that ingest data in different ways.

Real data could be in either of the two methods so the code will need to be dynamic to pull either from a table or from existing .csv files.

Alternatively, our assumptions have the requirement that the data is ready to go, so we could pick a single method and state that is the format the data needs to be in for the code to work.

Without a decision here, it will be difficult to make a path forward to test different datasets.

[mlbelobraydi]

I think we need to synchronize methods between the main branch and Evan_update branch before going forward. If we go the independent .csv can we borrow ingestion tools from striplog to make the table method easier? This might spin off into a bit of an ingestion tool (indigestion tool, more like it) to help fit some other test data into our processes.

[mlbelobraydi]

@EvanBianco has a solution for loading the data in different ways. Need to identify how to bring in the functions on xsection.py is a way that helps app.py.