Skip to content

High disk usage #11

@soichih

Description

@soichih

This app currently creates a large output file (track.tck), but it also leaves large amount of intermediate output files.

-rw-r--r-- 1 hayashis hayashis   67109140 Jan 12 08:03 wm.mif
-rw-r--r-- 1 hayashis hayashis   85630244 Jan 12 08:03 dwi.mif
-rw-r--r-- 1 hayashis hayashis   15808893 Jan 12 08:03 dt.mif
-rw-r--r-- 1 hayashis hayashis      82607 Jan 12 08:03 brainmask.mif
-rw-r--r-- 1 hayashis hayashis      82607 Jan 12 08:03 sf.mif
-rw-r--r-- 1 hayashis hayashis    2635044 Jan 12 08:03 fa.mif
-rw-r--r-- 1 hayashis hayashis         45 Jan 12 08:04 response.txt
-rw-r--r-- 1 hayashis hayashis   15808893 Jan 12 08:04 lmax2.mif
-rw-r--r-- 1 hayashis hayashis   39521806 Jan 12 08:05 lmax4.mif
-rw-r--r-- 1 hayashis hayashis   73773790 Jan 12 08:05 lmax6.mif
-rw-r--r-- 1 hayashis hayashis  118564846 Jan 12 08:07 lmax8.mif
-rw-r--r-- 1 hayashis hayashis  282733427 Jan 12 08:11 wm_tensor.tck
-rw-r--r-- 1 hayashis hayashis  273706654 Jan 12 08:12 csd_lmax2_wm_SD_PROB.tck
-rw-r--r-- 1 hayashis hayashis  298399402 Jan 12 08:13 csd_lmax4_wm_SD_PROB.tck
-rw-r--r-- 1 hayashis hayashis  304275370 Jan 12 08:13 csd_lmax6_wm_SD_PROB.tck
-rw-r--r-- 1 hayashis hayashis  301887838 Jan 12 08:14 csd_lmax8_wm_SD_PROB.tck
-rw-r--r-- 1 hayashis hayashis  355744948 Jan 12 08:15 csd_lmax2_wm_SD_STREAM.tck
-rw-r--r-- 1 hayashis hayashis  339183784 Jan 12 08:16 csd_lmax4_wm_SD_STREAM.tck
-rw-r--r-- 1 hayashis hayashis  312402760 Jan 12 08:16 csd_lmax6_wm_SD_STREAM.tck
-rw------- 1 hayashis hayashis       9927 Jan 12 08:17 stderr.3015105.m2.log
-rw-r--r-- 1 hayashis hayashis  291279292 Jan 12 08:17 csd_lmax8_wm_SD_STREAM.tck
-rw-r--r-- 1 hayashis hayashis 2759610145 Jan 12 08:19 track.tck
-rw------- 1 hayashis hayashis       3475 Jan 12 08:19 stdout.3015105.m2.log
-rw-r--r-- 1 hayashis hayashis          2 Jan 12 08:20 finished

matlab2's scratch volume is currently 92% full, and most of the disk usage comes from storing output from this app generated within the last 30 days or so. I am wondering if this app can be updated to remove those intermediate files after track.tck is generated (maybe some metadata can be captured - file size, stream count, etc.. before removal - if it''s useful..)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions