![]() ![]() 황순욱박사 Activities Geant4 Workshop and Tutorials Needs by community => Tutorials & Papers Stage2: 2012~ Present: HEP Group Challenge Program (2012) => Collaboration Computational Science (2013~) => R&Dĥ Stage1: 2009~2011 Ref. EM Physics)Ĥ History Stage1: 2009~2011: IT Group Stage2: 2012~ Present: HEP Group SimpliCarlo) Fermilab (Parallel) W/ Soon 2-1. Quality and Assurance Group (Group: Soon Jun) => Part II Profiling for Medical Physics (cf. KISTI Tachyon2 (CPU: 200,000 CPU*h) – Andrea Physics List using Beam – Chanyoung Lee 1-2. Physics List and Validation Tool Kit Group (Chair: Gunter) => 0.1 FTE & Test => Part I. Unless required, you should not set these environment variables, because that may interfere with the configure script.Presentation on theme: "Geant4 profiling for medical physics"- Presentation transcript:Ħth International Geant4 Tutorial in Korea KIRAMS, Seoul, Korea July 24~28, 2017 Geant4 profiling for medical physics Kihyeon Cho and Insung Yeo (KISTI) One or more of these may be needed for some platforms. ![]() If you need to pass the same arguments to the FORTRAN 90 build, also set FCFLAGS.ĪRFLAGS, NMFLAGS, FPP, M4FLAGS, LIBS, FLIBS, FLDFLAGS If setting these you may also need to set FFLAGS for the FORTRAN 77 test programs. "-DNDEBUG" to omit assertion checks, for example. Using Fortran compilers from different vendors is not supported and may not work. For vendor compilers, make sure you're using the same vendor's Fortran 90 compiler. If you don't specify this, the configure script will try to find a suitable Fortran compiler. Otherwise use FC to specify the Fortran compiler. Only specify this if your platform explicitly needs a different Fortran 77 compiler. Use –disable-f90 to disable the netCDF Fortran 90 API, but build the netCDF Fortran 77 API. If you don't specify this, the configure script will try to find a suitable Fortran and Fortran 77 compiler. If you wish to use a vendor compiler you must set CC to that compiler, and set other environment variables (as described below) to appropriate settings. If you don't specify this, the configure script will try to find a suitable C compiler. In this case you will need to run configure with –disable-fortran-compiler-check and –disable-fortran-type-check.Įnvironment Variable Description Notes Variable Or the more general "pkg-config" utility, if you have it: fortran my_prog.f -o my_prog `pkg-config -cflags -libs netcdf-fortran`įor cross-compiles, the following environment variables can be used to override the default fortran/C type settings like this (in sh): export NCBYTE_T="integer(selected_int_kind(2))"Įxport NF_INT1_T="integer(selected_int_kind(2))" In either case, $/bin: fortran my_prog.f -o my_prog `nf-config -fflags -flibs` Syntax to set environment variables instead of the ENV_VARIABLE=value If you are using csh instead, you will have to use the setenv ENV_VARIABLE value In the example commands below, we assume use of a POSIX-standard shell, such as sh, bash, ksh, or zsh. More recently, building netcdf-fortran as an automated step in the netcdf-c build is now possible (for non-MSVC builds) by using new options at configure time, so if you haven't built and installed the netCDF-C library yet, you may want to try the new netCDF-C Fortran-bootstrap procedure. This separation simplifies the building and use of the C and Fortran netCDF libraries and allows them to evolve independently. With more recent versions, the Fortran netCDF library has been split off into an independent source distribution, intended to be built as a separate library, after the C library is built and installed. In versions before 4.2, the Fortran netCDF library source was bundled with the C library source in one distribution. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |