This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
tile_server [2020/08/10 17:51] yves created |
tile_server [2025/11/13 17:03] (current) 195.16.27.44 |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Tile server included ====== | + | ====== Local tile server included ====== |
| A tile server is a piece of software that can break down large images into smaller pieces, at a specified resolution. The resulting "pieces" are referred as "tiles". | A tile server is a piece of software that can break down large images into smaller pieces, at a specified resolution. The resulting "pieces" are referred as "tiles". | ||
| Line 9: | Line 9: | ||
| You can learn more about [[https://realdata.pathomation.com/what-whole-slide-images-wsis-are-made-of/|how this process works on our blog]], where we explain why [[https://realdata.pathomation.com/what-whole-slide-images-wsis-are-made-of/|tile servers are essential to tackle digital pathology data streaming bottlenecks]]. | You can learn more about [[https://realdata.pathomation.com/what-whole-slide-images-wsis-are-made-of/|how this process works on our blog]], where we explain why [[https://realdata.pathomation.com/what-whole-slide-images-wsis-are-made-of/|tile servers are essential to tackle digital pathology data streaming bottlenecks]]. | ||
| - | ** Combine PMA.core and PMA.start ** | + | ** Discover PMA.core ** |
| - | PMA.core is PMA.start's big brother. It supports more storage options, offers security options, and manages slide meta-data. | + | [[https://www.pathomation.com/pims/ce/|PMA.core]] is PMA.start's big brother. It is a powerful image management software technology that supports all network and cloud storage options, has CE-IVD certification, offers user management, manages slide meta-data like annotations. |
| - | PMA.start and PMA.core can perfectly go together, and we have many satisfied customers that have built ecosystems that exploit the features of both. | ||
| - | Here are two use cases worth highlighting: | ||
| - | * A research group at a major hospital runs a central PMA.core server to validate new protocols with clinicians. Meanwhile, individual developers run PMA.start on their local (Linux) workstations, in combination with our ImageJ (Java) plugin, to develop new algorithms before they are pushed into the production environment | ||
| - | * A life science company allows PMA.start to be used on individual users' computers, so that they can quickly evaluate local slide content, typically delivered from outside collaborating groups. PMA.start allows for local viewing of slides, without the need to push these slides onto a central server first. | ||