Here is an overview of what we consider to be the key website statistics and information:
| Parameter name | Status | Comment |
|---|---|---|
| Website meta title | Pydicom | | Search engines recommend title length of around 50-60 characters. The length of this title is 9. |
| Meta description | Pydicom Dicom (Digital Imaging in Medicine) is the bread and butter of medical image datasets, storage and transfer. This is the future home of the Pydicom documentation. If you are a Python developer looking to get started with Dicom and Python, this will be the place to learn and contribute! For now, here are some helpful links, and general plan for some of the code bases in the organization. If you want to come and chat, find our community on Gitter, or post an issue on one of our repos.ModulesPydicomIf you want to work with dicom datasets, you should use pydicom. We have started a base of docs here, and see the docs on readthedocs for you to get started.Pynetdicompynetdicom3 is where you want to start if you want to create Service Class Providers (SCPs) or Service Class Users (SCUs). These are the little servers/processes that echo/store/move/find dicom datasets around. This is the bread and butter of the protocol, and is based on the original pynetdicom. We will soon be consolidating these two so that it is less confusing.Deiddeid is a simple module and client that can handle coding (replacement of identifiers) with a study alias. See the documentation base for getting started.Applicationssendit is an example Dockerized web application to recive Dicom images, deidentify using your API (and deid, above), and then send off to different storage locations. This application is under development, and not yet ready for use. See the documentation for details.dicom-database is a simlpified version of sendit, intended for local management of DICOM. This application is under development.ContainersWe will be developing different dicom applications that are container-based. This means using Docker and Singularity to easily deploy servers (more suited for Docker), and general tools and applications (Singularity is more suited for tools on shared resources).Getting Started ContainersDicom-Containers serves equivalent Singularity and Docker containers for working with dicom tools and pydicom. Specifically: getting-started serves a Docker and Singularity container,each of which is a “quick start” image that you can build to easily start using some basic tools for working with dicom files. Currently, the image installs the Dicom ToolKit, along with miniconda3 installed with pydicom and pynetdicom3. pydicom-docs is a container that builds sphinx docs, intended for developers of pydicom that want a solution to develop docs that doesn’t require installing additional dependencies.Dicom ScraperDicom Scraper is a tool under development to detect burned-in pixel annotations with ORC, and remove them. Currently, the Dockerized application is using an older version of scipy and python 2*, and this will be updated. The detection is working relatively good and will still need some testing and tweaking.APIsDicom CookiesAs a new person to Dicom, I found it hard to find and programatically download a quick (and maybe fun?) Dicom dataset. Toward this goal, I created a statically served Dicom Cookies dataset. The human readable entrypoint is here, and you can see it being used programatically here.Coming SoonWe will be creating a set of web application (Dockerized) to be deployed in different cloudy places to work with Dicom. If you are interested in this, please join the effort! Welcome to Pydicom May 29, 2017 We are happy to announce that the new Pydicom site is underway! Pydicom is an effort to bring together a... Previous Next Site last generated: Jul 18, 2017 | To make sure all the meta description is visible in search results page, Google recommends length of up to 320 characters at the most. This description has exactly 3757 characters. |
| Load time | 0.2492 seconds on average | Website load speed is pretty fast. |
| Total links on homepage | We found 52 links | This is a normal amount of links. |
| Page HTML size | 22.6KB | Load speed (and overall responsiveness) is such an important factor for both search engines and user experience, would you not agree? With that in mind, this is a very good result. |
| Website server | Server appears to be online. The IP address for the server is 151.101.113.147. | It's unfortunate, but despite our best attempts, we failed to gather enough data to provide a meaningful insight at this time. |
What, all that information was not enough? You want... more? Right, then. You asked for it.
Similarly to how a hard drive or a modern SSD device holds your files, a server holds all the files the website needs to operate. To load a webpage, your browser needs to contact the said server and request files - strings of code that make up the website into what it is, including images, text and database entries. Each physical server has a unique IP address that is used by the browser to contact it.
Let's see what technical information we've managed to gather:
| Header in detail |
|---|
HTTP/1.1 200 OK Server: GitHub.com Content-Type: text/html; charset=utf-8 Strict-Transport-Security: max-age=31557600 Last-Modified: Tue, 18 Jul 2017 17:20:06 GMT Access-Control-Allow-Origin: * Expires: Thu, 28 Dec 2017 20:11:44 GMT Cache-Control: max-age=600 X-GitHub-Request-Id: 91CC:30DF:111EF04:1A41090:5A454DA8 Content-Length: 22838 Accept-Ranges: bytes Date: Thu, 28 Dec 2017 20:01:44 GMT Via: 1.1 varnish Age: 0 Connection: keep-alive X-Served-By: cache-hhn1548-HHN X-Cache: MISS X-Cache-Hits: 0 X-Timer: S1514491304.259366,VS0,VE92 Vary: Accept-Encoding X-Fastly-Request-ID: 62bc3f594e8d5e6ee9091f908110d6f558a09fb2 |
A good domain address is usually one that is easy to spell, resulting in the smallest amount of mistypes possible. Still, such a thing inevitably happens. Here is a list with the most frequent 1703 mistypes, associated with pydicom.github.io:
If you are curious about what TLD extensions could also match the domain name of pydicom.github.io well, we have prepared an extensive list for you to look through:
We are glad you have finished this report. Hopefully, you found what you were looking for. In case you need more information to compare, here is a list of some other detailed overviews we have prepared: