Package Details: weasis-bin 3.6.1-1
- View PKGBUILD / View Changes
|Git Clone URL:||https://aur.archlinux.org/weasis-bin.git (read-only, click to copy)|
|Description:||Weasis is a multipurpose DICOM viewer with a highly modular architecture|
|First Submitted:||2019-02-20 13:00|
|Last Updated:||2020-08-17 14:03|
Weasis Weasis is a free DICOM viewer which requires JAVA Runtime Environment 6 or later to run. To open a DICOM file here, you need to import it to this software first. View single file or multiple files in multiple frame tabs.
- Navigation Weasis Medical Viewer. Weasis is a multipurpose standalone and web-based DICOM viewer with a highly modular architecture.It is a very popular clinical viewer used in healthcare by hospitals, health networks, multicenter research trials, and patients.
- Trusted Mac download Weasis 3.6.2. Virus-free and 100% clean download. Get Weasis alternative downloads.
Required by (0)
ggnoredo commented on 2021-04-21 16:37
error: failed to parse srcinfo for 'weasis-bin-3.6.1-1': key 'groups' requires a value: Line 7: groups =
wcasanova commented on 2021-04-13 00:20
@junker it works please update the version and sha512sum as well since it is not the same
the .desktop is needed for the dicomizer binary
Weasis Dicom Viewer Free Download
Junker commented on 2021-02-20 04:12
version 3.7.0 is crashing.. : 570046 abort (core dumped) ./Weasis
check somebody please this PKGBUILD, if you don't have a segfault, i will update it.
Junker commented on 2019-09-17 06:14
hakim commented on 2019-09-17 01:34
Fresh install of Manjaro and the weasis-bin installer fails
install: cannot stat '/opt/Weasis/bin/Weasis.desktop': No such file or directory> ERROR: A failure occurred in package(). Aborting...
Any thoughts on how to install?
nroduit commented on 2019-08-25 16:30
From the version 3.5.3, the native installers (msi, deb, rpm, pkg) replace the weasis-portable.zip package and no longer requires Java to be installed on the system. It also serves as a basis for launching Weasis from a web context using the weasis protocol (https://nroduit.github.io/en/getting-started/weasis-protocol/).
See also https://groups.google.com/d/msg/dcm4che/3C84sscQqkQ/W2nvWma7AQAJ
Junker commented on 2019-08-21 12:40
arkoprovo1996 commented on 2019-08-21 11:59
Please add the line
in file 'viewer-linux.sh' (/opt/weasis-bin/viewer-linux.sh)
before the final line $JAVACMD ...
mzecher commented on 2019-05-21 01:59
Thanks for the package. It does however not work with jre11. I got it to run with jre10-openjdk
Tetrapyle commented on 2019-04-18 16:45
Please, I think you should replace:
in the PKGBUILD.
After having set up dcm4chee w/ TLS encryption and gleefully performing a few dcmsnds or dcmqrs, you may find yourself a bit frustrated to discover that Weasis no longer seems to work with dcm4chee via weasis-pacs-connector.
Note: This is a follow-up article to setting up dcm4chee w/ TLS. Also, the below has only been tested with dcm4chee2.x.
Weasis working with TLS (launched from dcm4chee-web3).
In my case, this was because the C-FIND’s that weasis-pacs-connector uses to tell Weasis the uri’s of the images it needs to download aren’t by default setup to use TLS. Opening up dcm4chee’s log, you should see some error’s to that effect. This is a bit frustrating given that weasis-pacs-connector runs on the *same box* *via* dcm4chee and so presumably shouldn’t need this extra layer of authentication. Alas this is not the case.
Luckily, weasis-pacs-connector does come with config options to enable TLS. However, I found the setup to be a bit tricky, as the config syntax differs greatly between the current weasis-pacs-connector version (the master branch found here), and v5.0.1 which is the latest pre-compiled version available on sourceforge, as of this writing, so I decided to write up some instructions.
Step 1: Download the correct properties file
The first step is to copy weasis-connector-default.properties from the correct branch of the weasis-pacs-connector git repo, rename it to weasis-pacs-connector.properties, and place this file in the appropriate folder according to your JBoss / Wildfly version, as described in the docs here.
On my system, running jboss inferior to version 7, the location is $DCM4CHEE/server/default/conf/.
If you are using weasis-pacs-connector v5.0.1, then the direct link to the properties file is here. If you are using the latest master branch version (which I am told will in the near future become v6.x), the link is here. Again, be careful to get this right as this file has changed quite a bit between v5.0.1 and the current latest version.
The next step differs based on your version of weasis-pacs-connector.
Step 2 for weasis-pacs-connector v5.0.1
If you’ve download the correct weasis-pacs-connect.properties file then this step will be rather self-explanatory, as the options related to turning on TLS are already referenced within this file. Simply uncomment / edit so that they match with the details of your install. My file looks like this:
Step 2 for weasis-pacs-connector “v6.x” / “current” master
Note: These are directions for the “latest” (at the time of this writing) version of weasis-pacs-connector grabbed directly from the master branch of the git repo (again, as it was at the time of this writing) and built from source. I have been told this version will soon become v6.x, however, as these instructions are against the ‘latest’ master which has not yet been tagged with an official release version, they may become quickly outdated. So take the below with a grain of salt and continue to refer to the official docs.
If you’ve already downloaded the correct weasis-connector-default.properties file the next step is to download dicom-dcm4chee.properties from the same git repo and plop it into the same directory as weasis-pacs-connector.properties. However you must rename it such that it is not named one of:
as these are *already* packaged with the weasis-pacs-connector war archive and the settings in these files (which do *not* enable TLS) will override your custom defined file if it has one these names. My file is named dicom-dcm4chee-local.properties.
Make the appropriate edits for your system. My file looks like:
Finally, open up weasis-pacs-connector.properties and make sure this file is properly referenced, like so:
Step 3: Restart dcm4chee
Weasis Viewer Download
Restart dcm4chee and open up a dicom archive w/ Weasis via dcm4chee-web3 or otherwise, it should now work w/ TLS.
Weasis Download Linux
- If you changed the AE title of your dcm4chee instance, make sure to make the appropriate adjustments in the weasis-pacs-connector config files. If this is the case Weasis will fail to load studies TLS mode or not.