1. www.eu-eela.org E-science grid facility for Europe and Latin America E2GRIS1 Francisco Prieto (PhD), Maria Boton, Raul Priego – CETA- CIEMAT Itacuruça (Brazil), 2-15 November 2008 PORTING APPLICATIONS TO THE GRID. THE gLite WORKLOAD MANAGEMENT SYSTEM

2. www.eu-eela.org E-science grid facility for Europe and Latin America 1. INTRODUCTION TO WMS  1.1 OVERVIEW OF THE WORKLOAD MANAGEMENT SYSTEM  1.2 JOB PREPARATION  1.3 JDL. THE JOB DESCRIPTION LANGUAGE  1.4 SPECIAL JOBS  1.5 JOB SUBMISSION AND STATUS MONITORING 2. APPLICATIONS PORTING  2.1 PROBLEM ANALYSIS  2.2 GRID IMPLEMENTATION  2.3 PORTING EXAMPLE CONTENTS

3. www.eu-eela.org E-science grid facility for Europe and Latin America 1 INTRODUCTION TO WMS In order to accomplish these tasks, the WMS implements the following services  1.1 OVERVIEW OF THE WORKLOAD MANAGEMENT SYSTEM I 1) Job submission 2) Job execution according to prescribed schemes (match-making) 3) Job status monitoring 4) Retrieval of execution output WMS COMMITMENTS The purpose of the Workload Management System (WMS) is to accept user jobs, to assign them to the most appropriate Computing Element, to record their status and retrieve their output. The Resource Broker (RB) is the machine where the WMS services run From the gLite 3.1 User guide:

4. www.eu-eela.org E-science grid facility for Europe and Latin America The Resource Broker (RB) in gLite 3.0, WMS in version 3.1 1 INTRODUCTION TO WMS  1.1 OVERVIEW OF THE WORKLOAD MANAGEMENT SYSTEM III WMS CONTEXT IN THE gLITE INFRASTRUCTURE InformationService Logging & Book-keeping

5. www.eu-eela.org E-science grid facility for Europe and Latin America 1 INTRODUCTION TO WMS  1.1 OVERVIEW OF THE WORKLOAD MANAGEMENT SYSTEM IV WMS GRID INTERACTIONS a) Information Service b) LFC Catalogue c) Logging and Bookkeeping (LB) d) Policy Management Systems WMS USER INTERACTION IN JOB SUBMISSION a) WMS b) Computing Element c) Worker Node WMS INTERACTIONS

6. www.eu-eela.org E-science grid facility for Europe and Latin America 1 INTRODUCTION TO WMS  1.1 OVERVIEW OF THE WORKLOAD MANAGEMENT SYSTEM V WMS INTERACTIONS IN THE gLITE INFRASTRUCTURE b) Job Submitted. In the JDL one or more files to be copied from the UI to the WN can be specified, and these are initially copied to RB An event is logged in the LB and the status of the job is SUBMITTED. c) WMS looks for the best available CE to execute the job. To do so, it interrogates the Information Supermarket (ISM), an internal cache of information which in the current system is read from the BDII, to determine the status of computational and storage resources, and the File Catalogue to find the location of any required input files. Another event is logged in the LB and the status of the job is WAITING. d) The gLite WMS prepares the job for submission, creating a wrapper script that will be passed, together with other parameters, to the selected CE. An event is logged in the LB and the status of the job is READY. e) The CE receives the request and sends the job for execution to the local LRMS. An event is logged in the LB and the status of the job is SCHEDULED. f) The LRMS handles the execution of jobs on the local Worker Nodes. The Input Sandbox files are copied from the gLite WMS to an available WN where the job is executed. An event is logged in the LB and the status of the job is RUNNING. i) If the job ends without errors, the output (not large data files, but just small output files specified by the user in the so called Output Sandbox) is transferred back to the gLite WMS node. An event is logged in the LB and the status of the job is DONE j) At this point, the user can retrieve the output of his job to the UI. An event is logged in the LB and the status of the job is CLEARED.

7. www.eu-eela.org E-science grid facility for Europe and Latin America WM a) Web service Interface WM Proxy b) Task queue b) Match-Maker system c) Information SuperMarket 1 INTRODUCTION TO WMS  1.1 OVERVIEW OF THE WORKLOAD MANAGEMENT SYSTEM VI LOGGING AND BOOK-KEEPING a) Register every WMS action (in particular job actions) b) Accounts for job status WMS ELEMENTS

