[SAGA-RG] adapter should mkdir working_directory?

[Thilo Kielmann]

This sounds like reasonable behavior.

However, it MUST be documented. And I wonder if this is something that
could be implementation-specific or better not?
Do we have to add a gazillion of "what happens if" in the SAGA spec??? 
If not, will SAGA applications ever be portable across implementations???

Thilo

On Fri, Jul 10, 2009 at 06:39:18AM +0200, Andre Merzky wrote:
> From: Andre Merzky <andre at merzky.net>
> To: Hartmut Kaiser <hkaiser at cct.lsu.edu>
> Cc: 'SAGA RG' <saga-rg at ogf.org>
> Subject: Re: [SAGA-RG] adapter should mkdir working_directory?
> 
> Quoting [Hartmut Kaiser] (Jul 10 2009):
> > 
> > > I'm Yutaka Kawai @KEK, woriking for SAGA adapter implementation for
> > > NAREGI and PBS.
> > > 
> > > I have a question about adapter behavior for working_directory. If a
> > > user specify a working_directory in the job description but the
> > > directory does not exist, what is the suitable adapter's behavior?
> > > Should the adapter throw "DoesNotExist"? or mkdir the directory for the
> > > job? In the case of the current NAREGI, it mkdir the working directory
> > > in constructing its WFML. On the other hand, PBS does not. I want to
> > > decide whether adapters absorb the difference or not. Could you tell me
> > > the case of LFC also?
> > 
> > I'm not aware of any rule implemented by all existing job adaptors, but I
> > think creating the directory is a viable solution as it improves the users
> > experience and makes SAGA easier to use. 
> 
> +1
> 
> Cheers, Andre.
> 
> -- 
> Nothing is ever easy.
> --
>   saga-rg mailing list
>   saga-rg at ogf.org
>   http://www.ogf.org/mailman/listinfo/saga-rg



-- 
Thilo Kielmann                                 http://www.cs.vu.nl/~kielmann/