Presentation is loading. Please wait.

Presentation is loading. Please wait.

Babel F2003 Struct Support Update and FACETS integration Funded by DOE (TASCS) Grant No DE-FC02-07ER25805, DOE Grant No DE-FG02-04ER84099 and Tech-X Stefan.

Published byBarnaby Wiggins Modified over 9 years ago

Similar presentations

Presentation on theme: "Babel F2003 Struct Support Update and FACETS integration Funded by DOE (TASCS) Grant No DE-FC02-07ER25805, DOE Grant No DE-FG02-04ER84099 and Tech-X Stefan."— Presentation transcript:

1 Babel F2003 Struct Support Update and FACETS integration Funded by DOE (TASCS) Grant No DE-FC02-07ER25805, DOE Grant No DE-FG02-04ER84099 and Tech-X Stefan Muszala John Cary, Tom Epperly, Ammar Hakim, Scott Kruger, Gary Kumfert, Alexander Pletzer, Rooparani Pundaleeka, Srinath Vadlamani, Nanbor Wang January 17, 2008

2 Distcomp: One of the goals of the Distcomp work is to implement Fortran 2003 bindings in Babel for struct support. This work is aligned with the work of the Common Component Architecture (TASCS). What are the Tech-X scopes of the Distcomp and TASCS projects? TASCS: Part of the TASCS work is a collaboration with the FACETS* project in which we are integrating a C++ framework with Fortran modules (eventually Python, C). We are using the newly developed Fortran 2003 bindings in Babel to achieve our goal. * FACETS-( Framework Application for Core-Edge Transport Simulations ) is a SCIDAC project led by Tech-X which aims to integrate core, edge and wall fusion simulations.

3 FACETS+Babel integration only requires components at end of call chain

4 What work has been Completed? Distcomp: F2003 Implementation of Primitive Types in Babel. F2003 Implementation of Array Types in Babel. F2003 Implementation of R-array Types in Babel. TASCS work related to Fusion Projects: Have SIDL versions of FACETS Fortran Derived Types. Runs in a test FACETS Framework using R- arrays. Have SIDL prototype of FACETS interface which passes Babel struct from C++ to Fortran transport module Added timing infrastructure to test codes in order to compare with original (non-Babel) test code.

5 What still needs to be completed? Distcomp : Regression tests for F2003 structs. Includes all Fortran->”other language” combinations. Add examples - have some of these in Tech-X repo. Enumeration Types Documentation. Check pointer _init - (OK?) for non-static rarrays. Check pointer _destroy - (OK?) for non-static rarrays. Make sure copy works - (OK?) For non-static rarrays. _serialize/_deserialize for RMI calls. Provide access to every struct member. TASCS work related to Fusion Projects: Complete transport module interfaces. Continue working on SIDL interfaces for other modules.

6 package addRand version 1.0{ struct fStruct{ double bX; int bY; }; … } module addRand_fStruc use,intrinsic :: iso_c_binding type,bind(c) :: addRand_fStruct_t real(c_double) :: bX integer(c_int32_t) :: bY end type addRand_fStruct_t end module addRand_fStruct How we use BindC to provide Babel Primitive type capability in Babel Structs.