8. www.eu-eela.org E-science grid facility for Europe and Latin America 1 INTRODUCTION TO WMS Basically, a repository of resource information available only in read mode to the matchmaking engine Information SuperMarket Task queue system Possibility to keep a submission request for a while if no resources are immediately available.  1.1 OVERVIEW OF THE WORKLOAD MANAGEMENT SYSTEM VII Match-making mechanism The matchmaker has the goal to find the best suitable CE where to execute the job To accomplish this task, the WMS interacts with the other EGEE/LCG components (Replica location Service, and Information Service) There are three different scenarios to be dealt with separately: a) Direct job submission b) Job submission without data-access requirements c) Job submission with data-access requirements

9. www.eu-eela.org E-science grid facility for Europe and Latin America A WM can adopt different policies to schedule a job: Two job submission models (accordingly to user requests and site policies) : 1 Eager scheduling (PUSH): The job is bound to a resource as soon as possible. Once a given decision has been taken, the job is passed to the selected resource for execution. 2 Lazy scheduling (PULL): a job is held by the WM until a resource becomes available. When this happen, the resource is matched against the submitted jobs. Intermediate approaches are also possible 1 INTRODUCTION TO WMS Batch Schedule policies.  1.1 OVERVIEW OF THE WORKLOAD MANAGEMENT SYSTEM VIII

10. www.eu-eela.org E-science grid facility for Europe and Latin America 1 INTRODUCTION TO WMS  1.1 OVERVIEW OF THE WORKLOAD MANAGEMENT SYSTEM IX

11. www.eu-eela.org E-science grid facility for Europe and Latin America The following information needs to be specified when a job has to be submitted: 1) Job characteristics 2) Job requirements and preferences on the computing resources 3) Software dependencies 4) Job data requirements 1 INTRODUCTION TO WMS  1.2 JOB PREPARATION This information is specified using a Job Description Language (JDL) Based upon Condor’s CLASSified ADvertisement language (ClassAd) Hence, JDL allows the definition of a set of attributes which are taken into account by WMS when making its scheduling decision

