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

UI changes to website enabling case study as a sub category #1144

Open
Tracked by #907
jwarner8 opened this issue Feb 14, 2025 · 0 comments
Open
Tracked by #907

UI changes to website enabling case study as a sub category #1144

jwarner8 opened this issue Feb 14, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@jwarner8
Copy link
Contributor

Currently the left hand panel is populated through the category argument of recipes. If we plots lots of spatial plots, for example, the Surface Spatial Plot will contain ~40 plots. If we run for multiple case studies, this number will scale (so 14 case studies - a two week trial) - we will have 14*40 plots, which will become unmanageable to navigate quite quickly.

I wonder if we could create an index file that populates the menu with subcategories, so that you would have something like this;

Surface Spatial Plot
20191014T0000Z
20191015T0000Z
20191016T0000Z
Aggregated
Histogram
20191014T0000Z
20191015T0000Z
20191016T0000Z
Aggregated

We could pass the case study (cycle point) through to the recipe via the includes or otherwise, and use this to populate a menu? E.g. in the recipe;

category: Surface Spatial Plot Difference
category2: $CYCLEPOINT
title: Surface $VARNAME difference ($BASE_MODEL - $OTHER_MODEL)
description: Extracts and plot the difference in surface $VARNAME for all times.

@jwarner8 jwarner8 added the enhancement New feature or request label Feb 14, 2025
@jfrost-mo jfrost-mo mentioned this issue Feb 14, 2025
24 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant