Re: Troubles with "Salome-CFD extension"
Posted: Wed Mar 16, 2022 12:28 am
Hello,
The OSpray plugin should only affect ParaView, so does not seem related to your issue.
So I am not sure what is wrong here.
2 tests may be interesting:
- sourcing the SALOME environment before running salome_cfd
- sourcing the salome environment before running the install.
Though in both cases, I am not sure of the name of the file you need to source, as it has changed across salome versions and builds (things are becoming more unified, but there may be a backlog here).
You can search for salome_modules.sh and salome_prerequisites.sh in the salome install, and run "source" with either or both of these files (I am not sure whether one or both are present).
Normally, this is done automatically by the salome_cfd_extensions "configure" step, which searches for those files, so I doubt forcing this in the install may help. But it is easy to test at least for the execution step.
Also, if you have no other error logs, SALOME might log some errors under /tmp, so you may check there.
I have tested the salome_cfd_extensions build with Ubuntu 18.04 if I remember correctly, but I do not think I have tested it on Ubuntu 20.04, so there might be some other issues. I'll check with a colleaguer who recently did an Ubuntu install.
Best regards,
Yvan
The OSpray plugin should only affect ParaView, so does not seem related to your issue.
So I am not sure what is wrong here.
2 tests may be interesting:
- sourcing the SALOME environment before running salome_cfd
- sourcing the salome environment before running the install.
Though in both cases, I am not sure of the name of the file you need to source, as it has changed across salome versions and builds (things are becoming more unified, but there may be a backlog here).
You can search for salome_modules.sh and salome_prerequisites.sh in the salome install, and run "source" with either or both of these files (I am not sure whether one or both are present).
Normally, this is done automatically by the salome_cfd_extensions "configure" step, which searches for those files, so I doubt forcing this in the install may help. But it is easy to test at least for the execution step.
Also, if you have no other error logs, SALOME might log some errors under /tmp, so you may check there.
I have tested the salome_cfd_extensions build with Ubuntu 18.04 if I remember correctly, but I do not think I have tested it on Ubuntu 20.04, so there might be some other issues. I'll check with a colleaguer who recently did an Ubuntu install.
Best regards,
Yvan