Input/output logging

[elmisback]

In order to replace the Herbie demo, the most important missing feature is input-output logging. We can accomplish this through a logging server that all input expressions, alternatives, and sampling info are sent to. We should try to avoid data duplication to the extent that we can, but the priority is having something that runs.

[elmisback]

We need to save at least the input spec, the sample, any expressions considered, and the analysis data for those expressions for each tool.

[elmisback]

• [ ] dump Odyssey state into a single object as a schema draft

[elmisback]

We could also potentially load analysis state from this server?

[parthrdesai]

Need to discuss with Edward more on what we need to do to accomplish this.

[elmisback]

• https://github.com/herbie-fp/odyssey/blob/main/doc/adding_external_tool_backend.md
• https://github.com/herbie-fp/odyssey/tree/main/server -- has .service.example files for running server with systemd -- these examples run binaries, but you will just run a Node process that handles logging
• goal is log all of the user-input expressions (landing page + Add button)
• add a session ID so we know who did what

[parthrdesai]

Created an express server listning on port 8003 which gets data: sessionID, expression and timestamp. We can now log data for both expressions landing page and add button expressions. Below is a file where we are logging now.

[parthrdesai]

Added more logging like:

• Now we can log all the expression that are produced by herbie when user clicks improve
• Now we can log Selected point in Error Plot by user and on what expression is selected point selected in the graph.
• Also we have now description for each logging event. Eg: "Added expr from home page", " Select point: xyz on Expression: zxy".

Looking forward to get as much as data we can get from user through logs.