Skip to content

Website refurbishing#6

Draft
mj-gomes wants to merge 4 commits intomasterfrom
focal_plane_ui
Draft

Website refurbishing#6
mj-gomes wants to merge 4 commits intomasterfrom
focal_plane_ui

Conversation

@mj-gomes
Copy link
Copy Markdown
Collaborator

@mj-gomes mj-gomes commented Mar 16, 2026

This PR will update the overall website design and functionalities, namely adding a focal plane visualization.
I am opening it now as a draft just so that we can discuss as I proceed with the current changes. Please, feel free to suggest new functionalities or changes to the current ones!

As of now (16/03), these are the changes made:

  • added a focal plane visualization tab to the website, which for now allows to double click any pixel and go to the correspondent detector (of course each pixel corresponds to more than one detector, but this is the alpha version of this functionality, it will be improved in the next days).
  • changed overall design to be more LiteBIRD oriented. I took some design inspiration from Planck Legacy Archive website
  • added a Recent Updates "blog" which I believe can be of use whenever there is a new release, a new change in the website, or other important things for which users should be updated.
  • I also added a "wiki page" column to the table of releases, even though we should discuss if we need to have both the document and the wiki page in there, since the wiki page also has the link to the document, so maybe putting only the link to the correspondent wiki page is enough.

Below are some screenshots of the current status.

image image

@mj-gomes mj-gomes changed the title Focal plane UI Website refurbishing Mar 16, 2026
@mj-gomes
Copy link
Copy Markdown
Collaborator Author

mj-gomes commented Mar 20, 2026

20/03/26 update:

  • added buttons for each of the detectors corresponding to a given selected pixel, clicking the name of a detector then opens in a new window the correspondent detector_info page.
  • we can now (it is actually mandatory for copying the path) pick the release (the release names are hardcoded for now, in a next iteration they should be automatically fetched from the database).
  • after picking the release, one can then click the copy button and copy the full path to the detector for that release.

Getting the information for each detector is done through GET requests to methods implemented in views, so that as less operations as possible are done on the client side.

This works well assuming the detectors' positions in the focal plane will not change (it assumes the same layout for every release). If this changes, the drawing of the plot itself should be release-specific and not automatic when opening the page. This should not be hard to implement if needed.

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant