Better name for the app

[udupa-varun]

The current name was always supposed to be a placeholder, and now that the app has taken on a more defined shape, it's time to choose a more appropriate name. Some considerations of the app's identity and the purpose for which it has been built this way:

• The primary objective is to enhance the Libraries project building experience. e.g. you have some DAQ data files that you explore, lay out your raw data, then features and finally health.
• At any point in that process, you can save out your current results into an H5 file via the Libraries project script. The data in this file can be explored visually within the app.
• Charts can be saved out for any presentations if needed.
• The H5 file can be rather large over time, and is built to allow for viewing specific time periods at a time.
• Note that there is a loose plan to support two kinds of "raw data" - one set that is more dashboard friendly and sent to Deploy, and another set that might differ in terms of number of variables, or sampling rate etc. The H5 file will be the only source for that other set of raw data. See #21
• Another use case could be a deployed project, where a machine/component has had an incident worth exploring offline. e.g. you want to see if tweaking the model/adding new features would have produced an earlier warning. Any results before the tweaking are already available for you in the file Libraries created.
• While the app has charts like Deploy, that is the only intersection. It only does visualization, and has a different approach to it. There is no concept of a project, or any of the Deploy staples like reporting/prediction/alarms/emails/integration etc.
• In the distant future (if folks are in agreement internally), it could be used as a presentation tool for clients, or be made available on client systems. The only reason this is mentioned now is as a consideration when naming the application.

In summary, the app is considered:

• an extension of Libraries,
• is a visualization tool,
• aims to help with developing/tuning Libraries projects,
• and offers a deeper dive than the traditional dive Deploy offers.

With that, some names to begin with:

• PDX H5 Explorer (current name)
• PDX Libraries Charts
• PDX Libraries Results Viewer
• PDX Time Machine
• PDX Scuba

(no such thing as a bad name, right?)

@MattBuzza feel free to throw in suggestions! I will reach out to PB this week, mainly to introduce the app but will see if he has suggestions as well.

[MattBuzza]

PDX Scuba sounds pretty cool and has a nice ring to it. Other possible names:

• PDX Data Explorer
• PDX Offline Visualizer or Explorer
• PDX Detective (haha)
• PDX Magnifying Glass

PB can probably come up with better names too.

I do like the idea of being able to use the h5 explorer for generating plots for clients for practicality reasons, but I'd think we'd want to convey to our customers that PDX Deploy can be used to generate the same or at least most of the plots, since Deploy is what they will be using/what we are selling our customers (at least for the foreseeable future). Not sure how feasible it is, but it might be good to even make the plots that are exported from the h5 viewer look the same as the plots exported from Deploy to make it easier for them to visualize doing it in Deploy, but I don't think thats a big deal, will have to see what PB thinks.