Sam way as with unpacksdcmdir, ie, by specifying  -run run subdir format stemname Another way it to use the -auto-runseq format , eg -auto-runseq mgz this will output all the runs preprending the run number and protocol name If you are using 7.3.X, then you can also add --dcm2niix which will speed things up a lot

On 9/23/2022 8:26 AM, O'Dor, Sarah,PHD wrote:

Good afternoon,

Quick question about unpacking:

The instructions I have from a previous staff member said to do this:

In folder where files are going, type: unpacksdcmdir -src <location of scans> -targ . -scanonly scanout.txt

So what I submit is:

unpacksdcmdir -src /cluster/archive/338/siemens/Prisma_fit-67026-20220208-132737-000260 -targ . -scanonly scanout.txt

When I do that, it just makes the files:

dicomdir.sumfile scanout.txt  unpack.log

I’m trying to use the dcmunpack command instead. From following the template on the website, I’ve been trying the following commands:

[pandas:Pandas57UC] (nmr-stable6-env) dcmunpack -src /cluster/archive/338/siemens/Prisma_fit-67026-20220208-132737-000260 -index-out dcm.index.dat

{lots of other content here, so let’s skip to….}

dcmunpack done

[pandas:Pandas57UC] (nmr-stable6-env) dcmunpack -src /cluster/archive/338/siemens/Prisma_fit-67026-20220208-132737-000260 -index-in dcm.index.dat -targ .

ERROR: need input runs

How should I specify input runs?

Thanks,

Sarah

---

Freesurfer mailing list Freesurfer@nmr.mgh.harvard.edu https://mail.nmr.mgh.harvard.edu/mailman/listinfo/freesurfer