If for some reason, a very large set of source code files needs to be maintained, too large to fit in home space, then camp space should be used. This space can be used for quite a long time, up to 90 days. If your development cycle including debugging takes longer than three months, there is a fundamental flaw in your approach. Raw files that are produced by the computer, libraries, executables, output files, and data files for computational codes should be kept on camp disks if they are needed regularly by many people for a long time, like the executables of group software. If such files are needed only for a single debug run, they can be stored appropriately on a scratch disk.
Disk quotas are in place on all home disks, to keep data deterioration under control.
Students are allocated 15 Mbytes, Post-doctoral fellows 25 MBytes and external associates and visitors 5 MBytes. Group software repositories are allocated as much as needed. Exceptions can and will be made for good reason. Its main purpose is to store permanent data that is needed on those machines all the time, such as libraries of object modules and executables compiled for the architecture of these machines. This category is for storing the results and data files needed for a project and as a holding place for moving data to and from tape.