steve
Senior Member
Posts:1885
 |
| 2010-08-28 12:59 AM |
|
We're glad to announce that we've finally posted a Community Preview of our new Silverlight viewer integrated into the ImageServer on the web site for download! We're calling the software our Webstation. It has many of the same features as our Workstation, but running in a web browser.
Here's a few notes about the release:
- You can access the main information page here.
- This release is an Alpha release. The release will not attempt to upgrade over the top of an official release of the ImageServer. It must be installed on a dedicated system and we will not support automatic upgrades from the install.
- If you are unable to install the software, but still want to see what it can do, we have posted a few YouTube videos showing the Webstation's functionality. You can see them on the main information page.
- We have put together complete documentation of the Webstation features and have integrated it into the ImageServer's User's Guide. At this time we have not posted the documentation on our site, but it is available as always after installing the software from the Start menu.
- If your client does not have Silverlight installed, a link should be displayed to download it the first time you attempt to access the viewer from the ImageServer's GUI.
- The Webstation will run under Safari on a Mac, after installation of Silverlight 4.
- With the addition of the Webstation functionality, the ImageServer does require more server side resources. A copy of the core Workstation is running within the ImageServer's ShredHostService for each client that connects to the Webstation and suitable resources must be available on the server to handle each of the clients utilizing the Webstation.
- The source for the Webstation is not publicly available at this time. We do plan to open source the code, but it will be some time before it is available.
- We do not at this time have a target date for the next official ImageServer release containing the Webstation functionality.
As always, we really are looking for your feedback on our new creation! Please post any feedback on the Beta Testers Forum. We really want to hear your feedback on the product so we can make it better.
The ClearCanvas Team.
|
|
| Real-time support available to Clinical Edition and Team Edition customers |
|
|
image
Veteran Member
Posts:104
|
| 2010-08-28 01:30 AM |
|
Hello CC Team,
Excellent I like it ...........Now i will go for deeply test.
Best Regards
Image |
|
|
|
|
sezerpal
Veteran Member
Posts:113
|
| 2010-09-04 04:24 PM |
|
That is what we expected from you. First class job. Even works on mac :)
Sezer |
|
|
|
|
doxgy
New Member
Posts:1
|
| 2010-09-04 11:41 PM |
|
Thanks for the good things that the team has developed a version of good to us.
I have tested with. Vibharam Hospital, Thailand.
This has been a good response from doctor. Them say; Not different from the software business.
Important, we can define or select level. Resolution of the display or not.
To the quality, I mean lossless compression level.
For to see in the network hospitals.
Cheer for all the development team.
Take care and Health of all concerned.
Shiva P.
Vibharam Hospital, Thailand. |
|
|
|
|
steve
Senior Member
Posts:1885
|
| 2010-09-07 01:37 AM |
|
Shiva,
There's two configuration options related to the compression used in the WebViewer. One option, CompressionType, sets the format we use transmitting images to the client. The default value is "jpeg", but it also can be set to "png". The second option, JpegQualityFactor, sets the quality factor for images when the CompressionType is set to "jpeg". The default value for this is 80.
We did some experimentation with using png, which is lossless, but the performance wasn't that great. Having a very fast network makes it better, but feel free to experiment and see for yourself.
The quality factor obviously also has an impact on performance, but it can affect image quality. Note that right now we are compressing the image with the overlays on the image, so a lower quality factor will cause some artifacts around the overlay text.
Steve |
|
| Real-time support available to Clinical Edition and Team Edition customers |
|
|
Paul.Tracy
New Member
Posts:3
|
| 2010-09-14 10:41 AM |
|
Hi,
The hospital I work for are currently looking at the Workstation, standalone, connected up to an AGFA PACS back end and are very impressed. Are there plans for a standalone WebStation version to enable the same sort of set-up? Also Any ideas on a code release date?
Many thanks
Paul |
|
|
|
|
steve
Senior Member
Posts:1885
|
| 2010-09-15 01:15 AM |
|
Paul,
As described in the User's Guide, the ImageServer backend to the Webstation can be setup to function as a "temporary cache". I'm not quite sure what you're implying by "stand-alone", but it certainly can be used in a mode where its not your permanent archive.
As for code release, I'm not quite sure, but it will be a ways off.
Steve |
|
| Real-time support available to Clinical Edition and Team Edition customers |
|
|
isheo@ru-se.com
Basic Member
Posts:15
|
| 2010-09-15 04:17 AM |
|
Our hospital have Agfa Pacs. We install clearcanvas image server+webstation as temporary cache and whe configure agfa pacs to route all images to him. After that we link our ris to webstation to preview images. Works fine. |
|
|
|
|
Paul.Tracy
New Member
Posts:3
|
| 2010-09-16 09:33 AM |
|
That sounds exactly like what I want to try out. I would really appreciate if you could let me know how you went about configuring this setup.
Thanks
Paul |
|
|
|
|
steve
Senior Member
Posts:1885
|
| 2010-09-16 11:42 AM |
|
Paul,
The ImageServer is setup to function as a temporary cache when you install it. The User's Guide for the ImageServer has a small section that discusses this in the section Features/Filesystem Disk Management Support.
Steve |
|
| Real-time support available to Clinical Edition and Team Edition customers |
|
|
isheo@ru-se.com
Basic Member
Posts:15
|
| 2010-11-18 04:41 PM |
|
When install webstation as cache to use it webviwer you must tell to your main pacs to route dicom files to webstation. |
|
|
|
|
Elickson
New Member
Posts:4
|
| 2010-11-23 09:18 AM |
|
Could you pls tell me how to change compress rate of the image in Webstation viewer?
Is it possible that user can change compress rate dynamically? |
|
|
|
|
steve
Senior Member
Posts:1885
|
| 2010-12-02 09:47 AM |
|
The Alpha version of the Webstation does not change the compression rate dynamically. The JPEG quality factor is set in the configuration file and cannot be changed . We have done some fiddling with dynamically adjusting the compression ratios for the final release, but its not determined yet if we will include that code in the final release.
In any case, if you want to change the JPEG quality factor for the Alpha release, search for JpegQualityFactor in the ShredHostService's configuration file. The default quality factor is 80.
Steve |
|
| Real-time support available to Clinical Edition and Team Edition customers |
|
|
shastrik
New Member
Posts:8
|
| 2010-12-03 12:37 PM |
|
I just installed and was able to login to imageserver and send some images but I cannot view images. I am getting the following error when I click view images button. "Could not establish connection to net.tcp//localhost:4520/ApplicationServices" I am on Windows Vista and .NET TCP Port sharing service has been enabled. Any suggestions ?
Ken |
|
|
|
|
shastrik
New Member
Posts:8
|
| 2010-12-03 01:02 PM |
|
Incidentally, this is the ClientAccessPolicy.xml file. The firewall is off
|
|
|
|
|
DM
Advanced Member
Posts:35
|
| 2010-12-10 09:26 AM |
|
Has anyone had an issue where you stay on the login page even though you have logged in successfully?
It won't redirect to any other page and when I explicitly navigate to another page for example /Pages/Studies/ I am being redirected back to the login page:
http://IP_OF_SERVER/ImageServerAlpha/Pages/Login/Default.aspx?ReturnUrl=%2fImageServerAlpha%2fPages%2fStudies%2fdefault.aspx |
|
|
|
|
steve
Senior Member
Posts:1885
|
| 2010-12-13 10:48 AM |
|
We've had this happen a few times in the past with users. We've thought in the past it was because of the session timing out right away after login, due to inconsistencies with the time settings on client and server. Have you tried logging in from the server console (where this problem shouldn't exist)? Also, have you looked at all at the logs in the "web" folder of the install directory?
Steve |
|
| Real-time support available to Clinical Edition and Team Edition customers |
|
|