Context Navigation

Changes between Version 5 and Version 6 of Software/Mira

v5	v6
20	20	Anyway, its easy to fix. Add -MI:somrnl=0 to your command line (anywhere works I think, I did it right after the -job command).
21	21
22		Another thing Mira doesn't like is NFS mounted directories - such as the mykopat grid. As far as I understand it, if several computers need to communicate during an assembly, Mira fears it will slow down by a factor of 10 or more. On the grid, this can be circumvented by forcing the grid to run the job on only one machine. Add #$ -q *@my-mgrid2 (or whatever machine is most suited for this) to the initial list of commands in your job and Mira should decide you are not running on a NFS system.
	22	Another thing Mira doesn't like is NFS mounted directories - such as the mykopat grid. As far as I understand it, if several computers need to communicate during an assembly, Mira fears it will slow down by a factor of 10 or more. On the grid, this can be circumvented by forcing the grid to run the job on only one machine. Add #$ -q *@my-mgrid2 (or whatever machine is most suited for this) to the initial list of commands in your job and Mira should decide you are not running on a NFS system. If it persists in claiming your on NFS, you can add -MI:sonfs=no to the command line, telling it to override the NFS abortion. As long as you have told Mira to only run on one machine, it will not have any NFS-related problems, even though the software itself might still think so.