Closed
Bug 1485977
Opened 7 years ago
Closed 6 years ago
Provide a process for producing an experiment report
Categories
(Data Science :: General, task, P2)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: harter, Assigned: tdsmith)
References
Details
As the components of the experiment analysis pipeline [1] come together, we should provide a step-by-step guide of how to generate an experiment report.
[1] https://docs.google.com/document/d/1KSBgiKFRFqzcZWjRZt6faiRp4mR56jxaJtZwJRPa3Jk/edit#
| Reporter | ||
Updated•7 years ago
|
Priority: -- → P3
| Reporter | ||
Comment 1•7 years ago
|
||
Hey Tim,
Assigning this bug to you as discussed Monday. We need an interface for a analyst to produce an experiment report from the experiment analysis API Sunah is working on (Bug 1485804). I've been calling this the CLI, but I suppose it could be something as simple as documentation and a set of different tools. Bug 1485974 is somewhat related, designing the report scaffolding.
In short, we're looking for a way to turn a table of experiment metrics into a report. If the report we produce is in Markdown, analysts can extend that to be Rmd if they so choose. Maybe a Click CLI with some wrapper around Jinja makes sense? Feel free to grab some time on my calendar if you'd like to discuss.
Assignee: nobody → tdsmith
Priority: P3 → P2
Summary: Provide a step-by-step guide to producing an experiment report → Provide a process for producing an experiment report
| Assignee | ||
Updated•7 years ago
|
Component: Telemetry APIs for Analysis → General
Product: Data Platform and Tools → Data Science
Updated•7 years ago
|
Status: NEW → ASSIGNED
Comment 3•6 years ago
|
||
Is this bug still needed or can we close? Please note that if we do not receive a response within 7 days we will close the ticket.
Flags: needinfo?(tdsmith)
| Assignee | ||
Comment 5•6 years ago
|
||
I think the process Felix is driving is a better way to represent this work now.
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•