Skip to content

[EPIC] GEOS-Trame roadmap #84

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

Open
1 of 4 tasks
margauxraguenel opened this issue Apr 18, 2025 · 0 comments
Open
1 of 4 tasks

[EPIC] GEOS-Trame roadmap #84

margauxraguenel opened this issue Apr 18, 2025 · 0 comments
Assignees
Labels

Comments

@margauxraguenel
Copy link
Contributor

margauxraguenel commented Apr 18, 2025

What is the requested feature?

To ease the use of GEOS, we propose a tool that can help visualize and correct elements of the deck. This tool represents interactively the tree of the xml deck structure, and allows to visualize 3D components (mesh, wells, boxes) and apply some corrections if needed directly in the deck.


Describe the solution you'd like

We propose to develop a web app based on the TRAME framework, which allows to add multiple components for text editing and visualization. This work is done in collaboration with Kitware.

This work will rely on algorithms already present in the geosPythonPackages, and propose an alternative to the ParaView plugins for specific deck pre-processing.

The Trame window is for now composed of 5 parts:

  • tree structure of the xml
  • calendar view of the events
  • code editor snippet for parameters check
  • 3D view
  • plot view (check of relative permeabilities for example)

The proposed work here aims at enriching this tool.


Proposed roadmap

  • add possibility to save the deck if modified
  • improve the calendar view
  • add other parameters to check in the crossplot view (imposed gradients, rates on wells,...)
  • new tab to help configure launch
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants