VisIt on Mac Studio M2 Max #19505
-
|
I do a lot of 3D visualization with VisIt. Is the current version of VisIt 3.4.1 for Mac Silicon (dmg download) currently optimized to fully utilize the CPU and GPU cores? For example, if I create a new local host profile with 8 processors, will the compute automatically use the high-performance cores? Do you recommend doing a custom build of VisIt? |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 2 replies
-
|
Alas, no, not yet. We are still working through issues with a native Apple silicon build. At this point, its more a matter of resources than a lot of build issues. If you are willing to attempt a custom build of VisIt, that would be great. We would certainly welcome the help. Regarding CPU/GPU, yes, some features in VisIt are able to take advantage of GPUs via VTKm. However, currently, VTKm is used only in a limited subset of various VisIt plot/operators/expressions. If you have a visualization workflow that utilizes those parts of VisIt, you'd be in good shape. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for the quick response. We use a cubesphere mesh and .silo files, and we've found that we can't easily create working vtk files. Is it fair to assume that an Apple Silicon optimized version of VisIt is coming soon, or should I spend some time this summer trying to do a custom build?
Marc
…________________________________
From: Mark C. Miller ***@***.***>
Sent: Friday, May 10, 2024 12:23 PM
To: visit-dav/visit ***@***.***>
Cc: Gagne, Marc ***@***.***>; Author ***@***.***>
Subject: Re: [visit-dav/visit] VisIt on Mac Studio M2 Max (Discussion #19505)
Alas, no, not yet. We are still working through issues with a native Apple silicon build. At this point, its more a matter of resources than a lot of build issues. If you are willing to attempt a custom build of VisIt, that would be great. We would certainly welcome the help.
Regarding CPU/GPU, yes, some features in VisIt are able to take advantage of GPUs via VTKm. However, currently, VTKm is used only in a limited subset of various VisIt plot/operators/expressions. If you have a visualization workflow that utilizes those parts of VisIt, you'd be in good shape.
—
Reply to this email directly, view it on GitHub<#19505 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOPRZ4QJUB4XPRKLBUYHNYLZBTX7VAVCNFSM6AAAAABHQ3LUBCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TGOBWGY3DQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hmmm...I am confused by your remarks regarding "...easily create working vtk files". Note VTKm (and its ability to utilize GPUs) works for any kind of files (including Silo files), VisIt reads. You do not need to have vtk files to utilize it. Regarding Apple silicon native build, yes I am on the hook to return to that asap. So, its a priority to complete in the next few weeks. That said, I could use potential testers 😉 |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, I didn't know VTKm would work with all file types including silo files. And yes, I'd be happy to be a tester. Thank you, Mark.
Marc
…________________________________
From: Mark C. Miller ***@***.***>
Sent: Friday, May 10, 2024 12:31 PM
To: visit-dav/visit ***@***.***>
Cc: Gagne, Marc ***@***.***>; Author ***@***.***>
Subject: Re: [visit-dav/visit] VisIt on Mac Studio M2 Max (Discussion #19505)
Hmmm...I am confused by your remarks regarding "...easily create working vtk files". Note VTKm (and its ability to utilize GPUs) works for any kind of files (including Silo files), VisIt reads. You do not need to have vtk files to utilize it.
Regarding Apple silicon native build, yes I am on the hook to return to that asap. So, its a priority to complete in the next few weeks. That said, I could use potential testers 😉
—
Reply to this email directly, view it on GitHub<#19505 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOPRZ4T5PRJ2YQ522YWM5TDZBTY5FAVCNFSM6AAAAABHQ3LUBCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TGOBWG42DM>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Hi Mark, Just wondering if there’s been any movement on an Apple Silicon version of VisIt? Thanks,
Marc
From: Mark C. Miller ***@***.***>
Date: Friday, May 10, 2024 at 12:31 PM
To: visit-dav/visit ***@***.***>
Cc: Gagne, Marc ***@***.***>, Author ***@***.***>
Subject: Re: [visit-dav/visit] VisIt on Mac Studio M2 Max (Discussion #19505)
Hmmm...I am confused by your remarks regarding "...easily create working vtk files". Note VTKm (and its ability to utilize GPUs) works for any kind of files (including Silo files), VisIt reads. You do not need to have vtk files to utilize it.
Regarding Apple silicon native build, yes I am on the hook to return to that asap. So, its a priority to complete in the next few weeks. That said, I could use potential testers 😉
—
Reply to this email directly, view it on GitHub<#19505 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AOPRZ4T5PRJ2YQ522YWM5TDZBTY5FAVCNFSM6AAAAABHQ3LUBCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4TGOBWG42DM>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I'd be happy to be a tester of a native Apple Silicon version of Visit. Thank you. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, Is there any update with respect to VisIt for Apple M2 Ultra chips? |
Beta Was this translation helpful? Give feedback.
Alas, no, not yet. We are still working through issues with a native Apple silicon build. At this point, its more a matter of resources than a lot of build issues. If you are willing to attempt a custom build of VisIt, that would be great. We would certainly welcome the help.
Regarding CPU/GPU, yes, some features in VisIt are able to take advantage of GPUs via VTKm. However, currently, VTKm is used only in a limited subset of various VisIt plot/operators/expressions. If you have a visualization workflow that utilizes those parts of VisIt, you'd be in good shape.