7 How we use BindC to provide Babel Array type capability in Babel Structs. package addRand version 1.0{ struct fStruct{ double bX; int iY; array testArr; }; class modStruct{ void doWork(in int n, inout fStruct structTest); } addRand::fStruct fTest; … for (size_t i = 0 ; i < N ; i++) { sidl_double__array_set1(fTest.testArr,i,double(i)); } … addRand::modStruct bS = addRand::modStruct:: _create(); bS.doWork(10,fTest); … type(addRand_fStruct_t) :: structTest ! inout … do i=0,structTest%iY call get(structTest%testArr, i, temp) call set(structTest%testArr,i,temp*5.0) enddo module addRand_fStruct use,intrinsic :: iso_c_binding use sidl_double_array type,bind(c) :: addRand_fStruct_t real(c_double) :: bX integer(c_int32_t) :: iY type(sidl_double_1d) :: testArr end type addRand_fStruct_t end module addRand_fStruct

8 We have used BIND© to provide two types of rarray support for C/F90 and C++/F90 struct bindings. SIDL struct flags{ … rarray glfIflagin(5); … } C++/C … double glfIflagin[5]; … FORTRAN … real(c_double)::glfIflagin(5) … Static R-Array

9 We have used BIND© to provide two types of rarray support for C/F90 and C++/F90 struct bindings. SIDL struct structTest{ … int iY; rarray structRaw(iY); // Probably don’t want: rarray structRaw(*); … } C++/C double *structRaw; real(c_double),dimension(:),pointer :: structTest_structRAW_fptr call C_F_POINTER(CPTR=structTest%structRAW, & FPTR=structTest_structRAW_fptr, & SHAPE=(/DIM/)) … do i=1,structTest%iY structTest_structRAW_fptr(i)=structTest_structRAW_fptr(i)+5.0 enddo module addRand_fStruct use,intrinsic :: iso_c_binding use sidl_double_array type,bind(c) :: addRand_fStruct_t real(c_double) :: bX integer(c_int32_t) :: iY type(c_ptr) :: structRAW real(c_double)::fixBound(10) end type addRand_fStruct_t end module addRand_fStruct Dynamic R-Array

10 real(c_double),dimension(:),pointer :: structTest_structRAW_fptr call C_F_POINTER(CPTR=structTest%structRAW, & FPTR=structTest_structRAW_fptr, & SHAPE=(/DIM/)) do i=1,structTest%iY structTest_structRAW_fptr(i)=structTest_structRAW_fptr(i)+5.0 enddo call procedureDoSomething(structTest_structRAW_fptr) ! NOT call procedureDoSomething(structTest) What is the best way to pass the converted F pointer to deeply nested procedure calls?

11 struct Flags { … double glfCbetae; /*FD set cbetae=1 for fully electromagnetic */ double glfCnu; /*FD factor for the collisionality */ rarray glfIflagin(5); /*FD Transport flags internal to the GLF module */ rarray glfXparam(30); /*FD Normalizers and calibration coefficients */ /* internal to the module */ int mmmNroot; /*FD number of moments */ int mmmNpoints; /*FD should be always 1 */ … }; REAL(kind=r8) :: glfCbetae !*FD set cbetae=1 for fully electromagnetic REAL(kind=r8) :: glfCnu !*FD factor for the collisionality INTEGER, DIMENSION(5) :: glfIflagin !*FD Transport flags internal to the GLF module REAL(kind=r8), DIMENSION(30) :: glfXparam !*FD Normalizers and calibration c !* coefficients internal to the module INTEGER :: mmmNroot !*FD number of moments INTEGER :: mmmNpoints !*FD should be always 1 How do we convert the transport module Flags type to SIDL?

12 How do we provide the transport modules interface using Babel? fmcfmWrap::fmcfm FM = fmcfmWrap::fmcfm::_create(); retVal=t_start("TmInitFlags"); FM.siInitFlags(flags,funit_input); retVal=t_stop("TmInitFlags"); recursive subroutine fmcfmWrap_fmcfm_siInitFlags_mi(self, mflags, funit, & exception) … call sidlInitFlags(mflags,funit) … 19 SUBROUTINE sidlInitFlags(mFlags,funit) 20 USE input_namelist_mod 21 IMPLICIT NONE 22 23 TYPE(fmcfmWrap_Flags_t),INTENT(OUT) :: mflags 24 INTEGER, INTENT(IN) :: funit 25 26 IF(funit > 0) THEN 27 REWIND(funit) 28 READ(funit,GLF_FLAGS) 29 REWIND(funit) 30 READ(funit,MMM_FLAGS) 31 ENDIF 32 33 CALL setFlags(mFlags) 34 35 END SUBROUTINE sidlInitFlags

13 Questions/Comments

Download ppt "Babel F2003 Struct Support Update and FACETS integration Funded by DOE (TASCS) Grant No DE-FC02-07ER25805, DOE Grant No DE-FG02-04ER84099 and Tech-X Stefan."

Similar presentations

Everyone loves Fortran. 1. Deprecate mpif.h Fortran refresher Two Fortran interfaces for each MPI function Available in three different bindings Integer.

Everyone loves Fortran. 1. Deprecate mpif.h Fortran refresher Two Fortran interfaces for each MPI function Available in three different bindings Integer.
Semantic Analysis Chapter 6. Two Flavors  Static (done during compile time) –C –Ada  Dynamic (done during run time) –LISP –Smalltalk  Optimization.

Semantic Analysis Chapter 6. Two Flavors  Static (done during compile time) –C –Ada  Dynamic (done during run time) –LISP –Smalltalk  Optimization.
Chapter 7 Introduction to Procedures. So far, all programs written in such way that all subtasks are integrated in one single large program. There is.

Chapter 7 Introduction to Procedures. So far, all programs written in such way that all subtasks are integrated in one single large program. There is.
Chapter 5: Elementary Data Types Properties of types and objects –Data objects, variables and constants –Data types –Declarations –Type checking –Assignment.

Chapter 5: Elementary Data Types Properties of types and objects –Data objects, variables and constants –Data types –Declarations –Type checking –Assignment.
Tammy Dahlgren, Tom Epperly, Scott Kohn, and Gary Kumfert Center for Applied Scientific Computing Common Component Architecture Working Group October 3,

Tammy Dahlgren, Tom Epperly, Scott Kohn, and Gary Kumfert Center for Applied Scientific Computing Common Component Architecture Working Group October 3,
Chapter 9 Subprogram Control Consider program as a tree- –Each parent calls (transfers control to) child –Parent resumes when child completes –Copy rule.

Chapter 9 Subprogram Control Consider program as a tree- –Each parent calls (transfers control to) child –Parent resumes when child completes –Copy rule.
Creating and Linking Components in ESMF and CCA Eric Hutton Cyberinformatics and numerics working group February 2008.

Creating and Linking Components in ESMF and CCA Eric Hutton Cyberinformatics and numerics working group February 2008.
ISBN 0- 321-49362-1 Chapter 11 Abstract Data Types and Encapsulation Concepts.

ISBN Chapter 11 Abstract Data Types and Encapsulation Concepts.
Programming Languages: Design, Specification, and Implementation G22.2210-001 Rob Strom September 14, 2006.

Programming Languages: Design, Specification, and Implementation G Rob Strom September 14, 2006.
ISBN 0-321-33025-0 Chapter 9 Subprograms. Copyright © 2006 Addison-Wesley. All rights reserved.1-2 Introduction Two fundamental abstraction facilities.

ISBN Chapter 9 Subprograms. Copyright © 2006 Addison-Wesley. All rights reserved.1-2 Introduction Two fundamental abstraction facilities.
The environment of the computation Declarations introduce names that denote entities. At execution-time, entities are bound to values or to locations:

The environment of the computation Declarations introduce names that denote entities. At execution-time, entities are bound to values or to locations:
Peter Juszczyk CS 492/493 - ISGS. // Is this C# or Java? class TestApp { static void Main() { int counter = 0; counter++; } } The answer is C# - In C#

Peter Juszczyk CS 492/493 - ISGS. // Is this C# or Java? class TestApp { static void Main() { int counter = 0; counter++; } } The answer is C# - In C#
Functions. Program complexity the more complicated our programs get, the more difficult they are to develop and debug. It is easier to write short algorithms.

Functions. Program complexity the more complicated our programs get, the more difficult they are to develop and debug. It is easier to write short algorithms.
Chapter 8 :: Subroutines and Control Abstraction

Chapter 8 :: Subroutines and Control Abstraction
1 CISC181 Introduction to Computer Science Dr. McCoy Lecture 19 Clicker Questions November 3, 2009.

1 CISC181 Introduction to Computer Science Dr. McCoy Lecture 19 Clicker Questions November 3, 2009.
Inheritance in C++ CS-1030 Dr. Mark L. Hornick.

Inheritance in C++ CS-1030 Dr. Mark L. Hornick.
Learners Support Publications www.lsp4you.com Pointers, Virtual Functions and Polymorphism.

Learners Support Publications Pointers, Virtual Functions and Polymorphism.
Babel F2003 Wrap-up Stefan Muszala*, Tom Epperly(LLNL), Nanbor Wang* Funded by DOE (TASCS) Grant No DE-FC02-07ER25805, DOE Grant No DE-FG02-04ER84099 and.

Babel F2003 Wrap-up Stefan Muszala*, Tom Epperly(LLNL), Nanbor Wang* Funded by DOE (TASCS) Grant No DE-FC02-07ER25805, DOE Grant No DE-FG02-04ER84099 and.
Types for Programs and Proofs Lecture 1. What are types? int, float, char, …, arrays types of procedures, functions, references, records, objects,...

Types for Programs and Proofs Lecture 1. What are types? int, float, char, …, arrays types of procedures, functions, references, records, objects,...
CcaEcloud Phase I Wrap-up Phase I Doe SBIR Stefan Muszala, PI DOE Grant No DE-FG02-08ER85152 Tech-X Corporation Boulder, CO Updates: onRamp, FACETS+Babel,

CcaEcloud Phase I Wrap-up Phase I Doe SBIR Stefan Muszala, PI DOE Grant No DE-FG02-08ER85152 Tech-X Corporation Boulder, CO Updates: onRamp, FACETS+Babel,

Similar presentations

Ads by Google