I want to filter image modality alowed to be received by a storescp process. I think this may be achieved using the configuration file option of storescp, in the file I will allow only the file I want to received (e.g MR image).

I copy the storescp.cfg file for directory /etc and start the storescp with the following command line

Code:

StoreScp.exe --fork -sp -xf storescp.cfg GenericStorageSCP 104

but I got this error:
Error: unknown configuration profile name: GENERICSTORAGESCPI check that a profile with this name GENERICSTORAGESCP exist and it is ok (execpt the case)

What's the right way to use storescp with a config file ? what do I miss ?

A general description about the file's format comes in the file asconfig.txt, which is also available online. without checking, there is some fiddling usually with case sensitivity. For now, try all possibilities We should then comment in the example file and storescp documentation what is the right way to do it.

Yes, I read the description of the file. I tried to use the file provided with dcmtk and it did not work .. Isn't it tested ?

Michael Onken wrote:

without checking, there is some fiddling usually with case sensitivity. For now, try all possibilities We should then comment in the example file and storescp documentation what is the right way to do it.

As you can see, the profile "GENERICSTORAGESCP" is declared in the file with the right case (uppercase)

Quote:

P.S: Why you posted this under "Other DICOM Tools"?

when I searched the forum t osee if someone else have or had in the past the same problems, I saw that the post related to storescp/stroscu (nearly all *scp | * scu in fact) when in this forum so I posted also here....[/code]

but it find the use of "default" in the configuration file a bit disturbing...
When I read this, I just think that if no profile was entered, it would use the one specified by the "default" statement..

but it find the use of "default" in the configuration file a bit disturbing... When I read this, I just think that if no profile was entered, it would use the one specified by the "default" statement..

There are at least two reasons for this behavior:

"Default" is just a symbolic name that has no further meaning.

The command line class that is used for parsing the command line options only allows for a fixed number of values after an option, e.g. --config-file <filename> <profile>.

"Default" is the just the name chosen by the original author of that file. It could be also any other string, you can exchange it to "Dummy" or whatever you like. It has no special meaning, e.g. it is not choosen automatically - you always have to specify the profile that should be used, there is no "fall back" called Default or the like.