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

VisIt 3.4.1: mesh opacity bug and missing triad lines #19614

Closed
tharman-git opened this issue Jun 19, 2024 · 8 comments
Closed

VisIt 3.4.1: mesh opacity bug and missing triad lines #19614

tharman-git opened this issue Jun 19, 2024 · 8 comments
Assignees
Labels
bug Something isn't working impact medium Productivity partially degraded (not easily mitigated bug) or improved (enhancement) likelihood medium Neither low nor high likelihood reviewed Issue has been reviewed and labeled by a developer
Milestone

Comments

@tharman-git
Copy link

Greetings,

With visit 3.4.1 there are two new bugs:

  1. The lines on the Triad are missing, see attached pngs.

  2. When I decrease the opacity from 100% in mesh plot attributes the view becomes garbled.

Below are two images that show the correct and the garbled mesh view.
works
garbled

These feature have worked with previous versions of VisIt.

Relevant Details:

We're loading Uintah data and using the server-client mode between a Debian 11 desktop and a cluster.

Client: VisIt installed from visit3_4_1.linux-x86_64-debian11.tar.gz

Server: VisIt compiled using

build_visit3_4_1 --parallel --uintah --no-icet --mesagl --llvm --no-sphinx --skip-opengl-context-check --system-cmake --qt6 --vtk9 --visit --makeflags -j20

 modules loaded:
 1) chpc/1.0 (S)   2) gcc/11.2.0   3) zlib/1.3.1   4) openmpi/4.1.6   5) cmake/3.26.0
@tharman-git tharman-git added bug Something isn't working impact medium Productivity partially degraded (not easily mitigated bug) or improved (enhancement) likelihood medium Neither low nor high likelihood labels Jun 19, 2024
@biagas
Copy link
Contributor

biagas commented Jun 19, 2024

Not sure if it's related to your issue, but a transparency bug was recently fixed. I wonder if you could provide input so we can see if that fix resolves your issue, too. Having data might also help isolate the Triad problem, not sure that's been reported already.

@JustinPrivitera
Copy link
Member

related to #19123

@tharman-git
Copy link
Author

Attached is a Uintah Data Archive (uda) and a VisIt session file. I used 10 cores in VisIt.

To open the uda select the file advect.uda.000->index.xml

meshOpacityBug.tar.gz

@cyrush cyrush added this to the 3.4.2 milestone Jul 25, 2024
@cyrush cyrush added the reviewed Issue has been reviewed and labeled by a developer label Jul 25, 2024
@cyrush cyrush assigned cyrush and JustinPrivitera and unassigned cyrush Sep 10, 2024
@cyrush
Copy link
Member

cyrush commented Sep 10, 2024

@tharman-git we have resolved several issues related to VTK and opacity, we are going to take a look at the triad issue with your data.

@JustinPrivitera
Copy link
Member

Hi @tharman-git. Sorry for the delay on this. I can reproduce your issue locally; thanks for the data and session file. I can confirm that the opacity issue has been fixed in our upcoming VisIt release. The triad line issue is annoying and is still an open issue. You can work around it by manually changing the Triad line width to something bigger than 1 in the Annotation settings:
image

To get around the opacity issue, you can turn off scalable rendering mode and run in serial, or you can use the beta install of VisIt that we have placed on the open side at /usr/gapps/visit/beta/bin/visit. A closed side install is coming shortly.

@JustinPrivitera
Copy link
Member

I am going to close this issue because the opacity bug has been fixed and there is already a ticket open for the triad lines disappearing.

@tharman-git
Copy link
Author

Thank you!

@JustinPrivitera
Copy link
Member

Forgot to mention before that the open and closed side versions of the 3.4.2 beta with the opacity fix are available at /usr/gapps/visit/beta/bin/visit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working impact medium Productivity partially degraded (not easily mitigated bug) or improved (enhancement) likelihood medium Neither low nor high likelihood reviewed Issue has been reviewed and labeled by a developer
Projects
None yet
Development

No branches or pull requests

4 participants