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

Flow Diagnostic Plot (one plot with no name) #11148

Closed
RezaeiDoust opened this issue Jan 31, 2024 · 2 comments · Fixed by #11146
Closed

Flow Diagnostic Plot (one plot with no name) #11148

RezaeiDoust opened this issue Jan 31, 2024 · 2 comments · Fixed by #11146
Assignees
Labels
BugInRelease Bug in an official release

Comments

@RezaeiDoust
Copy link
Collaborator

One of the plots under "Flow Diagnostic Plots" --> "Default Flow Diagnostic Plot" has not name.

Also, I believe "Default Flow Diagnostic Plot" should be the first plot in "Flow Diagnostic Plot". not because it is more important but due to naming. I can elaborate if needed.

image

@RezaeiDoust
Copy link
Collaborator Author

The plot with the missing name gets a name " Accumulated Flow ...." after a wells and date and ...are selected.

it could be (probably good) to start with "Accumulated Flow Chart" or something like that

@RezaeiDoust
Copy link
Collaborator Author

image

@RezaeiDoust RezaeiDoust added the BuildPlatform Issues related to build platform label Feb 1, 2024
@RezaeiDoust RezaeiDoust removed the BuildPlatform Issues related to build platform label Feb 1, 2024
@magnesj magnesj self-assigned this Feb 2, 2024
@magnesj magnesj added the BugInRelease Bug in an official release label Feb 2, 2024
@github-actions github-actions bot added the PendingRelease Issues is fixed and will be available in next release label Feb 2, 2024
@magnesj magnesj removed the PendingRelease Issues is fixed and will be available in next release label Mar 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BugInRelease Bug in an official release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants