User's Manual Sections

[pavlis]

Content we have at present is completely disconnected with the current table of content page for the user's manual. Let me suggest a new organization for the pages and how the existing pages fit into that order:

1. Overview: not written yet and in the current contents (pretty clear need) Should stress use of jupyter notebook tutorials in parallel with this manual.
2. Creating a MsPASS Workflow: This is to be written. Starts with the basic that the job control language. Should describe layout of MsPASS modules. Should describe the documentation and tell users how they should use the docs to design their workflow
3. MsPASS Data Objects - revisions of existing page with the file name "data_objects_design_concepts.rst".
4. MsPASS <-> Obspy - describe converters and how to jump between MsPASS and obspy
5. Database Concepts - revisions to newly pushed page with the title "CRUD_operations.rst"
6. Error Logs - stress this is a parallel safe way to post error messages
7. Undertaker - a section on the concept and use of kill.
8. Importing data - new section focusing for now on SEED data but describing how custom imports can be done. Should how a structure to add sections for new data formats. e.g. we (actually probably I) can and probably should build a sac import module. With C++ code I already have in SEISPP this would be pretty easy.
9. Graphics - brief introduction of the SeismicPlotter and SectionPlotter classes I wrote but also describe how a user can use lower level pyplot functions or obpsy plot functions.
10. Serial Processing - This should describe how to prototype a workflow. It should especially stress a subset of users our system can and should support; obspy users who could use a database to organize their data. Good model would be to have a parallel jupyter tutorial this section would refer to with blocks of code.
11. Parallel Processing - this is an important new section. I think it should be tightly linked to the preceding section and the related tutorial.
12. Exporting data - we have nothing on this topic yet, but it will be needed. A very thorny problem. In the near term we may want to only describe how to use python to do this and not actually have anything other
    than a generic algorithm for export we can suggest (i.e. query for subset to export, loop over cursor converting and saving converted data to external file(s).)
13. Processing History - at the end for now. Perhaps should be earlier before "Importing Data"

[pavlis]

Small modification I think might make sense. I think items 6 and 7 would be better combined in a single section with the title "Error Handling". They actually are closely related topics.