On Mon, Dec 21, 2009 at 11:48 AM, Simon King <simon.k...@nuigalway.ie> wrote: > Hi Minh! > > On 21 Dez., 19:38, Minh Nguyen <nguyenmi...@gmail.com> wrote: > [...] >> When something like this happens, it is likely the problem is related >> to NFS, especially disk I/O on an NFS mounted disk. To minimize >> disruption, one should use the directory /scratch on sage.math. > > Thank you! So, I will use /scratch instead.
Note that the main advantage of /home is that it is "snapshoted" and backed up regularly. /scratch is also rsync'd to /disk/scratch regularly, which is also "snapshoted". > >> For >> more guidelines on minimizing disruption on the Sage cluster, see the >> guidelines [1] on the Sage wiki. >> >> [1]http://wiki.sagemath.org/SageClusterGuidelines > > I think that the computations that I currently do concern sage > development: It is about finite groups whose modular cohomology can't > be computed with the current p_group_cohomology spkg; the purpose of > these computations is to find ways to make it better, and similar > computations a month ago actually resulted in a bug report to > Singular. I hope this matches the scope of sage.math > > Best regards, > Simon > > -- > To post to this group, send an email to sage-devel@googlegroups.com > To unsubscribe from this group, send an email to > sage-devel+unsubscr...@googlegroups.com > For more options, visit this group at > http://groups.google.com/group/sage-devel > URL: http://www.sagemath.org > -- William Stein Associate Professor of Mathematics University of Washington http://wstein.org -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