12. www.eu-eela.org E-science grid facility for Europe and Latin America 1 INTRODUCTION TO WMS  1.3 JDL- THE JOB DESCRIPTION LANGUAGE I An attribute is the pair (key, value), where the value might be an integer, string, boolean, etc. = ; Comments must either be preceded by (#) or follow the C++ syntax JDL is case sensitive to tabs and white spaces In case values as strings, these must be enclosed in double quotes and backslash (\) Arguments= “\”Hello World!\” 10”; Special characters, such as &, |,, are only allowed through the following syntax: Arguments = “-f file1\\\&file2” Single quotes “’” are not allowed

13. www.eu-eela.org E-science grid facility for Europe and Latin America 1 INTRODUCTION TO WMS  1.3 JDL- THE JOB DESCRIPTION LANGUAGE II JobType (optional field) –Normal (simple, sequential) –Interactive –MPICH –Checkpointable –Partitionable –any combination of these Examples: JobType=“Interactive”; JobType={“MPICH”,”Checkpointable”}; “Interactive” + “MPICH” not allowed JDL FIELDS

14. www.eu-eela.org E-science grid facility for Europe and Latin America Executable –Command, script or program to be sent to the GRID for execution. –User can specify an executable located in a remote CE or in the UI (the executable must be included in the InputSandBox). Examples: Executable={“/grid/ceta/testrungdir/RunTrayectory.sh”}; Executable={“RunTrayectory.sh”}; InputSandbox={“/home/fprieto/GRID_TEST/RunTrayectory.sh”} 1 INTRODUCTION TO WMS  1.3 JDL- THE JOB DESCRIPTION LANGUAGE III

15. www.eu-eela.org E-science grid facility for Europe and Latin America Arguments (optional) String where all arguments needed for the execution are specified. Example: If the “sum” takes N1 and N2 as arguments: $sum N1 N2 –output output.out In the JDL: Executable=“sum”; Arguments={“N1 N2 –output output.out”}; 1 INTRODUCTION TO WMS  1.3 JDL- THE JOB DESCRIPTION LANGUAGE III

16. www.eu-eela.org E-science grid facility for Europe and Latin America Environment (optional) Environment variables needed for a proper execution Example: Environment={“JAVABIN=/usr/local/java”}; 1 INTRODUCTION TO WMS  1.3 JDL- THE JOB DESCRIPTION LANGUAGE IV

17. www.eu-eela.org E-science grid facility for Europe and Latin America StdInput (optional) –Standard input of job execution StdOutput (optional) –Standard output of job execution StdError (opcional) –Standard error for job execution Examples: StdOutput = "message.txt"; StdError = "stderror"; 1 INTRODUCTION TO WMS  1.3 JDL- THE JOB DESCRIPTION LANGUAGE IV

18. www.eu-eela.org E-science grid facility for Europe and Latin America InputSandbox (optional) –List of files, located at the UI, needed for job execution –Every listed file will be automatically sent to the remote resource Example: InputSandbox={“my-script.sh”,”/tmp/cc.sh”}; OutputSandbox (optional) –List of files generated after execution which are intended to be retrieved Example: OutputSandbox={“std.out”,”std.err”,”points.data”}; 1 INTRODUCTION TO WMS  1.3 JDL- THE JOB DESCRIPTION LANGUAGE V

19. www.eu-eela.org E-science grid facility for Europe and Latin America VirtualOrganisation (optional) –VO name which the user belong to Example: VirtualOrganisation={“ceta”}; 1 INTRODUCTION TO WMS  1.3 JDL- THE JOB DESCRIPTION LANGUAGE V

20. www.eu-eela.org E-science grid facility for Europe and Latin America 1 INTRODUCTION TO WMS  1.3 JDL- THE JOB DESCRIPTION LANGUAGE VI Requirements (optional) –Computational resources needed by the job –Requirements are specified by using the GLUE schema attributes issued through the Information Service –If no requirements are given, the default configuration values of the UI are set: Default.Requirements=other.GlueCEStateStatus==“Production”; Examples: Requirements=other.GlueCEUniqueID==“grid006.cecalc.ula.ve:2119/jobmanager-pbs-infinite”; Requirements=Member(“ALICE-3.07.01”, other.GlueHostApplicationSoftwareRunTimeEnvironment);

21. www.eu-eela.org E-science grid facility for Europe and Latin America Rank (optional) –float point expression to classify the CEs matching the intended requirements –The Rank expression might hold the attributes describing the CE in the Information System (IS) –Rank field evaluation is performed by the Resource Broker during the “match-making” process –The higher the numeric value, the better the Rank –When Rank is not set, the default UI configuration value is used: Default.Rank=other.GlueCEStateFreeCPUs; 1 INTRODUCTION TO WMS  1.3 JDL- THE JOB DESCRIPTION LANGUAGE VII

22. www.eu-eela.org E-science grid facility for Europe and Latin America 1 INTRODUCTION TO WMS  1.3 JDL- THE JOB DESCRIPTION LANGUAGE VIII InputData (optional) –List of Logical File Names (LFNs) or Grid Unique Identifiers (GUIDs) representing the input files needed for a job execution –This list is used by the Resource Broker to find a CE from where those files can be accessed more efficiently Example: InputData={“lfn:cmstestfile”,”guid:135b7b23-4a6a-11d7-87e7-9d101f8c8b70”};

23. www.eu-eela.org E-science grid facility for Europe and Latin America DataAccessProtocol (needed if InputData has been specified) –Protocol or list of protocols used by the application to access the files listed in the InputData of a given SE. –Not all the SEs handle the same set of protocols (gridftp, file, rfio …) Example: DataAccessProtocol={“file”,”gridftp”}; 1 INTRODUCTION TO WMS  1.3 JDL- THE JOB DESCRIPTION LANGUAGE IX

24. www.eu-eela.org E-science grid facility for Europe and Latin America 1 INTRODUCTION TO WMS  1.3 JDL- THE JOB DESCRIPTION LANGUAGE X OutputData (optional) –This field allows the user to retrieve the register and automatic load of the output data generated in the Worker Node (WN) and stored in a Storage Element (SE) –Its main attributes are:  OutputFile  StorageElement  LogicalFileName OutputFile (needed if OutputData is specified) –Represents the output file name, generated at the W which needs to be registered and loaded by the WMS in a SE.

25. www.eu-eela.org E-science grid facility for Europe and Latin America StorageElement (optional) –It represents the SE URI where the output file specified in the attribute OutputFile will be load by the WMS LogicalFileName (optional) –It represents the LFN associated to the output file to be addressed in the catalogue. 1 INTRODUCTION TO WMS  1.3 JDL- THE JOB DESCRIPTION LANGUAGE XI

26. www.eu-eela.org E-science grid facility for Europe and Latin America 1 INTRODUCTION TO WMS  1.3 JDL- THE JOB DESCRIPTION LANGUAGE XII StorageIndex (neede if InputData and OutputData are specified) –It represents the StorageIndex Service URL to be contacted in order to solve the names of the files specified in InputData and/or OutputData Example: StorageIndex=“https://glite.org:9443/StorageIndex”;https://glite.org:9443/StorageIndex OutputSE (optional) –It represents the SE URL where output data is intended to be stored. –This attribute is used by the Resource Broker to find the “closest” CE to the specified SE and, hence, planning execution there. Example: OutputSE=“grid003.cecalc.ula.ve”;

27. www.eu-eela.org E-science grid facility for Europe and Latin America Example 1 The resource needs PBS as LRMS having at least 2 CPUs Requirements=other.GlueCEInfoLRMSType==“PBS” && other.GlueCEInfoTotalCPUs>1 ; (Notice that attribute names are preceded by other.) Example 2 Resource must have the specified software installed (this information is published in the resource environment) Requirements=Member(“CMSIM-133”, other.GlueHostApplicationSoftwareRunTimeEnvironment); RunTimeEnvironment is a multiple value attribute The Member operator returns “true” if the given value exists in the RunTimeEnvironment list 1 INTRODUCTION TO WMS  1.3 JDL- THE JOB DESCRIPTION LANGUAGE XIII JDL EXAMPLES

28. www.eu-eela.org E-science grid facility for Europe and Latin America Example 3 The job must be executed in a CE belonging to cern.ch Requirements=(RegExp(“cern.ch”, other.GlueCEUniqueID)); 1 INTRODUCTION TO WMS  1.3 JDL- THE JOB DESCRIPTION LANGUAGE XIV

29. www.eu-eela.org E-science grid facility for Europe and Latin America Example 4 The job requires at least 25 minutes of CPU time and 100 minutes of real time Requirements = other.MaxCPUTime>=1500 && other.MaxWallClockTime>=6000; 1 INTRODUCTION TO WMS  1.3 JDL- THE JOB DESCRIPTION LANGUAGE XV Example 5 The resource must have 2 packages installed (VO-alice-Alien y VO-alice-Alien-v4-01-Rev-01) and the job must be executed at least during 86000 seconds Requirements = Member(“VO-alice-Alien”, other.GlueHostApplicationSoftwareRunTimeEnvironment) && Member(“VO-alice-Alien-v4-01- Rev-01”, other.GlueHostApplicationSoftwareRunTimeEnvironment) && (other.GlueCEPolicyMaxWallClockTime > 86000);

30. www.eu-eela.org E-science grid facility for Europe and Latin America 1 INTRODUCTION TO WMS  1.4 SPECIAL JOBS I At the state of the art, parallel jobs can run inside single Computing Elements (CE) only; Several projects are involved into studies concerning the possibility of executing parallel jobs on Worker Nodes (WNs) belonging to different CEs MPI IMPLEMENTATION

31. www.eu-eela.org E-science grid facility for Europe and Latin America 1 INTRODUCTION TO WMS  1.4 SPECIAL JOBS II 1) the MPICH software must be installed and placed in the PATH environment variable on each WNs of the CE. 2) Some MPI’s applications require a shared filesystem among the WNs to run. The variable VO_ _SW_DIR will contain the name of a directory in case of SHARED filesystem. The variable VO_ _SW_DIR will contain “.” if there is NO SHARED filesystem. INSTALL: glite-MPI_utils at CE and Worker Nodes MPI Infrastructure Requirements

