Programming/Fortran - Revision history

Pysdlb: /* Navigation */

2022-11-16T11:28:12Z

‎Navigation

Pysdlb at 16:05, 8 November 2022

2022-11-08T16:05:00Z

Pysdlb at 16:01, 8 November 2022

2022-11-08T16:01:43Z

Pysdlb at 12:26, 2 November 2022

2022-11-02T12:26:15Z

Pysdlb at 09:11, 24 May 2021

2021-05-24T09:11:58Z

Pysdlb at 10:56, 10 June 2019

2019-06-10T10:56:52Z

Pysdlb at 10:27, 10 June 2019

2019-06-10T10:27:22Z

Pysdlb at 08:04, 20 April 2018

2018-04-20T08:04:54Z

Pysdlb at 15:25, 18 April 2018

2018-04-18T15:25:08Z

Pysdlb at 15:22, 18 April 2018

2018-04-18T15:22:19Z

← Older revision		Revision as of 11:28, 16 November 2022
Line 313:		Line 313:
	* [[programming/Python\|Python Programming]]		* [[programming/Python\|Python Programming]]

−	~~==Navigation==~~	+	{{Languagespagenav}}
−
−	* [[Main_Page\|Home]]
−	* [[Applications\|Application support]]
−	* [[General\|General]]
−	~~* [[Programming\|Programming support]] *~~

← Older revision		Revision as of 16:05, 8 November 2022
Line 155:		Line 155:
	There does exist a number of FORTRAN code analysis tools (static and dynamic checking), a particularly useful one is FORCHECK.		There does exist a number of FORTRAN code analysis tools (static and dynamic checking), a particularly useful one is FORCHECK.

−	Also is ~~camFORT~~ a tool for cross-checking variables and their computation elements within a program, this is particularly useful for high mathematical/ scientific codes.	+	Also, camFORT is a tool for cross-checking variables and their computation elements within a program, this is particularly useful for high mathematical/ scientific codes.

@@ Line 69: / Line 69: @@
 * module add intel/2018 (Intel compiler)
-'''Note''': It is generally accepted that the intel compiler generates faster code on Intel hardware than gcc, although gcc is generally more compatible with a wide range of hardware.
+'''Note''': It is generally accepted that the intel compiler generates faster code on Intel hardware than GCC, although GCC is generally more compatible with a wide range of hardware.
 ====Design considerations====
@@ Line 185: / Line 185: @@
 </pre>
-* '''Good practice''' when compiling is to only use compiler optimization flags at the final stages towards production release, Intel's fortran compiler usually has -O2 set by default, so placing compiler flag -O0 would be necessary to turn this off.
+* '''Good practice''' when compiling is to only use compiler optimization flags at the final stages towards production release, Intel's Fortran compiler usually has -O2 set by default, so placing compiler flag -O0 would be necessary to turn this off.
-* '''Note''' : mpifort would be used as the compiler wrapper if the above example used [[Applications/OpenMPI|openMPI]].
+* '''Note''' : mpifort would be used as the compiler wrapper if the above example is used [[Applications/OpenMPI|openMPI]].
 ====Documentation generators====

@@ Line 147: / Line 147: @@
 </pre>
-* Go to statements are sometimes useful but they are discouraged because they are generally difficult to manage;
+* Go-to statements are sometimes useful but they are discouraged because they are generally difficult to manage;
@@ Line 160: / Line 160: @@
 ====Fortran pre-processing====
-The pre-processor is a text processing tool that is usually integrated into the compiler;
+The pre-processor is a text-processing tool that is usually integrated into the compiler;
 It is a separate stage and occurs prior to compilation;
@@ Line 237: / Line 237: @@
 PROGRAM H5_CRTDAT
-   USE HDF5 ! This module contains all necessary modules
+   USE HDF5 ! This module contains all the necessary modules
    IMPLICIT NONE
@@ Line 299: / Line 299: @@
 </pre>
