Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • nomad-FAIR nomad-FAIR
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 325
    • Issues 325
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 48
    • Merge requests 48
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
    • Model experiments
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • nomad-labnomad-lab
  • nomad-FAIRnomad-FAIR
  • Issues
  • #517

Improving the overview page with section results

In non trivial cases (e.g. long geometry optimisation and many sites in the system), the load times for the overview page (v0.10.1) can be quite long. For example here: https://nomad-lab.eu/prod/rae/beta/gui/entry/id/10k9kKRNTiWFsaK56Ft3og/xUjNvzui8NTYPBhdxshs5QukaRms/overview

The cause is loading a large archive of several MB. With the new section results, we can reduce this by only partially loading some of the archive. This is more test driving the section results and try its viability before investing more time. The overview page is a mimic for the "average" API user that is just interested in the results.

  • The entry page should download the entry data using API v1, which will contain the old section_metadata and if available, also the new section_results. The GUI should primarily use section_results as the information source, but will also have a fallback of using the information in section_metadata to populate the GUI.
  • If section_results is available for the entry, the overview page should use the new partial archive requests to only download section_results from the archive (incl. the referenced systems, properties, etc). This will improve the page loading speed. This is not just networking, the API also will only load the relevant sections from the disk on the server. Also in this case there should be a fallback that downloads the full archive and uses the old metadata to populate the GUI.
  • The overview page uses the available properties (provided as part of the repo metadata) to pre-render all properties (not just the material).
  • We add a geometry opt. normalizer that compresses the convergence into a numpy array quantity. This should be saved in section geometry optimisation.
  • We produce a section results with the new normalizer. The geometry optimisation convergence can be added as a property. We can do this without the new indices.
  • We remove the structure view from optimization component. It was rather gimmicky and doesn't warrant to load all the systems.
Edited May 04, 2021 by Lauri Himanen
Assignee
Assign to
Time tracking