The echoscp application implements a Service Class Provider (SCP) for the
Verification service class. It listens for
incoming association requests on the specified port, and once an association
@@ -129,7 +129,7 @@
The echoscu application implements a Service Class User (SCU) for the
Verification service class. It establishes an
association with a peer Application Entity (AE), sends a
@@ -131,7 +131,7 @@
The following example shows what happens when it is successfully run on
an SCP at IP 127.0.0.1 and listen port 11112 that supports the
Verification service:
The following example shows what happens when it is successfully run on
an SCP at IP 127.0.0.1 and listen port 11112 that supports the
Query/Retrieve (Find) service:
When using the -k keyword option it becomes possible to specify the
query dataset (the Identifier) without needing to create a DICOM file.
Multiple instances of -k can be used to build up the Identifier. For
@@ -290,7 +290,7 @@
The getscu application implements a Service Class User (SCU) for
the Query/Retrieve service class. It requests an
association with a peer Application Entity and once established, sends a C-GET
@@ -141,7 +141,7 @@
The following example shows what happens when it is successfully run on
an SCP at IP 127.0.0.1 and listen port 11112 that supports the
Query/Retrieve (Get) service:
When using the -k keyword option it becomes possible to specify the
query dataset (the Identifier) without needing to create a DICOM file.
Multiple instances of -k can be used to build up the Identifier. For
@@ -276,7 +276,7 @@
When using the -k keyword option it becomes possible to specify the
query dataset (the Identifier) without needing to create a DICOM file.
Multiple instances of -k can be used to build up the Identifier. For
@@ -113,7 +113,7 @@
The movescu application implements a Service Class User (SCU) for
the Query/Retrieve service class and optionally
a Service Class Provider (SCP) for the Storage
@@ -145,7 +145,7 @@
The following example shows what happens when it is successfully run on
an SCP at IP 127.0.0.1 and listen port 11112 that supports the
Query/Retrieve service with the default Move Destination AE title
@@ -194,7 +194,7 @@
When using the -k keyword option it becomes possible to specify the
query dataset (the Identifier) without needing to create a DICOM file.
Multiple instances of -k can be used to build up the Identifier. For
@@ -318,7 +318,7 @@
The movescu application supports the Query/Retrieve service classes as an
SCU and the Storage service as an SCP (with the --store option). The
following SOP classes are supported:
The qrscp application implements a Service Class Provider (SCP) for the
Verification, Storage and Query/Retrieve
service classes. It listens for incoming association requests on the
@@ -155,7 +155,7 @@
The qrscp application uses a configuration file format compatible with the
-configparser Python module. The [DEFAULT] section contains the
+configparser Python module. The [DEFAULT] section contains the
configuration options for the application itself while all other sections
are assumed to be definitions for the Query/Retrieve service’s Move
Destinations: