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

Embedding Projector: fix bookmark projection state #6328

Merged
merged 1 commit into from
Apr 19, 2023

Conversation

alicialics
Copy link
Contributor

@alicialics alicialics commented Apr 15, 2023

Motivation for features / changes

When a bookmark state of loaded, it will contain data on a certain set of projections for some of points (B).

The app also has a different (current) state (A) in terms of which points are projected.

We should completely replace the App state (A) with the bookmark state B.

Technical description of changes

store/replace shuffledDataIndices for bookmarks
wipe out existing projections in app state

Screenshots of UI changes

N/A

Detailed steps to verify changes work correctly (as executed by you)

  1. Export a bookmark that has a UMAP state
  2. Refresh app, open UMAP panel and load in the previous state.
  3. Verify only one set of 5k points are shown (as opposed to 10k points)
  4. Refresh app, load previous UMAP state and adjust parameters to a new UMAP calc is performed
  5. Verify only one set of 5k points are shown (as opposed to 10k points)

Alternate designs / implementations considered

@alicialics alicialics force-pushed the fix_bookmark_proj branch 2 times, most recently from 7bf028f to 6436b3b Compare April 15, 2023 18:23
@rileyajones rileyajones merged commit a1a3b14 into tensorflow:master Apr 19, 2023
14 checks passed
dna2github pushed a commit to dna2fork/tensorboard that referenced this pull request May 1, 2023
## Motivation for features / changes

When a bookmark state of loaded, it will contain data on a certain set
of projections for some of points (B).

The app also has a different (current) state (A) in terms of which
points are projected.

We should completely replace the App state (A) with the bookmark state
B.

## Technical description of changes

store/replace shuffledDataIndices for bookmarks
wipe out existing projections in app state

## Screenshots of UI changes

N/A

## Detailed steps to verify changes work correctly (as executed by you)

1. Export a bookmark that has a UMAP state
2. Refresh app, open UMAP panel and load in the previous state.
3. Verify only one set of 5k points are shown (as opposed to 10k points)
4. Refresh app, load previous UMAP state and adjust parameters to a new
UMAP calc is performed
5. Verify only one set of 5k points are shown (as opposed to 10k points)

## Alternate designs / implementations considered
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants