JSAGA

1) SAGA specification enable this, but of course it also depends on each adaptor.

You ask for the requirements with SAGA job description attributes. Relevant attributes for MPI should be SPMDVariation, TotalCPUCount, NumberOfProcesses and ProcessesPerHost.

Try "jsaga-job-run --help" for a quick list of available attributes, and see SAGA specification (http://www.ogf.org/documents/GFD.90.pdf) from page 168 to 174 for a more detailed description of these attributes.

2) The only thing you can ask for is the SPMDVariation (e.g. MPI, MPICH1, MPICH2...).

3) The command jsaga-jobcollection-run takes a JSDL (http://www.ogf.org/documents/GFD.56.pdf) file instead of SAGA job description attributes.

You can submit parametric jobs using notation @{INDEX}, as shown in this example:
https://cvs.in2p3.fr/gridpub/jsaga/jsaga-engine/test/resources/jobcollection/test_simple/job.xml?rev=1.1&content-type=text/x-cvsweb-markup

Other examples are available here:
https://cvs.in2p3.fr/gridpub/jsaga/jsaga-engine/test/resources/jobcollection/

But I have to tell you that this command is not SAGA-compliant, and it is also more complex and less used, hence probably less reliable than other commands...

Hello,

From the above post I conclude that it is not possible to pass custom requirements (e.g. CpuNumber or the so called VO tags) to the final JDL. Is this still true for new JSAGA releases (currently I am using version 0.9.10). If yes, is there a workaround to pass these non-standard requirements?

Thanks,
Daniel

Hi Daniel,

Yes, passing custom requirements is possible, but this depends on which plug-in is used.

Currently, this is supported for CREAM and WMS (see [http://grid.in2p3.fr/software/jsaga-dev/adaptors/jsaga-adaptor-wms/faq.html#jdl]).

Regards,
Sylvain