32. www.eu-eela.org E-science grid facility for Europe and Latin America From the user’s point of view, jobs to be run as MPI are specified setting the JDL JobType attribute to MPICH and specifying the NodeNumber attribute as well Example: JobType = “MPICH”; NodeNumber = 4; When the previous two attributes are included in a JDL, the User Interface (UI) automatically adds the following expression to the JDL Requirements expression in order to find out the best resource where the job can be executed. (other.GlueCEInfoTotalCPUs >= NodeNumber) && Member (“MPICH”,other.GlueHostApplicationSoftwareRunTimeEnvironment) 1 INTRODUCTION TO WMS  1.4 SPECIAL JOBS III MPI Usage

33. www.eu-eela.org E-science grid facility for Europe and Latin America Type = "Job"; JobType = "MPICH"; Executable = “cpi"; NodeNumber = 2; StdOutput = “cpi.out"; StdError = “cpi.err"; InputSandbox = {"cpi"}; OutputSandbox = {“cpi.err",“cpi.out"}; RetryCount = 0; 1 INTRODUCTION TO WMS  1.4 SPECIAL JOBS IV MPI Example:

34. www.eu-eela.org E-science grid facility for Europe and Latin America 1 INTRODUCTION TO WMS  1.4 SPECIAL JOBS V A job collection is a set of independent jobs that user wants to submit and monitor via a single request Jobs of a collection are submitted as DAG nodes without dependencies JDL is a list of classad, which describes the subjobs Type = "collection"; VirtualOrganisation = “gilda"; nodes = { [ ], … }; JOB Collections

