From: Frederic Pons Date: Tue, 5 Dec 2023 18:34:02 +0000 (+0100) Subject: init release notes for v9.12 X-Git-Url: http://git.salome-platform.org/gitweb/?a=commitdiff_plain;h=a0b9319cc6151957d41139c3bda0e6212e2962c7;p=tools%2Fconfiguration.git init release notes for v9.12 --- diff --git a/release_notes/images/v9_12_scaled_jacobian.png b/release_notes/images/v9_12_scaled_jacobian.png new file mode 100644 index 0000000..620d475 Binary files /dev/null and b/release_notes/images/v9_12_scaled_jacobian.png differ diff --git a/release_notes/known_issues.rst b/release_notes/known_issues.rst new file mode 100644 index 0000000..07c5be6 --- /dev/null +++ b/release_notes/known_issues.rst @@ -0,0 +1,149 @@ +Known problems and limitations +============================== + +* Application crash might occur on the data publication in the study if both data server and CPP container + are running in the standalone mode. + + +* Sometimes regression test bases give unstable results; in this case the testing should be restarted. + + +* SALOME in general supports reading of documents from earlier versions but the documents created in the + new version may not open in earlier ones. However, some studies may work incorrectly in SALOME 9x; mainly + it concerns studies with Post-Pro data in which med v2.1 files have been imported. Due to removal of med + v2.1 support and deprecation of Post-Pro module in SALOME series 9x, there can be problems with opening + of such studies in SALOME. + + +* Compilation of OCCT by Makefiles on a station with NVIDIA video card can cause problems because the installation + procedure of NVIDIA video driver removes library ``libGL.so`` included in package libMesaGL from directory + ``/usr/X11R6/lib`` and places this library ``libGL.so`` in directory ``/usr/lib``. However, libtool expects to + find the library in directory ``/usr/X11R6/lib``, which causes compilation failure (See ``/usr/X11R6/lib/libGLU.la``). + We suggest making symbolic links in that case using the following commands (*Note: you need root permission to do this*): + + .. code-block:: bash + + $ ln -s /usr/lib/libGL.so /usr/X11R6/lib/libGL.so + $ ln -s /usr/lib/libGL.la /usr/X11R6/lib/libGL.la + + +* ParaVis and Mesh modules work unstably using a remote connection. You can use VirtualGL to benefit from the remote + graphic card (launch vglrun salome), or use mesa_salome to bypass the graphic card (but it is slower). For ParaVis, + you can also launch pvserver in the remote desktop and connect to it from your local computer. Finally, clusters + often provide their own solution to access visualization nodes for remote post-processing. Ask the cluster's support + for dedicated information. + + +* For the current moment, because of the ParaView application architecture limitations, ParaVis module has the + following known limitations: + + * ParaVis module works unstably using a remote connection; when SALOME is running on a remote computer, activation + of ParaVis module can sometimes lead to the application hang-up. + + * Different visual artifacts may take place in ParaView or VTK viewer when using a remote connection; this is a + limitation of indirect rendering: ParaView uses OpenGL 2.0 backend which some features are not supported by indirect + rendering. + + * ParaVis module compilation can fail on 64-bit platforms when building ParaMEDCorba plugin (due to crash of kwProcessXML + tool during generation of the plugin documentation). In such case it is necessary to unset ``VTK_AUTOLOAD_PATH`` + environment variable and restart the compilation, for example: + + .. code-block:: bash + + $ unset VTK_AUTOLOAD_PATH + + * Loading big files in ParaVis might render SALOME instable. This problem is expected to be fixed in one of the next + releases; it can be temporarily avoided in the current version by applying one of the two solutions below: + + * In ParaVis settings (ParaView tab -> RenderView tab), increase the amount of memory under "Remote/Parallel rendering + options" to something bigger than the default 20 MB (for example 200 MB). + +* ParaView application may crash during start-up on Linux because of graphics card driver's limitations. The following + workaround may help solving this issue: + + .. code-block:: bash + + $ export VTK_DISABLE_VISRTX=1 + $ export VTK_DISABLE_OSPRAY=1 + +* Med library (medfichier) can read only MED files of version 2.2 and newer. + +* Users can experience OpenGL issues when running SALOME on virtual machines or with Intel graphic chipset. If such + issue occurs, use run_mesa_salome.bat to launch SALOME. + +* For Windows 10 operating system, the Microsoft Visual C++ Redistributable for Visual Studio 2017 is required. It can + be downloaded from the official Microsoft site: + + https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads + + For convenience, the distributable is included into the SALOME archive as well. + +* Because of the known 8192 character command line limit, On Windows, the installation directory should be as short as + possible, e.g. ``C:\SALOME-9.10.0``.On Linux and Windows, the installation folder should not contain spaces or + special characters. + + +* There are known issues about behavior of the automatic link between Shaper and Mesh. The behavior will not be optimal + if several iterations between the two modules are done by the user. + +* When invoking context help from dialogs of Shaper module, an error message can be observed in the case of using old + versions of Firefox as the default browser: + + .. code-block:: bash + + PCOMGlueLoad error for file /usr/lib64/firefox/libxul.so: + /usr/lib64/firefox/libxul.so: undefined symbol: FT_Palette_Select + Couldn't load XPCOM. + + This error message happens, for instance, with Firefox v75. The problem is caused by incompatibility of freetype + library, shipped with SALOME, with old versions of Firefox. The problem is not reproduced with newer versions of + Firefox (e.g. v89). To solve mentioned problem, we suggest installing latest version of Firefox, or using other + browser (e.g. Chrome) as the default one. + + +* Users can experience problem with launching SALOME because of absence of Python 3. For SALOME, Python 3 is a + mandatory pre-requisite. It is available as a native package on most of Linux distributions, so if you experience + this problem, just install the corresponding package. For example, on Debian or Ubuntu: + + .. code-block:: bash + + $ apt install python3 + $ update-alternatives --install /usr/bin/python python /usr/bin/python3 1 + + If you aren’t able to install Linux packages (e.g. because of lack of permissions), you can use one of the following + workarounds: + a) Source environment file supplied with SALOME distribution: + + .. code-block:: bash + + $ . env_launch.sh + $ salome + + b) Generate bash script and use it as a launcher instead of default one: + + .. code-block:: bash + + $ ./install_bin.sh + $ sat launcher SALOME-9.11.0 --exe runSalome.py -n salome.sh + $ salome.sh + +* There is a known problem with saving / loading big studies. The problem is caused by SALOME architecture and CORBA + used as the transport between components. CORBA has 2 GB data transfer limit, so one may experience a problem with + saving / loading big studies in default mode. This problem can be partially bypassed by using “multi-file” save-mode. + + +* SALOME version 9.7 introduced a “Session Less” mode allowed using SALOME API without launching CORBA servers. There + is a known limitation that “session less” and “standard” modes cannot be mixed in the same session as this may cause + various artifacts. + + +* On Fedora 32 and 34 platforms, users can experience issue displaying SALOME icons. The issue can be resolved as + follows: + + .. code-block:: bash + + $ dnf install qt5ct + $ export QT_QPA_PLATFORMTHEME=qt5ct + $ qt5ct + + Then, in qt5ct interface, choose "Fusion" instead of "Adwaita" or "Breeze" that are causing some issues. diff --git a/release_notes/new_features_v9_12.rst b/release_notes/new_features_v9_12.rst new file mode 100644 index 0000000..679d45a --- /dev/null +++ b/release_notes/new_features_v9_12.rst @@ -0,0 +1,108 @@ +New Features and Improvements +============================= + +GEOM +---- + +* Memory communication between SHAPER and GEOM + + Implemented four new Python API methods (two in GEOM and two in SHAPER) to exchange XAO + data through memory buffer, avoiding physical files creation on disk. + + SHAPER: + + .. code-block:: python + + buffer = model.exportToXAOMem(doc, selection, author, geometry_name) + Import_1 = model.addImportXAOMem(doc, buffer) + + GEOM: + + .. code-block:: python + + buffer = geompy.ExportXAOMem(shape, [groups], [fields], author) + (status, shape, [sub_shapes], [groups], [fields]) = geompy.ImportXAOMem(buffer, name_for_publication_in_study) + + + +* Dump Shape Internal Data + + The existing method KindOfShape from the Python API of the GEOMETRY module + was extended to support more different types of edge geometry and with more parameters. + Additionally supported curve types are: + + * Bézier Curve + * B-Spline Curve + * Hyperbola + * Parabola + + For other already supported curve types, the KindOfShape method returns additional parameters, + like e.g. the normal of a circle/ellipse/arc. + + +SHAPER +------ + +* Sketch middle point constrain should create point if missing + + The middle point constrain now creates the middle point if it does not exists. + +* Non planar faces + + Added the ability to build non-planar faces from non-planar input data (wire or closed set of edges) + in SHAPER using exact the same face feature. + +* Filters on group + A new filter has been added that selects all types of geometry (solid, face, edge, vertex). + It searches for matches by pattern (which is a regular expression) among all available + result names in SHAPER + + +MESH +---- + +* Decompose Viscous Layer API + + TODO + +* Generate mesh of faces of volume elements + + Add the possibility to create all face elements in a volumetric mesh. + +* SMESH controls Jacobian + + New quality metric "Scaled Jacobian" is now available. + The Scaled Jacobian is a scalar quantity to be displayed with a scalar color bar for the min and + max values registered on the mesh. This metric is available in menu Controls -> Volume Control. + + .. image:: images/v9_12_scaled_jacobian.png + :alt: Scaled Jacobian quality control + +* SMESH parallel multinodes + + TODO + + +Other +----- + +* YACS tests work with SSL + + TODO + +* YACS proxy mechanism for big objects transferred + + TODO + +* Fix in MedCoupling for GetCellContainingPoints + + TODO + +* MedCoupling fix for interpolation P1P0 for hexa mesh + + TODO + +* MedCoupling Basic Iterative + + TODO +