Open colinkcurtis opened 5 years ago
Maybe we should just have the workflow produce one "view" at a time, spitting them out at is receives responses. That way, we can worry about aggregating "all_responses" into the gamma_XYZ.out.json file separately. The one big problem becomes two smaller and more manageable issues...
The second item is now implemented, a /api/simple/view/{uid}/ style link is now produced for each response generated and a new (default) browser tab is opened for each automatically.
Take the statistics, e.g. p-value, and all other relevant metrics, through the workflow process so that at the end the sub-groups can be compared in the context of the knowledge graph & map
Estimated Completion: This will be one of my primary Hackathon Activities, March 4 - 8