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

Update the default state generation of neuroglancer #1430

Open
3 tasks
Tracked by #1058
manasaV3 opened this issue Dec 24, 2024 · 1 comment
Open
3 tasks
Tracked by #1058

Update the default state generation of neuroglancer #1430

manasaV3 opened this issue Dec 24, 2024 · 1 comment
Labels
backend P0 Must have

Comments

@manasaV3
Copy link
Contributor

manasaV3 commented Dec 24, 2024

Motivation

To update the neuroglancer visualization config state to incorporate changes made to improve user experience.

Changes to be incorporated:

  1. Reformatted layout of the neuroglancer page (Reach out to Metacell about this)
  2. opacity slider for additive blending (feat: Add default opacity to 1 and blend to additive (CC-165) cryoet-data-portal-neuroglancer#27)
  3. hide shader code from users (Add option to hide/show code block google/neuroglancer#688, feat: Add default value to false for code editor display cryoet-data-portal-neuroglancer#29)
  4. hide the opaque, single-color background of the orthoplanes in the 3D view of the tomogram (feat: option to hide cross section background in 3D slice views google/neuroglancer#663)

Changes Required

As all of the integrations to the in the cryoet-data-portal-neuroglancer, have default values, this should not require any additional values to be passed during the state generation.
The version of cryoet-data-portal-neuroglancer package included with the ingestion, should be be updated to include the new changes, and the config generation should be validated for any regressions. This can be done by comparing it to the existing rendering in prod for comparing the layers generated visually.

What done looks like

  • All of the config changes have been incorporated.
  • The neuroglancer config has been regenerated for all the dataset and runs in staging and pass the validations
  • The neuroglancer config has been updated in prod
@manasaV3
Copy link
Contributor Author

Implementing #1431 would address most of the requirements for this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend P0 Must have
Projects
None yet
Development

No branches or pull requests

1 participant