Data Access

From CNI Wiki
Revision as of 01:48, 12 May 2011 by imported>Rfbowen (Created page with "For the time being, dirmonitor and pfilemonitor are the two ever-running processes that manage moving data from cnimr to cnirt in an organized format. Should data stop showing u...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

For the time being, dirmonitor and pfilemonitor are the two ever-running processes that manage moving data from cnimr to cnirt in an organized format.

Should data stop showing up at any time, a variety of things could have been to blame. Perhaps the mount of the pfile or dicom directories reset or is absent, or someone may have reset the scanner (or maybe even cnirt).

To check if dirmon is running, try: ps aux | grep dirmon

You should see something like: cni 31446 6.8 29.3 3769888 3616544 ? Sl May09 200:00 /usr/bin/python ./dirmonitor.py

To check if pfilemon is running, try: ps aux | grep pfilemon

You should see something like: cni 15878 97.2 0.0 41548 8648 ? Rl 12:45 350:59 /usr/bin/python ./pfilemonitor.py

Pfiles are located on the mount: /net/cnimr/export/home/signa/research/mrraw/

Dicoms are located on the mount: /net/cnimr/export/home1/sdc_image_pool/images

If you can ls both of those, you're in good shape.

Assuming you want to reset whatever happens to be not working (be it dirmon or pfilemon), use a killall and re-initialize it.

If you aren't getting dicoms/niftis try: killall -9 dirmonitor.py /home/cni/dirmonitor/dirmonitor.py &

If you aren't getting pfiles try: killall -9 pfilemonitor.py /home/cni/dirmonitor/pfilemonitor.py