35. www.eu-eela.org E-science grid facility for Europe and Latin America type = "collection"; InputSandbox = {"date.sh"}; RetryCount = 0; nodes = { [ file ="jobs/job1.jdl" ; ], [ Executable = "/bin/sh"; Arguments = "date.sh"; Stdoutput = "date.out"; StdError = "date.err"; OutputSandbox ={"date.out", "date.err"}; ] ], [ file ="jobs/job3.jdl" ; ] }; 1 INTRODUCTION TO WMS  1.4 SPECIAL JOBS VI Job Collection Example:

36. www.eu-eela.org E-science grid facility for Europe and Latin America -A parametric job is a job where one or more of its attributes are parameterized Values of attributes vary according to a parameter Example: JobType = "Parametric"; Executable = "/bin/sh"; Arguments = "md5.sh input_PARAM_.txt"; InputSandbox = {"md5.sh", "input_PARAM_.txt"}; StdOutput = "out_PARAM_.txt"; StdError = "err_PARAM_.txt"; Parameters = 4; ParameterStart = 1; ParameterStep = 1; OutputSandbox = {"out_PARAM_.txt", "err_PARAM_.txt"}; -Job monitoring / managing is always done through an unique jobID, as if the job was single (see submission of collection - Parameter can be also a list of string 1 INTRODUCTION TO WMS  1.4 SPECIAL JOBS VII Parametrized Jobs

37. www.eu-eela.org E-science grid facility for Europe and Latin America 1 INTRODUCTION TO WMS  1.4 JOB SUBMISSION AND STATUS MONITORING I glite-wms-job-submit [–r ] [-c ] [-vo ] [-o ] where: -r the job is submitted directly to the computing element identified by -c the configuration file is pointed by the UI instead of the standard configuration file -vo the Virtual Organisation (if user is not happy with the one specified in the UI configuration file) -o the generated edg_jobId is written in the Useful for other commands, e.g.: glite-wms-job-status –i (or edg_jobId) -i the status information about edg_jobId contained in the are displayed

38. www.eu-eela.org E-science grid facility for Europe and Latin America glite-wms-job-list-match Lists resources matching a job description The --rank option prints the ranking of each resource Performs the matchmaking without submitting the job glite-wms-job-cancel Cancels a given job glite-wms-job-status -i jobid (--noint) Displays the status of the job glite-wms-job-get-output --dir output -i jobid (--noint) Returns the job-output (the OutputSandbox files) to the user glite-wms-job-get-logging-info Displays logging information about submitted jobs (all the events “pushed” by the various components of the WMS) Very useful for debug purposes (see next slide) 1 INTRODUCTION TO WMS  1.4 JOB SUBMISSION AND STATUS MONITORING II USEFUL UI COMMANDS

39. www.eu-eela.org E-science grid facility for Europe and Latin America –Which quantities are expected to be obtained in the study? –Identify the stages of the process to obtain such quantities and intermediate results/files –Which is the input data (parameters, input files, etc)?. Can the input data be partitioned to generate different configurations? (data partitioning) –Starting from the same input data, is there an stage where the intermediate products can be partitioned? (process partitioning) – Which elements should be stored? (estimate the volume of data) –What success policies apply? (retry counts etc) –How will output data be treated? (post-processing) THESE RESULTS MUST GUIDE THE GRID IMPLEMENTATION 2 PORTING APPLICATIONS TO THE GRID. HANDS ON  2.1 PROBLEM ANALYSIS I

40. www.eu-eela.org E-science grid facility for Europe and Latin America 2 PORTING APPLICATIONS TO THE GRID  2.1 PROBLEM ANALYSIS II From the preceding analysis, it must be determined the nature of the jobs. Jobs can be: 1) Independent 2) Dependent 1) Non-interactive 2) Interactive

