Versions Compared

Old Version 5

changes.mady.by.user Daniel Figat

Saved on

compared with

New Version 6

changes.mady.by.user Daniel Figat

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

 

Warning

A name of user subroutine must be exactly the same as it was defined in user code

 

4.1.4 Environment

 

Fig. 3. FC2K environment tab

...

4.1.7 "Source" tab explained

Image RemovedImage Added

Fig. 7. "Source" tab

...

  • a programming language
  • utilized compiler,
  • type of code execution (sequential of parallel)
  • libraries being used

4.1.7

...

A user, using this tab, selects programming language of codes provided, compiler used to built library and type of code execution (sequential or parallel)

Image Removed

Fig. 8. "Source" tab - code description
  • Type - Defines programming language of user codes. It could be set to:
    • Fortran
    • _C/C++
  • Compiler - Defines compiler being used. Possible values:
    • ifort, g95, gfortran
    • gcc, g++
  • Parallel MPI - If turned ON uses MPI compilers (mpiifort for ifort, mpif90 for gfortran, mpigxx for C)
  • OPENMP - Defined if usage of OpenMP directives is turned ON/OFF
  • Batch - If turned ON, submits a user code to jobs queue (combined with Parallel MPI or OPENMP switch runs user code as parallel job)

...

.1

...

Libraries

"Main library"

A "Main library" field allows to define a path to library containing user subroutine/function.

Image RemovedImage Added

Fig. 98. "Source" tab - A path to "main"and "optional" library
"Optional library"

A "Optional library" field allows to define a path to optional library containing user subroutine/function.

 

"Custom libraries"

"Custom libraries" are non-standard static libraries required for building the user code.

Fig. 109. "Source" tab - A list of "custom" libraries

...

"System libraries" are system libraries handled by pkg-config mechanism and required for building the user code.

Fig. 1110. "Source" tab - A list of "system" libraries

...

  • add library from the list,
  • remove library
  • display detailed info (library definition returned by pkg-config mechanism)

Fig. 1211. Adding "system" libraries
Tip
  • Tooltips show a detailed info about parameters that would be added to Makefile for selected library
  • "Search" field allows for easy filtering the list of libraries
  • Only ITM libraries (80+) are shown by default. To see a list of all libraries (250+) defined by pkg-config mechanism "List all system libraries" checkbox should be selected.
  • The libraries marked as built for compiler other than currently selected one are filtered out of the list. To turn off this filter unselect appropriate checkbox

 

4.1.8 "Settings" tab explained

A user, using this tab, selects programming language of codes provided, compiler used to built library and type of code execution (sequential or parallel)

Image Added

Fig. 12. "Settings" tab - code description
  • Programming languange:
    • Type - Defines programming language of user codes. It could be set to:
      • Fortran
      • _C/C++
    • Compiler - Defines compiler being used. Possible values:
      • ifort, gfortran
      • gcc, g++
  • Computation:
    • Parallel MPI - If turned ON uses MPI compilers (mpiifort for ifort, mpif90 for gfortran, mpigxx for C)
    • OPENMP - Defined if usage of OpenMP directives is turned ON/OFF
    • Batch - If turned ON, submits a user code to jobs queue (combined with Parallel MPI or OPENMP switch runs user code as parallel job)
  • Additional features:
    • Calls init method - 
    • Returns diagnostic info - 

4.1.9 "Documentation" tab explained

The "Documentation" tab specifies an user-defined Kepler actor description. It could be displayed from actor pop-up menu.

Fig. 13. "Documentation" tab

4.1.10 "Interface" tab explained

The "Interface" tab specifies interface for Kepler actor.

Image Added

Fig. 14. "Interface" tab

4. Incorporating user codes into Kepler using FC2K - exercises

...