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

create a UI for vieweing a scorecard #156

Open
TatianaBurek opened this issue Oct 29, 2019 · 1 comment
Open

create a UI for vieweing a scorecard #156

TatianaBurek opened this issue Oct 29, 2019 · 1 comment
Assignees
Labels
METviewer: Scorecard priority: medium Medium Priority type: enhancement Improve something that it is currently doing

Comments

@TatianaBurek
Copy link
Collaborator

TatianaBurek commented Oct 29, 2019

During the scorecard calculation we can create a XML and an image for each cell. The links to these files can be added to each element so users can view the plot and/or load XML to METviewer/METexpress and recreate the plot.
Project key 2783533

scorecaard_ui

@TatianaBurek
Copy link
Collaborator Author

  1. The GSL scorecard that you will see in the video presentation has a web GUI to construct the final grid. In the METviewer case, it would be a big challenge to implement a similar interface. Would it be OK to continue working with XML and the batch mode?
    -- For now, working with XML and batch mode is good. If we happen to be swimming in money when it is all said and done (ha), we can pursue a different interface.
  2. Where will this application be installed and run? RAL server? Someplace else?
    -- RAL server would be the primary target. If it gains traction, I could see folks at EMC wanting access to this application as well.
  3. As you know very well :), METviewer uses data that was previously loaded to the database. Which is an extra step that as I understand you try to avoid. I see that you put a lot of effort to use MET Analysis tools working from the command line instead. Would it be OK to leave the current design with the database or the intent is to use "the command line" scorecard which means, of course, extra time and effort.
    -- Ah, good question. For this scorecard work, we fully intended it to be run the traditional way, where we load the data into a database. We wanted to explore command line options for some of the standard plots we always make, mostly to make the functionality available on an HPC (like Hera), so folks w/o access (or experience) with METviewer could easily make a few plots after running an experiment. Our group still intends on using METviewer for plots and analysis (especially since it is a lot more customizable at this time).
  4. How do you envision the results? Some standalone web page? Part of the METviewer app?
    -- Honestly, I don't know! What would be easiest or more scalable from your perspective?
  5. Issue create a UI for vieweing a scorecard #156 lists a lot of ideas that might be not possible to implement for this budget. Would displaying a plot without the XML part be OK?
    -- Yes, displaying a plot without an XML is fine. We requested more $$, but it got cutback, so let's keep the ideas we don't have money for in mind for the future.

Scorecard example:
gfs_rap_amj_i00_scorecard_surface.xml.txt

TatianaBurek added a commit that referenced this issue Sep 11, 2023
TatianaBurek added a commit that referenced this issue Sep 18, 2023
@TatianaBurek TatianaBurek self-assigned this Oct 17, 2023
TatianaBurek added a commit that referenced this issue Apr 12, 2024
TatianaBurek added a commit that referenced this issue Apr 18, 2024
TatianaBurek added a commit that referenced this issue May 22, 2024
TatianaBurek added a commit that referenced this issue May 22, 2024
@bikegeek bikegeek moved this from 🏗 In progress to 🛑 Stalled in METplus-Analysis-6.0.0 Development Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
METviewer: Scorecard priority: medium Medium Priority type: enhancement Improve something that it is currently doing
Projects
Status: 🟢 Ready
Development

No branches or pull requests

3 participants