Differences

This shows you the differences between two versions of the page.

--- start [2020/05/29 14:01]
charlotte
+++ start [2021/07/20 16:41]
81.82.195.9
@@ Line 1: / Line 1: @@
-====== PMA.core wiki start page ======
+====== PMA.core wiki ======
+PMA.core manages your whole slide images. It operates through web protocols and supports [[supported_file_formats|a number of file formats]], allowing you to manipulate WSI data from different vendors in a standardized manner. This enables efficient management of digital slide images while requiring minimal setup.
+{{::pma_core_dashboard.png?direct&600|}}
+==== PMA.core is a tile server ====
+PMA.core is foremost a tile server. Whole slide images are big, and an efficient scheme must be in place to optimally serve their content. PMA.core is that efficient solution.
+[[https://www.youtube.com/watch?v=sepPIexKELE|Our YouTube video tells you more about tile servers and whole slide images]]
+==== PMA.core offers a jumpstart into digital pathology ====
+PMA.core can be used as a foundation for applications that allow viewing and other operations such as annotations, data capture, and image analysis. PMA.core contains the necessary functions to retain these types of data, but by itself it does not provide end-user interfaces to create and manipulate it.
+The software acts as an [[honest broker|honest broker]] between the [[supported_file_formats|various vendor-dependent file formats]] on one end, and a variety of different end-user applications on the other:
-PMA.core operates through web protocols and supports a number of file formats, allowing you to manipulate WSI data from different vendors in a standardized manner. This enables efficient management of digital slide images while requiring minimal setup.
-PMA.core manages your whole slide images. It is not responsible for viewing and other operations such as annotations, data capture, and image analysis. While PMA.core contains the necessary functions to retain these types of data, it does not provide end-user interfaces to create and manipulate it. The software acts as a broker between the various vendor-dependent file formats on one end, and a variety of different end-user applications on the other:
-{{ :about.png?nolink&600 |}}
-The end-user applications are typically referred to as "downstream" applications in this manual. They can be other member-components of our platform (PMA.view is an excellent viewer), but they may be completely custom-built by third-parties as well (in which case communication with PMA.core is conveniently facilitated through webservices).
-This type of broker-like interaction  enables both downstream viewing and analysis. PMA.core allows adopters of WSI to build a context around each slide (on-slide graphical annotations and form-data) and manage this as needed.

PMA.core 3

User Tools

Site Tools

Differences

Page Tools