41. www.eu-eela.org E-science grid facility for Europe and Latin America –Generation of configuration space  Set of all entities which constitute an analysis??  (model parameters, initial conditions, other) –Job executions tasks:  Send jobs to the GRID infrastructure  Monitor job status according to the configuration space –Storage  Storage large files at the SE. Use specific LFN  GRID Federated database interaction? –Navigation over results/retrieve  According to the configuration space and the success policies 2 PORTING APPLICATIONS TO THE GRID  2.2 GRID IMPLEMENTATION I

42. www.eu-eela.org E-science grid facility for Europe and Latin America BUILD-UP A GLOBAL DESIGN!! 2 PORTING APPLICATIONS TO THE GRID  2.2 GRID IMPLEMENTATION II 2) Which elements are needed for job execution at: a) UI b) WN c) SE (big files) d) Metadata at AMGA (DB) 3) How these elements interact? 1) What is a job? (what is executed?) 4) How is the output treated?

43. www.eu-eela.org E-science grid facility for Europe and Latin America  2.3 PORTING EXAMPLE I 2 PORTING APPLICATIONS TO THE GRID ANALYSIS OF THE PHASE SPACE OF THE FORCED NONLINEAR PENDULUM GOAL REQUIREMENTS Orbits integrated in time for different parameter values in order to find patterns in the phase space (such as attractors) Java Bash Commons Org Apache math libraries PARTITION SCHEME The parameter space is partitioned. Then for each point of this space, an orbit is numerically integrated,

44. www.eu-eela.org E-science grid facility for Europe and Latin America  2.3 PORTING EXAMPLE II 2 PORTING APPLICATIONS TO THE GRID At the UI At the WN Stored in SE Wrapper, executable,JDL’s, etc configuration files executable wrapper...

45. www.eu-eela.org E-science grid facility for Europe and Latin America GENERATE CONFIGURATIONS  2.3 PORTING EXAMPLE III 2 PORTING APPLICATIONS TO THE GRID TO WN 1 TO WN 2

46. www.eu-eela.org E-science grid facility for Europe and Latin America  2.3 PORTING EXAMPLE IV 2 PORTING APPLICATIONS TO THE GRID External Library Configuration Files Executable Output File Associated LFN to SE with LFN

47. www.eu-eela.org E-science grid facility for Europe and Latin America Type = "Job"; JobType = "Normal" Executable = "’/bin/bash’"; Arguments = {"RunTrayectory.sh,ParamsSweep.conf ParamsName.conf IC.conf Integrator.conf omegaXX_muYY"}; StdOutput = "std.out"; StdError = "std.err"; InputSandbox = {"/GridTest/Scrpits/RunTrayectory.sh","/GridTest/jarfile/OrbitIntegrator.jar","/GridTest/conf/ParamsSw eep.conf","/GridTest/conf ParamsName.conf","/GridTest/conf/IC.conf","/GridTes/conf/Integrator.conf","/GridTest/lib/commons- math-1.2.jar"}; OutputSandbox = {"std.out","std.err","OrbitName","Orbit.log"}; THE JDL FOR THIS PROBLEM glite-wms-job-submit -o JOBID.id /temp/jdl/JDL_omegaXX_muYY.jdl glite-wms-job-status -i JOBID --noint JOB SUBMISSION JOB STATUS MONITORING JOB RETRIEVE glite-wms-get-output --dir output -i JOBID.id --noint  2.3 PORTING EXAMPLE V 2 PORTING APPLICATIONS TO THE GRID

48. www.eu-eela.org E-science grid facility for Europe and Latin America GENERATING AMGA ENTRIES  2.3 PORTING EXAMPLE VI 2 PORTING APPLICATIONS TO THE GRID ORBITS ARE NAVIGATED LATER THROUGH AMGA QUERIES: Query> omega=2.0 mu=02. Associated LFN obtain this file from the SE

49. www.eu-eela.eu Itacuruça (Brazil), E2GRIS1, 2.11.2008 – 15.11.2008 Questions … 2 THANKS Dr. Francisco Prieto Castrillo, Science and Technology Unit Coordinator, CETA-CIEMAT