Issue with VisIt on Ubuntu 24 Rendering Silo Files #20067
-
Originally Posted by @Olami1993 in closed issue #4845. Issue with VisIt on Ubuntu 24 Rendering Silo Files Dear Support Team, I am experiencing an issue where silo files appear as a black output ( when i added the plot and vlick draw it was black) when loaded in VisIt on Ubuntu 24. I suspect this may be due to compatibility between my current version of VisIt and Ubuntu 24 or a potential issue with the silo files themselves. Could you please advise on resolving this issue or recommend any updates or patches that address this? Thank you for your assistance. |
Beta Was this translation helpful? Give feedback.
Replies: 13 comments 11 replies
-
@Olami1993 |
Beta Was this translation helpful? Give feedback.
-
I installed version 3.4.1 on the Ubuntu 24 version . My data is silo
format. But when I tried to visualize the examples the visit/data e.g
rect3d.silo it worked perfectly
…On Thu, 21 Nov 2024, 17:38 Kathleen Biagas, ***@***.***> wrote:
rect3d.zip <https://github.com/user-attachments/files/17848289/rect3d.zip>
You can try this vtk file. Just unzip it and try a Pseudocolor Plot with
VisIt.
—
Reply to this email directly, view it on GitHub
<#20067 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BEJAJNF47WEO3HGLO7SYS4D2BX47HAVCNFSM6AAAAABSHI6BFOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMZTHAZTGMQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
When I load my own silo files, vislt does not issue any explicit warnings
or errors, but the rendered plots appear as a black box. I am uncertain
about the exact spatial extents of my data. It is possible that the issue
might be related to scale , and I will review this aspect. I am primarily
trying to use the pseudocolor/density. Here is the example of my data
data.zip
<https://drive.google.com/file/d/1TCE1dPce-pjVsJGpMF_DJHuqRPfQAW3A/view?usp=drive_web>
…On Thu, Nov 21, 2024 at 6:00 PM Kathleen Biagas ***@***.***> wrote:
When trying your own Silo files, did VisIt issue any warnings or errors?
Do you know the spatial extents of your data? We sometimes see issues with
black plots when the data is either extremely large or extremely small in
scale.
Which Plot are you trying?
Are you willing/able to share your data files? You can attach them here in
a zip file.
—
Reply to this email directly, view it on GitHub
<#20067 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BEJAJNEBOHBJTD6WXUAOIDT2BX7RRAVCNFSM6AAAAABSHI6BFOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMZTHA2TMNQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
ecc05_d2l3n127_level00_0000.00000000.silo
<https://drive.google.com/file/d/1qzo14oN304BUbrgsLHlvSUBGgvSvfTe9/view?usp=drive_web>
ecc05_d2l3n127_level01_0000.00000000.silo
<https://drive.google.com/file/d/1Ld_DGn-xk5k40r6hsIUh8yYr_A3zB4Dt/view?usp=drive_web>
ecc05_d2l3n127_level02_0000.00000000.silo
<https://drive.google.com/file/d/1F4fEz7Ll_-Qvt4j793QbgZnNRyPXqRYx/view?usp=drive_web>
…On Thu, Nov 21, 2024 at 7:01 PM Kathleen Biagas ***@***.***> wrote:
I cannot access that drive. Could you zip up the smallest sample of your
data file that reproduces the problem and attach it directly here?
—
Reply to this email directly, view it on GitHub
<#20067 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BEJAJNHTG2DWMES4PICIUS32BYGVLAVCNFSM6AAAAABSHI6BFOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMZTHEYTQNQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
here is the zip file that contains the data for one level
…On Thu, Nov 21, 2024 at 7:35 PM Kathleen Biagas ***@***.***> wrote:
I am still getting links to google drive, and a notification that I don't
have access.
—
Reply to this email directly, view it on GitHub
<#20067 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BEJAJNEDVWA7FKT5DU2WQ6D2BYKWJAVCNFSM6AAAAABSHI6BFOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMZTHE2DSOA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Hello VisIt-DAV Team and Prof Kathleen,
Attached are a part of the silo files where the problem still occurs.
Please review and advise on a solution.
Thank you for your assistance
…On Thu, 21 Nov 2024, 19:01 Kathleen Biagas, ***@***.***> wrote:
I cannot access that drive. Could you zip up the smallest sample of your
data file that reproduces the problem and attach it directly here?
—
Reply to this email directly, view it on GitHub
<#20067 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BEJAJNHTG2DWMES4PICIUS32BYGVLAVCNFSM6AAAAABSHI6BFOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMZTHEYTQNQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Here is the link to the file:
https://drive.google.com/file/d/1Rk4QCzqroL31ioc6J05tNAt3xFyGQUMX/view?usp=sharing
…On Thu, Nov 21, 2024 at 7:37 PM Justin Privitera ***@***.***> wrote:
you need to set the share permissions to "anyone with the link"
—
Reply to this email directly, view it on GitHub
<#20067 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BEJAJNAYGW72S3PC6CXRYX32BYK55AVCNFSM6AAAAABSHI6BFOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMZTHE2TEMQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Hello @Olami1993. I think this is a bug with the version of VTK we use, which handles rendering. It looks like VisIt 3.3.3 does not have this issue, as it uses an older version of VTK. Your data is very large in scale:
If I use the I have linked a ticket that captures this issue. We will investigate for future releases of VisIt. In the meantime, I would suggest either using the |
Beta Was this translation helpful? Give feedback.
-
Dear Prof. Justin,
Thank you very much sir for your time and attention and the entire VisIt
team. Noted sir. I will check it out Prof.
…On Mon, 25 Nov 2024, 21:09 Justin Privitera, ***@***.***> wrote:
#3619 <#3619>
—
Reply to this email directly, view it on GitHub
<#20067 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BEJAJNBBQID4MQJJZ6DP6G32CNYXBAVCNFSM6AAAAABSHI6BFOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMZXGYZDQMA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Thanks, I will let you know.
…On Mon, 25 Nov 2024, 21:16 Justin Privitera, ***@***.***> wrote:
Let me know if you have further questions.
—
Reply to this email directly, view it on GitHub
<#20067 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BEJAJNGSKCLSEPT6RFFQ2YT2CNZRFAVCNFSM6AAAAABSHI6BFOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMZXGYZTIMI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
It looks like I was mistaken and this bug has been fixed. We will be releasing VisIt 3.4.2 shortly in which this behavior is corrected. |
Beta Was this translation helpful? Give feedback.
-
Awesome, thanks for the update! But currently I can still visualize the
data on the current version?
…On Mon, 25 Nov 2024, 21:35 Justin Privitera, ***@***.***> wrote:
It looks like I was mistaken and this bug has been fixed. We will be
releasing VisIt 3.4.2 shortly in which this behavior is corrected.
—
Reply to this email directly, view it on GitHub
<#20067 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BEJAJNCIVZ72LCVRMV4Y2Z32CN3Y5AVCNFSM6AAAAABSHI6BFOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMZXGY2DQMA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Ok, I will try. Thanks Prof
…On Mon, 25 Nov 2024, 21:39 Justin Privitera, ***@***.***> wrote:
Yes, but you'll need to scale it down by a factor of 10^-3 at least.
—
Reply to this email directly, view it on GitHub
<#20067 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BEJAJNCQ5MYINT7LYEF4DHD2CN4IBAVCNFSM6AAAAABSHI6BFOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMZXGY2TCMI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
Hello @Olami1993. I think this is a bug with the version of VTK we use, which handles rendering. It looks like VisIt 3.3.3 does not have this issue, as it uses an older version of VTK.
Your data is very large in scale:
The original extents are (-1.197e+14, 1.197e+14, -1.197e+14, 1.197e+14, -1.197e+14, 1.197e+14)
. As @biagas noted above,If I use the
Transform
Operator to scale the plot down, the plot starts to display properly once we get to these extents:(-1.197e+11, 1.197e+11, -1.197e+11, 1.197e+11, -1.197e+11, 1.197e+11)
. This is accomplished by scaling in the X, Y, and Z di…