-==Further Information==
+==Next Steps==
 * [http://www.tutorialspoint.com/fortran/ http://www.tutorialspoint.com/fortran/]

@@ Line 69: / Line 69: @@
 * module add intel/2018 (Intel compiler)
-'''Note''' : It is generally accepted that the intel compiler generates faster code on Intel hardware than gcc, although gcc is generally more compatible with a wide range of  hardware.
+'''Note''': It is generally accepted that the intel compiler generates faster code on Intel hardware than gcc, although gcc is generally more compatible with a wide range of hardware.
 ====Design considerations====
-* Array storage in Fortran is column-major. That is to say, when stored in memory as a linear array, the matrix will be arranged as . Thus, accessing the elements of column-wise is most efficient. A useful way to remember this is that in Fortran, the first index varies fastest.
+* Array storage in Fortran is column-major. That is to say, when stored in memory as a linear array, the matrix will be arranged as. Thus, accessing the elements of column-wise is most efficient. A useful way to remember this is that in Fortran, the first index varies fastest.
-Accessing the memory in the order in which it is stored will be faster, and also means any vectorisation optomisations can be easily performed by the compiler.
+Accessing the memory in the order in which it is stored will be faster, and also means any vectorization optimizations can be easily performed by the compiler.
 In Fortran, this means writing loops like:
@@ Line 87: / Line 87: @@
 </pre>
-This is the opposite way around to languages like C, which is row major.
+This is the opposite way around to languages like C, which is row-major.
 * When reading or writing an array, use the array name and not a DO loop or an implied DO-loop that specifies each element number. Fortran 95/90 array syntax allows you to reference a whole array by using its name in an expression.
@@ Line 153: / Line 153: @@
 ====Debugging code====
-There does exist a number of FORTRAN code analysis tools (static and dynamic checking), a particular useful one is FORCHECK.
+There does exist a number of FORTRAN code analysis tools (static and dynamic checking), a particularly useful one is FORCHECK.
-Also is camFORT a tool for cross checking variables and they computation elements within a program, this is particularly useful for high mathematical/ scientific codes.
+Also is camFORT a tool for cross-checking variables and their computation elements within a program, this is particularly useful for high mathematical/ scientific codes.
 ====Fortran pre-processing====
-The pre-processor is a text processing tool which is usually integrated into the compiler;
+The pre-processor is a text processing tool that is usually integrated into the compiler;
 It is a separate stage and occurs prior to compilation;
@@ Line 190: / Line 190: @@
 ====Documentation generators====
-Suitable automatic source code generators for fortran are [http://fortranwiki.org/fortran/show/FORD FORD] and [http://fortranwiki.org/fortran/show/Doxygen doxygen]
+Suitable automatic source code generators for FORTRAN are [http://fortranwiki.org/fortran/show/FORD FORD] and [http://fortranwiki.org/fortran/show/Doxygen doxygen]
 == Usage Examples ==
@@ Line 208: / Line 208: @@
 #SBATCH -p compute
 #SBATCH --exclusive
 echo $SLURM_JOB_NODELIST
@@ Line 228: / Line 229: @@
 ==HDF5 library==
-HDF5 is a versatile data model that can represent very complex data objects and a wide variety of metadata, which is ideal for data which has a large disparity to be stored in a standard format description. [https://en.wikipedia.org/wiki/NetCDF NetCDF] is a similar system as well.
+HDF5 is a versatile data model that can represent very complex data objects and a wide variety of metadata, which is ideal for data that has a large disparity to be stored in a standard format description. [https://en.wikipedia.org/wiki/NetCDF NetCDF] is a similar system as well.
 (''Example from the HDF group'')

@@ Line 66: / Line 66: @@
 The following modules are available:
-* module add gcc/4.9.3 (GNU compiler)
+* module add gcc/8.2.0 (GNU compiler)
-* module add intel/compiler/64/2016.2.181 (Intel compiler)
+* module add intel/2018 (Intel compiler)
 '''Note''' : It is generally accepted that the intel compiler generates faster code on Intel hardware than gcc, although gcc is generally more compatible with a wide range of  hardware.

@@ Line 181: / Line 181: @@
 <pre style="background-color: black; color: white; border: 2px solid black; font-family: monospace, sans-serif;">
-[username@login01 ~]$  module add gcc/4.9.3
+[username@login01 ~]$  module add gcc/8.2.0
 [username@login01 ~]$  gfortran -o testFortran  testFortran.f03
 </pre>
@@ Line 212: / Line 212: @@
 module purge
-module add gcc/4.9.3
+module add gcc/8.2.0
 export I_MPI_DEBUG=5
@@ Line 311: / Line 311: @@
 * [[programming/C-Plusplus|C++ Programming]]
 * [[programming/Python|Python Programming]]
-{|
-|style="width:5%; border-width: 0" | [[File:icon_home.png]]
+==Navigation==
-|style="width:95%; border-width: 0" |
 * [[Main_Page|Home]]
 * [[Applications|Application support]]
 * [[General|General]]
-* [[Training|Training]]
+* [[Programming|Programming support]] *

@@ Line 173: / Line 173: @@
 <pre style="background-color: black; color: white; border: 2px solid black; font-family: monospace, sans-serif;">
-[username@login01 ~]$  gfortran -c -  DDEBUG code.F
+[username@login01 ~]$  gfortran -c -DDEBUG code.F
 </pre>

← Older revision		Revision as of 15:25, 18 April 2018
Line 158:		Line 158:


−	====Fortran ~~Pre~~-~~Processing~~====	+	====Fortran pre-processing====

	The pre-processor is a text processing tool which is usually integrated into the compiler;		The pre-processor is a text processing tool which is usually integrated into the compiler;