[Swift-user] swift on midway: apps and modules

[Michael Wilde]

Instead of /scratch/local try /scratch/midway/nbest

I suspect the error here is that you are setting the workdirectory to  path that is not shared between the login host and compute nodes.

If /scratch/midway/nbest works (and thus confirms this suspicion), and you still want to place your work directory on a node-local filesystem, you can try to turn on "coaster staging".  To do that, set the work directory back to /scratch/local, and in your properties file (in the "cf" file generated by the bin/runswift command in the RCC tutorial examples) change:

  use.provider.staging=true

to

  use.provider.staging=true

Now your input data files will be copied to the node /scratch/local dir and your output files copied back.

I just tested this using the workdirectory /scratch/local/wilde/swiftwork, which seemed to work, but I did not check everything carefully yet.

- Mike


----- Original Message -----
> From: "Neil Best" <nbest at ci.uchicago.edu>
> To: "David Kelly" <davidk at ci.uchicago.edu>
> Cc: swift-user at ci.uchicago.edu
> Sent: Monday, December 3, 2012 6:07:17 PM
> Subject: Re: [Swift-user] swift on midway: apps and modules
> On Thu, Nov 29, 2012 at 5:04 PM, David Kelly <davidk at ci.uchicago.edu>
> wrote:
> > Hi Neil,
> >
> > It could possibly be something environmental. Are the modules loaded
> > automatically when you log in through your .bashrc? If they are not
> > already, could you give that a try?
> >
> > If that doesn't work, try editing sites.xml and try changing
> >
> > <workdirectory>/scratch/local/swift</workdirectory>
> > to
> > <workdirectory>/project/joshuaelliott/narr</workdirectory>
> >
> > Then try the run again and let me know when it's finished. That will
> > just make some extra debugging information available that might
> > better explain why it's failing.
> >
> > Thanks,
> > David
> >
> 
> 
> Everything was basically working except that my project directory
> became too cluttered with temp files so I changed the workdirectory
> back to /scratch/... and now swift is failing with that "exit code
> 127" message again. What's the correlation between workdirectory and
> module/PATH problems? Or is there something else going on here?
> _______________________________________________
> Swift-user mailing list
> Swift-user at ci.uchicago.edu
> https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-user

-- 
Michael Wilde
Computation Institute, University of Chicago
Mathematics and Computer Science Division
Argonne National Laboratory