Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Metadata visualization for sequential data: Missing sequence index #1542

Closed
npatki opened this issue Aug 15, 2023 · 0 comments · Fixed by #1552
Closed

Metadata visualization for sequential data: Missing sequence index #1542

npatki opened this issue Aug 15, 2023 · 0 comments · Fixed by #1552
Assignees
Labels
bug Something isn't working
Milestone

Comments

@npatki
Copy link
Contributor

npatki commented Aug 15, 2023

Environment Details

  • SDV version: 1.3.0 (latest)
  • Python version: Any
  • Operating System: Any

Error Description

If I have sequential metadata, I can use the new single table visualize method to see the columns (see API).

When I use this, I see that the visualization correctly shows me any primary keys and sequence keys. However, it does not include the sequence index which an equally important part of my metadata.

Steps to reproduce

You can reproduce this with the demo data. The column Date is the sequence index.

from sdv.datasets.demo import download_demo

real_data, metadata = download_demo(
    modality='sequential',
    dataset_name='nasdaq100_2019'
)
metadata.visualize()

Output:

image

Expected Behavior

No matter what parameter is selected, the bottom section of the visualization should include all 3 valuess:

  • primary key
  • sequence key
  • sequence index

Note that all the concepts are optional, so if any of them are missing, they do not have to show up. Also see #1543, to make sure that these concepts show up in a single box, without any horizontal sub-dividers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants