From 0cd27442afe1a43a3346772d8a3b1716079af4a2 Mon Sep 17 00:00:00 2001 From: "Lefebvre, Robert A." Date: Mon, 29 Sep 2025 12:07:13 -0400 Subject: [PATCH 1/2] Workbench - 5.6.0 --- LICENSE | 2 +- README.md | 32 ++++++++++++++++++++++++++------ Workbench-5.5.1.dmg | 3 --- Workbench-5.5.1.exe | 3 --- Workbench-5.5.1.tar.gz | 3 --- Workbench-5.6.0.dmg | 3 +++ Workbench-5.6.0.exe | 3 +++ Workbench-5.6.0.tar.gz | 3 +++ 8 files changed, 36 insertions(+), 16 deletions(-) delete mode 100644 Workbench-5.5.1.dmg delete mode 100644 Workbench-5.5.1.exe delete mode 100644 Workbench-5.5.1.tar.gz create mode 100644 Workbench-5.6.0.dmg create mode 100644 Workbench-5.6.0.exe create mode 100644 Workbench-5.6.0.tar.gz diff --git a/LICENSE b/LICENSE index 13a9534..66e3cee 100644 --- a/LICENSE +++ b/LICENSE @@ -1,4 +1,4 @@ -Copyright (c) 2017-2023, UT-Battelle, LLC +Copyright (c) 2017-2026, UT-Battelle, LLC All rights reserved [NEAMS Workbench] diff --git a/README.md b/README.md index d9f9504..0992d26 100644 --- a/README.md +++ b/README.md @@ -2,7 +2,7 @@ ## Whats in the bundle: - Workbench-5.5.1.{tar.gz,dmg,exe}: NEAMS Workbench release with integrated ParaView 5.6 visualization toolkit + Workbench-5.6.0.{tar.gz,dmg,exe}: NEAMS Workbench release with integrated ParaView 5.13 visualization toolkit ## Install NEAMS Workbench @@ -10,13 +10,33 @@ Install the platform-specific binaries. Linux binaries are available in TAR.GZ. Start the NEAMS Workbench. - Workbench-5.5.1/bin/Workbench Workbench-5.5.1.tar.gz (Linux) - Workbench-5.5.1.app/Contents/MacOS/Workbench Workbench-5.5.1.dmg (MacOS) - Workbench-5.5.1\bin\Workbench.exe Workbench-5.5.1.exe (Windows) + Workbench-5.6.0/bin/Workbench Workbench-5.6.0.tar.gz (Linux) + Workbench-5.6.0.app/Contents/MacOS/Workbench Workbench-5.6.0.dmg (MacOS) + Workbench-5.6.0\bin\Workbench.exe Workbench-5.6.0.exe (Windows) >Note: The first time a version of Workbench is started on your machine an install-specific environment is setup. This can take a few minutes, so please be patient. A message stating `Testing for python using ...` will be presented in the terminal from which Workbench has been launched. +## NEAMS Workbench 5.6.0 + +### Added: +- Support for language Server protocol workspace change watching +- Support for multi-tab stop autocompletion snippets +- Support for language server data plotting extension +- Python utility script for converting WASP schema files to Python objects in support of Python-based language server integration +- Support for SCALE2MCNP alternate SCALE run configuration +- Support for saving and loading plots from JSON-SPF format + +### Changed: +- Mac bundle from Intel to ARM architecture +- ParaView 5.6 to 5.13 +- PyARC v2.6.0 to v3.0.0 + +### Fixed: +- Mac file dialog issue by using non-native file dialog for file open and new operations +- Support for language server protocol onHover array responses + + ## NEAMS Workbench 5.5.1 ### Added: @@ -226,9 +246,9 @@ Newer Mac operating systems require applications to be certified and signed. The 1. Open a terminal and change directory into the root directory of the Workbench installation (E.g., /software/Workbench) 2. Remove the quarantine attribute from the Workbench executable - - `xattr -dr com.apple.quarantine /Applications/Workbench-5.5.1.app` + - `xattr -dr com.apple.quarantine /Applications/Workbench-5.6.0.app` 3. Execute Workbench - - `/Applications/Workbench-5.5.1.app/Contents/bin/Workbench` + - `/Applications/Workbench-5.6.0.app/Contents/bin/Workbench` ### Rerunning SetupRemote for MCNP after opening an MCNP input The issue here is that the MCNP language server is running in the background due to having opened an MCNP input. During the SetupRemote process a new copy of the language server will be retrieved and installed. On Windows, because the language server is in use, the SetupRemote step fails providing an error about the file being locked. This isn't a big deal because there is currently only one language server for MCNP, but because the SetupRemote fails the new configured parameters are not properly finalized. This typically occurs when you want to change the path to MCNP on the server (E.g., because you got the path wrong the first time). diff --git a/Workbench-5.5.1.dmg b/Workbench-5.5.1.dmg deleted file mode 100644 index 353ddd7..0000000 --- a/Workbench-5.5.1.dmg +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:f860a05b8703c243e84433752b53c12303e729bdf30e46c8e1711096f60da168 -size 836090530 diff --git a/Workbench-5.5.1.exe b/Workbench-5.5.1.exe deleted file mode 100644 index b29cfbd..0000000 --- a/Workbench-5.5.1.exe +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:6e8fe2da94e05810a870db040d884e6b1e03d126b2705d10761bc2b49a3cb651 -size 719283700 diff --git a/Workbench-5.5.1.tar.gz b/Workbench-5.5.1.tar.gz deleted file mode 100644 index 9c978d5..0000000 --- a/Workbench-5.5.1.tar.gz +++ /dev/null @@ -1,3 +0,0 @@ -version https://git-lfs.github.com/spec/v1 -oid sha256:28bd9501bcfeaf0395796fe2a45f1c199feb4cedb8d1b05e4901f3a1eea21845 -size 839352421 diff --git a/Workbench-5.6.0.dmg b/Workbench-5.6.0.dmg new file mode 100644 index 0000000..babc945 --- /dev/null +++ b/Workbench-5.6.0.dmg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:a06be327dd2ac21674e11c01f89c2d5718ae66994ff916f50e29eae3c81b77ff +size 1458634333 diff --git a/Workbench-5.6.0.exe b/Workbench-5.6.0.exe new file mode 100644 index 0000000..b17707d --- /dev/null +++ b/Workbench-5.6.0.exe @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:22d13a3017603ab88bd25f1ddfb747ab27003aaff32053bd16edc9a8853cac63 +size 1233293326 diff --git a/Workbench-5.6.0.tar.gz b/Workbench-5.6.0.tar.gz new file mode 100644 index 0000000..710f080 --- /dev/null +++ b/Workbench-5.6.0.tar.gz @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:49aa55cdcd7b94adea04f79789271c4be409ae82cae278ad3a0bbeeba4501fe7 +size 1482319367 -- GitLab From a093deffbf875e04fd096f9c7465960f63eac0b4 Mon Sep 17 00:00:00 2001 From: "Lefebvre, Robert Alexander" Date: Mon, 6 Oct 2025 17:30:16 +0000 Subject: [PATCH 2/2] Edit README.md to simplify the Mac quarantine steps --- README.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 0992d26..d9c79e4 100644 --- a/README.md +++ b/README.md @@ -244,10 +244,9 @@ For assistance and bug reporting, please email nwb-help@ornl.gov ### Mac cannot run Workbench because the developer cannot be verified Newer Mac operating systems require applications to be certified and signed. The Workbench team is working to support this new requirement, but in the meantime there is a workaround. After downloading and unzipping the Workbench-Darwin bundle perform the following steps: -1. Open a terminal and change directory into the root directory of the Workbench installation (E.g., /software/Workbench) -2. Remove the quarantine attribute from the Workbench executable +1. Remove the quarantine attribute from the Workbench executable - `xattr -dr com.apple.quarantine /Applications/Workbench-5.6.0.app` -3. Execute Workbench +2. Execute Workbench - `/Applications/Workbench-5.6.0.app/Contents/bin/Workbench` ### Rerunning SetupRemote for MCNP after opening an MCNP input -- GitLab