Run summary does not include tables
See original GitHub issuewandb --version && python --version && uname
- Weights and Biases version: 0.8.18
- Python version: 3.6.9
- Operating System: Linux (Google Colab)
Description
I want to do an analysis of data that was added to tables in my run summary. However, when I try to retrieve the data tables using the Python API, I get empty dictionaries.
What I Did
import wandb
api = wandb.Api()
run = api.run("<project id here>")
assert 'table name' in run.summary.keys() # true
run.summary['table name'] # {}
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Data Warehousing Summary Tables - MariaDB
There will typically be a "few" summary tables. Often one summary table can serve multiple purposes sufficiently efficiently. As a rule of thumb,...
Read more >sumtable: Summary Statistics
summ is the set of summary statistics functions to run and include in the table. It is very flexible, hopefully without being difficult...
Read more >Make summary data easier to read by using a crosstab query
In the Crosstab row for the summary values field, select Value. You cannot specify criteria for or sort on a summary values field....
Read more >Excel Pivot Table Summary Functions Sum Count Change
In an Excel pivot table, Values are shown as Sum or Count. Learn why this happens, and see how to change to other...
Read more >Cubing – Summary tables - IBM
A summary table is a special type of a materialized query table (MQT) that specifically includes summary data.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for the response! I was able to reproduce the bug. If you call
run.summary_metrcs['table name']
the data is returned, we’ll look into the root cause and get a fix in the next release.Hey @seangtkelley In the past year we’ve majorly reworked the CLI and UI for Weights & Biases. We’re closing issues older than 6 months. Please comment to reopen.