Reference: 1208262126

An experienced Mathematical Modelling Consultant is required for an ERS Client's Dorset site. The successful applicant will provide scientific and technical consultancy to UK and overseas clients in the nuclear (and non-nuclear) sectors.

Location

Dorset

Client Information

Our Client's Nuclear Services (NSER) business provides consultancy advice to a variety of high technology users from within the nuclear and non-nuclear industries.

They provide scientific consultancy and software to many of the major players in the civil nuclear power industry, in the UK and overseas, and also support a number of large research programmes for the Ministry of Defence.

These posts represent an excellent opportunity for mathematicians, physicists, or engineers who wish to develop expertise in mathematical modelling in a diverse range of disciplines. These could include one or a combination of reactor physics, fluids and thermal modelling, radiation transport, aerosol transport, modelling chemical reactions and many others. Methods developments support safety and performance of power reactors, various nuclear facilities and other industrial plant operations.

NSER is a large department of experienced scientists and engineers, based at Winfrith and Harwell, working on a diverse range of projects for a broad portfolio of clients.

Working on these projects requires interaction with colleagues across the Groups, as well as supporting colleagues across the company. Many of their more experienced staff provide the technical lead on such projects, and this post offers the opportunity to develop into such a role.

Our client is committed to the training and continuing professional development of its staff; seeking to keep their skills up to date by appropriate training, attendance at conferences and liaison with universities. NSER has strong links with many science and engineering departments of a number of leading universities and retains access to state-of-the art research in these institutions.

Requirements & Responsibilities

The provision of scientific and technical consultancy to UK and overseas clients in the nuclear (and non-nuclear) sectors, including analysing problems and developing solutions.

Developing, maintaining and validating the computer codes in their code products range.

Involvement in research tasks in the civil or defence nuclear sectors.

The production and presentation of technical reports to clients; Task management, including delivery of work to agreed timescales and budget; Leading/assisting with the production of contract proposals and bids, and identifying new technical business development opportunities

Requirements: Education and Experience

Educated to honours degree level (1 or 2:1) in mathematics, physics or engineering, coupled ideally with a relevant post graduate qualification. They are seeking high calibre candidates, who are flexible and keen to develop their skills in the above disciplines.

Some experience of FORTRAN and other high level programming languages, and also with modelling packages such as MATHMATICA or MATHCAD would be an advantage, as would previous experience within the civil nuclear industry or the defence nuclear sector.

Applications from any well qualified candidates in related scientific disciplines are welcome; such candidates will be considered if they can demonstrate a high level of commitment to learn new skills.

Security clearance to work on defence related projects would be desirable.

Core Competences

A strong mathematics, physics or engineering background; An aptitude for mathematical modelling including the ability to break down complex situations into tractable problems; An aptitude for computer code development and application; Good analytical skills and the ability to interpret a variety of technical information, distilling and conveying key information; Task management to deliver to time, budget and quality; The ability to work well in multi-disciplinary teams; Flexibility and adaptability, to be able to work on a variety of projects and good interpersonal and communication skills.

Contact ERS on 01454 203 460, or submit a CV to cv@energyrs.co.uk, to register your interest or apply, details at www.ERSJobs.co.uk

Esta es una Guia rapida y practica de como Diferenciar.

TAREA: DISPARARTE EN EL PIE

C
Te disparas en el pie, pero lugo te das cuenta que el arma es demasiado poderosa para tus simples necesidades de dispararte en el pie.

C++
Accidentalmente creas una docena de clones tuyos y les disparas a todos en el pie. Proveer asistencia médica es imposible porque no puedes distinguir entre las copias reales y las que señalan a otros diciendo “¡Ese soy yo, ahí estoy!”

Java
Después de importar java.awt.pie.derecho.* y java.awt.pistola.mano.derecha.* y después de escribir las clases y los métodos que necesitas, ya se te olvidó lo que estabas haciendo.

Ruby
Tu pie está listo para que le dispares en unos cinco minutos, pero no puedes encontrar ningún lugar para dispararle.

C#
Cópiale el método a Java y trata de convecer a todos que tú lo haces mejor.

PHP
Te disparas en el pie con un arma hecha con 300 piezas de otras armas.

ASP.NET
Encuentras una pistola, se desbarata. La vuelves a armar, se vuelve a desbaratar. Tratas de usar el .GUN Framework… se desbarata. Terminas mejor apuñalándote el pie.

SQL
SELECT @munición:=bala FROM pistola WHERE gatillo = ‘JALAR’;
INSERT INTO pierna (pie) VALUES (@ammo);

Perl
Te disparas en el pie, pero nadie entiende cómo lo hiciste. Seis meses después tú tampoco lo entiendes.

JavaScript
Has perfeccionado una rica y robusta experiencia de usuario para dispararte en el pie. Después te das cuenta de que las balas estan desabilitadas en tu pistola.

CSS
Te disparas en el pie derecho con una mano, luego cambias de mano para dispararte en el otro pie, pero entonces te das cuenta que tu arma se ha convertido en una banana.

Fortran
Te disparas en cada dedo del pie, iterativamente hasta que se te acaban los dedos de los pies, después lees tu otro pie y repites. Si se te acaban las balas continuas de todas formas porque no hay capacidad de manejo de excepciones.

Modula2
Después de darte cuenta que no puedes hacer nada en este lenguaje, te das un tiro en la cabeza.

Cobol
Usando una PISTOLA COLT 45, APUNTAR arma a PIE.IZQUIERDO, ENTONCES colocar BRAZO.MANO.DEDO en PISTOLA.GATILLO y APRIETA. ENTONCES regresa PISTOLA a FUNDA. VERIFICAR si las agujetas se tienen que volver a amarrar.

Lisp
Te disparas en la extremidad la cual sostiene el arma con la cual
te disparas en la extremidad la cual sostiene el arma con la cual
Te disparas en la extremidad la cual sostiene el arma con la cual
Te disparas en la extremidad la cual sostiene el arma con la cual
Te disparas en la extremidad la cual…

Scheme
(define (disparo arma pie)
(if (null? pie) ()
(disparo arma (car (cdr( pie)))))

Basic
Te disparas en el pie con una pistola de agua. En sistemas grandes, continúas hasta que toda la parte baja del cuerpo esté inundada.

Visual Basic

Tratas de dispararte pero cuando tratas de meter la bala en el arma no podes porque pesa 153Kg.

Pascal
El compilador no te deja dispararte en el pie.

Snobol
Si tienes éxito, te disparas en el pie izquierdo.
Si no lo tienes, te disparas en el pie derecho.

Euclídeo concurrente
Te disparas a ti mismo en el pie de otra persona.

HyperTalk
Colocas la primera bala del arma dentro del pie de tu pierna izquierda.
Solucionas el resultado.

Motif
Te la pasas los días escribiendo una descripción UIL de tu pie, la trayectoria, la bala, y hasta las partíclas de humo. Cuando finalmente vas a jalar el gatillo, está atascado.

Unix
% ls
pie.c pie.h pie.o dedo.c dedo.o
% rm *.o
rm: .o: No such file or directory
% ls
%

Paradox
No sólo tú puedes dispararle a tu pie, tus usuarios también pueden.

Prolog
Le dices a tu programa que quieres que te disparen en el pie. El programa calcula cómo hacerlo, pero la sintaxis no le permite explicarte.

Ada
Después de empaquetar correctamente tu pie, intentas cargar el arma concurrentemente, jalar el gatillo, gritar y dispararte en el pie. Pero cuando lo pruebas, te das cuenta que tu pie está en la tipografía incorrecta.

Ensamblador
Tratas de dispararte en el pie sólo para descubrir que primero tienes que reinventar el arma, la bala y tu pie. Después de que lo haces, jalas el gatillo, el arma hace bip varias veces, y se descompone.

Python
Tratas de dispararte en el pie pero sólo le atinas al espacio entre los dedos.

Smalltalk
Uno-mismo pie disparar

370 JCL

Mandas tu pie al MIS con una documentacion de 4000 paginas explicando como queres que sea disparado. Tres Años despues, tu pie vuelve frito.

Articulo Original

module mod_angle ! fichero: mod_angle.f95
implicit none ! las variables se declaran explictamente
type Angle ! la estructura Angle es public pero sus miembros
private ! privados
real :: rad

LEER EL RESTO DE LA ENTRADA


Is it really the case that there's no way (in (portable) Fortran) to format a floating point number so that it has as many leading zeros as are necessary to fill the field?

Imagine I wanted to output something like ISO 6709 and have the location of Sheffield displayed as:

+53.40-001.50

In Python (using C's syntax) this is just '%+06.2f%+07.2f' % (lat,lon).

Can I really not do this in Fortran? Surely I have just missed something.

      WRITE(*,'(SP,F6.2,F7.2)')LAT,LON

gives me:

+53.40 -1.50

which is not what I wanted at all. I (half humourously) tried F06.2,F07.2 but that doesn't work.

If true, it's absolutely unforgivable.

This image was scanned from a 1954 issue of Popular Mechanics, the magazine. The text says,

Scientists at the RAND Corporation have created this model to illustrate how a "home computer" could look like in the year 2004. However the needed technology will not be economically feasible for the averate home. Also the scientists readily admit that the computer will require not yet invented technology to actually work, but 50 years from now scientific progress is expected to solve these problems. With teletype interface and the Fortran language, the computer will be easy to use.

Gotta love those early computer scientists!

As the creator of C++, Bjarne Stroustrup, said, “C++ is a better C” and surely it was. Classes and objects made it much easier to develop large programs, compared to C. Inheritance and polymorphism were useful, but the benefits of using classes and objects far surpassed those of inheritance and polymorphism. But many people, including me, found that it was difficult to ensure that all objects were properly destroyed, especially in large programs. This meant that large programs had memory leaks that needed to be debugged and removed and this required a lot of effort. Moreover, memory leaks meant that organizations could not rely on developing large programs with confidence.

Object destruction and memory leaks were addressed with the introduction of grabade collection Java™ and C#.  With garbage collection, the programmer needed no longer worry much about destroying unused objects. As soon as the objects went out of scope, they were made available for garbage collection. Programmers the world over soon found the advantages of using Java and C# too large to ignore and moved to en masses from C++ to these new languages.

Garbage collection involves some overhead because the garbage collector needs to go through all unused objects, clean them up and make the resulting memory available to the global pool. Although Java and C# are great for most software programs, there are still some types of software out there that could benefit from the more efficient nature of C++. Programmers can still churn out good programs that are relatively free of memory leaks using C++. So, when required, organizations should still consider using C++ for their software needs in special situations. For most general programming, Java and C# will do fine and will likely save the organization the headache of dealing with pesky memory leaks.

© Suresh Peram, 2008. All rights reserved.

Notes:

1. Java is a trademark of Sun Microsystems Inc.

I often get personally asked, and see the question come up online a lot, what courses a person should take in college if they want to become a professional programmer. I took a fairly broad range of classes in college (Caltech), and have been programming for 30 years now, so I have some perspective on what has worked for me and what hasn't. I've ordered them from most important to least.

Calculus - No, you won't use calculus in programming. But it turns out that the training of your mind that happens when learning calculus is very beneficial to programming. This training seems to happen in math courses and doesn't happen in programming courses. If you find yourself selecting college courses based on which ones don't require calculus, you should seriously consider changing professions, because you won't make it as a programmer. Take at least 3 years of calculus.

Physics - For unknown reasons, the best programmers tend to be physicists by training. The way physics is taught seems to teach the brain how to go about solving problems in an organized way. Besides, understanding newtonian and quantum mechanics is just freaking cool. You'll be able to proudly wear your Maxwell's Equations t-shirt. Fair warning: once you understand physics, Star Trek, Star Wars, and other hollywood sci-fi craptastic films won't seem so cool anymore.

Compiler Construction - You'll be using a compiler probably more than any other tool, and understanding them will help a lot in getting the most out of them and bending them to your will. Furthermore, the skills learned in writing a compiler pretty much cover the gamut of computer science concepts.

Assembler Programming - You'll never learn how a computer really works by learning high level languages. I know too many programmers who have a fear of assembler. They will go to great lengths to avoid even glancing at the assembler output of their compiler, as if it would strike them blind. But they'll never be in the top tier of programmers. You can learn an awful lot about the compiler you're using, and how to get the most out of it by looking at the asm output. You'll also find that sometimes that's the only way to figure out what is going wrong.

Business Accounting - Eventually in your career, you'll want to move into management or spin off and start your own company. At that point, knowing the fundamentals and language of business accounting is indispensible.
I know it's dull, dull, dull, and lion taming is so much more fun and you've even got a hat for it, but without knowledge of accounting you'll be crippled talking to investors, your bank, or the tax man.

Digital Electronics - Understanding how the hardware actually functions will help you approach a computer as a machine that can be mastered rather than a magic black box. You're going to be working with it a lot, might as well understand it.

Jet Engine Analysis - I'm fascinated by engines of all types. Jet engines are especially cool. I'll never forget going to the test bunker while the engineers lit off an F-100 engine. If I could figure out what this has to do with programming, I'd tell you. So sue me.

FORTRAN - It was a waste of time, because FORTRAN shortly thereafter went out of fashion. Generally, any programming course that focusses on learning a particular language is a waste of time. Instead, courses that teach a thought process that is applicable in general to programming is far more valuable. Learning particular languages is just a detail you can do later.

Chemistry - I never properly understood chemistry. This deficit doesn't seem to have mattered in my career. Chemistry seemed to be more oriented towards memorization, and trial and error. I don't think that applies much to programming.

Economics - Ok, this has nothing to do with programming. But economics is one of those dismal fields where everyone thinks they are an expert, from 16 years old on. Few would dream of pontificating about physics or calculus without learning something about it first, but nobody seems to have any qualms about doing it for economics. I see this all the time on reddit, digg, etc. So please, please, take a course in economics and at least understand the basic concepts!

Foreign Language - I'm going to get flamed for this, but I see little point to it for a programming career. I took German, and aside from the personal pleasure in learning it, it's been professionally useless to me. It's a global economy, but knowing German won't help you in dealing with the Chinese or the French, and vice versa. English is the global language of business, and if you know that, you'll be fine.

Interestingly, there's not a lot of actual programming courses in this list. If you're training to be a programmer, shouldn't programming courses be the bulk of them? Not necessarily. College should not be viewed as learning particular knowledge, but as learning how to think. Math will teach you how to think abstractly and logically, and physics will teach you how to approach solving problems. Once that is working in your head, you'll find you can pick up programming rather easily, and those thought processes will serve you well for anything you want to tackle, for the rest of your life.

2. INTEGER, INTENT(IN) :: a -> this is from the input, and it will not be changed.
INTEGER, INTENT(OUT) :: a -> the return value.. as far as i know, you cant passed a value in the call method for it.. kasi output sya..
INTEGER, INTENT(INOUT) :: a -> galing sa input.. then can change the value and return it.

3. DYNAMIC SIZE of the ARRAY
DOUBLE PRECISION, DIMENSION(:,:), ALLOCATABLE :: A !allocate 2D array
ALLOCATE(A(1:n, 1:n)) !size nya
DEALLOCATE(A) !need to free

4. END OF FILE. USE IOSTAT
READ(fUnit,*, IOSTAT = endOfFile) e, itmax, n
IF (endOfFile ibig sabhin end of file na..

5. if you want everything to be in just one program.. internal functions, subroutines.. you have to MAKE SURE THAT EVERYTHING IS DECLARED.. i mean.. there are variables that will be globally available.. so if you dont want it.. then declare a local one :D okie okei??!??

6. INITIALIAZE Variable.
Remember that you are not using JAVA. so an integer will not be initialized to 0 at declaration.. so if you are going to use something like f = f + ... then you neeed to initialize f first.. or else you get a garbage :P

7. Local variable Initialization
Wel.. another difference between fortran and java.. is that.. in fortran.. once you call a function that have an initialization at declaration.. the second time that you call that function.. d na sya naka init sa ganun.. :( it can remember the previous one.. :(.. so make sure na dapat.. lagi.. initialize mo nlng.. wag na sa declaraton.. wag dun. okie okie?? dapt after.. hehehe

8. FILE handling nga pala
OPEN(UNIT=fUnit,FILE=pathName,IOSTAT=openFile)
CLOSE(UNIT=fUnit)

9. If you're using notepad.. dapat may six spaces sa harap.. para mag blue. haha. :D

http://www.spy-hill.com/~myers/help/boinc/boinc-on-windows.html

-Chris

XCode Toolsとかが入っている事が前提となります。

gfortran-intel-leopard-bin.tar.gz (Intel Mac gfortran only)をHigh Performance Computing for Mac OS Xから落として自分のホームフォルダにおきます。

$ sudo tar zxvf gfortran-intel-leopard-bin.tar.gz -C /

1. Xcode Toolsのインストール

iMac付属のDVDから。或は、Apple's developer siteからdmgを落として。

2. PATHの設定

export PATH=/opt/local/bin:/opt/local/sbin:$PATH
export DISPLAY=:0.0

Mac24:~ ray$ env
MANPATH=/usr/share/man:/usr/local/share/man:/usr/X11/share/man
TERM_PROGRAM=Apple_Terminal
TERM=xterm-color
SHELL=/bin/bash
TMPDIR=/var/folders/a2/a2rMgf97Gpi9c0C7OP7+rU+++TI/-Tmp-/
Apple_PubSub_Socket_Render=/tmp/launch-a35KgQ/Render
TERM_PROGRAM_VERSION=240
USER=ray
COMMAND_MODE=unix2003
SSH_AUTH_SOCK=/tmp/launch-p9K05M/Listeners
__CF_USER_TEXT_ENCODING=0x1F5:1:14
PATH=/opt/local/bin:/opt/local/sbin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
PWD=/Users/ray
LANG=ja_JP.UTF-8
SHLVL=1
HOME=/Users/ray
LOGNAME=ray
DISPLAY=:0.0
SECURITYSESSIONID=xxx040
_=/usr/bin/env

3. MacPortsのインストール

The MacPorts Project -- Download & Installationから。MacPorts-1.6.0-10.5-Leopard.dmgだすた。

4. MacPortsのupdate

$ sudo port selfupdate

iMac24:~ ray$ sudo port selfupdate
Password:

MacPorts base version 1.600 installed

Downloaded MacPorts base version 1.600

The MacPorts installation is not outdated and so was not updated
selfupdate done!

5. G95のインストール

$ sudo port -d install g95
7分くらいで完了。
あとはビルドするだけ。
日本語マニュアルによると、

簡単な例:
g95 -c hello.f90
hello.f90 をコンパイルして, hello.o という名前のオブジェクト・ファイルを作る.
g95 hello.f90
hello.f90 をコンパイル, リンクし a.out (Unix) あるいは a.exe (Windows) という実行ファイルを生成する.
g95 -c h1.f90 h2.f90 h3.f90
複数のソース・ファイルをコンパイル. 問題がなければ, オブジェクト・ファイル h1.o, h2.o 及び h3.o ができる.
g95 -o hello h1.f90 h2.f90 h3.f90
複数のソース・ファイルをコンパイルし, これらをリンクして hello (Unix) あるいは hello.exe (Windows)という名前の実行ファイルを生成する.

参考サイト ひよこっ!: MacPortsでg95をインストール

Over time, Python, C#, C++, and Java replaced Assembler, PL/I, COBOL, and Fortran, speeds of processors and communications increased exponentially, "graphics" supplanted character-only terminals, memory and storage costs plummeted, and "distributed computing" became in vogue, putting more computing power closer to the user, and efforts focused on trying to get things off the "ancient" and hard-to-maintain mainframes. Then came the PC revolution, and for a while decentralization was all the range, and mainframes became very much "old school" and passé, their death warrants having been signed by columnists long ago. Then, people began to figure out two things: (1) they were putting a lot of complexity onto desktops, and this engendered mucho frustration, and required an expensive army of technicians and "help desks" to maintain some semblance of usability, and (2) those desktops had lots of power that went mostly unused most of the time. As Internet service became more reliable, as connection speeds increased, and as specialists like Google and Amazon learned to build multi-acre "farms" of cheap computers reliably and inexpensively, wise men and women figured out that "software as a service" (SAAS) had many potential benefits, and the transparent distribution of the centralized services was imperative to keep pace with wildly fluctuating changes in demand. Thus was born "cloud computing" which is the current rage.

The wizened old GoogleGazer is, once again, reminded, as the french proverb says, plus ca change, plus c'est la meme chose (the more things change, the more they remain the same). In computing, things stay the same, but the terminology changes, the mechanics of execution get slicker, and the costs of hardware decline inexorably as Moore's law has has proved itself for a half a century now. But the bottom line seems to be that we have now come full circle, and for good and for ill, we are moving with alacrity back to the era of centralized software hosting, centralized applications, and centralized control.

This is not necessarily a bad thing. The fundamental needs addressed by the grandfathers of today's young tiger developers haven't changed too much. People still seek powerful but simple to use and reliable solutions, and for the most part, they just want to get their work done without worrying too much about the complexity under the covers. As Samuel Clemens ("Mark Twain") famously observed as he got older, he was amazed at how much his dad had learned in the years between when he himself was 16 and 21! Not all old ideas are bad ideas, and implementing them with new technology can be a downright good idea.

-Chris

DO control-var = initial-value, final-value, [step-size]
statements
END DO

EXAMPLE

DO Count = -3, 4, 2
WRITE(*,*)  Count, Count*Count, Count*Count*Count
END DO

DO - EXIT
DO
statements-1
EXIT
statements-2
END DO

NESTED DO

INTEGER :: i, j

DO i = 1, 9
DO j = 1, 9
WRITE(*,*)  i*j
END DO
END DO

Handling End of File

INTEGER :: io, x, sum
sum = 0
DO
READ(*,*,IOSTAT=io)  x
IF (io > 0) THEN
WRITE(*,*) 'Check input.  Something was wrong'
EXIT
ELSE IF (io < 0) THEN
WRITE(*,*)  'The total is ', sum
EXIT
ELSE
sum = sum + x
END IF
END DO

The use of Cycle as Continue

DO control-inf
statements-1
CYCLE
statements-2
END DO

IF-ELSE

IF (logical-expression) THEN
   statements-1
ELSE
   statements-2
END IF

EXAMPLE:

INTEGER :: Number

READ(*,*)  Number
IF (MOD(Number, 2) == 0) THEN
   WRITE(*,*)  Number, ' is even'
ELSE
   WRITE(*,*)  Number, ' is odd'
END IF

IF (logical-expression) one-statement

EX.  IF( X > Y) write(*,*)

SELECTIVE CASE

EX 1

INTEGER :: Class

SELECT CASE (Class)
   CASE (1)
      WRITE(*,*)  'Freshman'
   CASE (2)
      WRITE(*,*)  'Sophomore'
   CASE (3)
      WRITE(*,*)  'Junior'
   CASE (4)
      WRITE(*,*)  'Senior'
   CASE DEFAULT
      WRITE(*,*)  "Hmmmm, I don't know"
END SELECT
WRITE(*,*)  'Done'

EX 2

SELECT CASE (Number)
   CASE ( : -1)
      Sign = -1
   CASE (0)
      Sign =  0
   CASE (1 : )
      Sign =  1
END SELECT
WRITE(*,*)  "Sign = ", Sign
NOTE:   THE ":" symbolizes the range.. pwde rin mag comma sa loob ng case, pwde din ang string.. :D

Availabe Data Types:
integer list of variables
real list of variables
double precision list of variables
complex list of variables
logical list of variables
character list of variables

*variables: no more than 31 characters, only [a-zA-Z0-9_] and starts with a letter. case insensitive

parameter (pi = 3.14) -> for the constant.. cant be change once declared

***********Body***********

program prog_name
IMPLICIT NONE
variable declarations
statements, algo
end program prog_name
*************************

Constants

for integer: 1, 0, +200, -300

for real: 2.0E6, 3.333E-1 (E = 10^)

for double: 2.0D6

for complex: (2, -3) , (1., 9.9E-1) (first part is the real or integer then the second is the imaginary)

logical : .TRUE. , .FALSE.

string: 'HELLO world' //to use the ' need to escape it. so double ''

Expressions:

operand operator operand ==> x + y**2 (** here is power)

How to multiply two real variables x and y using double precision and store the result in the double precision variable w:

      w = dble(x)*dble(y)

typecasting function: int, real, dble, ichar(convert char to integer), char (viceversa)

others:

comments: use '!'

continuation of lines: use '&'

declaration of variables:

real :: a, b, c

CHARACTER(LEN=10) :: City, Nation*20, BOX, bug*1 (default is 10, Nation is 20, bug is 1)

CHARACTER(LEN=*) :: Title, Position (* means that the size of this will be declared later)

INTEGER, PARAMETER :: A = '1'

CHARACTER(LEN=*), PARAMETER :: A="JEN", B="ZHEN" ==> A will have 3, B will have 4

Arithmetic: **, + , -, /, *

Relational: ==, /=, <, <=, >, >=

Logical: .NOT. .AND. .OR. .EQV. .NEQV.

FUNCTIONS:

READ DATA
READ(*,*) var1, var2, ..., varn

WRITE DATA
WRITE(*,*) exp1, exp2, ..., expn
WRITE(*,*) 'Angle = ', Angle (comma separated)

Concatenation: use '//'
Substring: LeftHand(3:5) = "abc": the new content of LeftHand is "12abc67890".

then after downloading the compiler. put the .exe to the C:\ folder, and then install it. Make sure that you put the files in the C:\ so that there will be no spaces in the directory path.

go to the system -> add new variable "LIBRARY_PATH", include the lib folder of the g95.. thats it!

to try the compiler.. type in the notepad this:

program Hello
print *, 'Hello, world'
end program Hello

then save it as hello.f90
then to compile.. go to command prompt and type: g95 -c hello.f90
to see the output: g95 -o out hello.f90
then type out to see the result.

Alright... let's get loopy in Fortran. It's been 5 years since I looked at a Fortran program, and 5 is close enough to infinity.

      program count
      integer i, n

c This program counts

      write (*,*) 'Count to:'
      read  (*,*) n
      do 10 i = 1, n
         write(*,*) i
 10   continue

      stop
      end

I'm already seeing cruft that I don't like about Fortran. The word "continue" literally does nothing in Fortran. The line "do 10 i = 1,n" will begin a counting loop until a line beginning with label "10". The problem is the label itself. I shouldn't have to use labels where labels aren't needed. The loop can be rewritten without the labels:

      do i = 1, n
         write(*,*) i
      end do

It's shorter. It's cleaner. It has no labels. I like it. Sadly, this is not standard Fortran. Let's go a while-loop:

      i = 1
      do while (i .LE. n)
         write(*,*) i
         i = i + 1
      end do

Again... we have clean, easy to read Fortran. There seems to be an extraneous "do" before the "while", but other than that, it's good code. Again, this isn't standard Fortran.

Standard Fortran is ugly. Legal "while" loops in Fortran don't use the word "while." They use "if." Blah. I feel like I'm writing code for my old TI-82 when I look at this code.

      i = 1
 10   if (i .le. 10) then
        write (*,*) i
        i = i + 1
        goto 10
      end if

This is a pre-conditional loop. The same loop can be written as a post-conditional loop.

      i = 1
 10   write (*,*) i
      i = i + 1
      if (i .le. 10) then
        goto 10
      endif

I don't see a way out of writing loops in Fortran without resorting to labels or non-standard code. See this post? I have to give a half-hour talk on just this content. Oh boy. How do I make this exciting?

Linux systems adhere to POSIX,[20] SUS,[21] ISO and ANSI standards where possible. To date, however, only the Linux-FT distribution has been POSIX.1 certified.[22]

Free software projects, although developed in a collaborative fashion, are often produced independently of each other. However, because the software licenses explicitly permit redistribution there is a basis for larger scale projects that collect the software produced by stand-alone projects and make this software available together in a Linux distribution.

A Linux distribution, commonly called a “distro”, is a project that manages a remote collection of Linux-based software, and facilitates installation of a Linux operating system. Distributions are maintained by individuals, loose-knit teams, volunteer organizations, and commercial entities. They include system software and application software in the form of packages, and distribution-specific software for initial system installation and configuration as well as later package upgrades and installs. A distribution is responsible for the default configuration of installed Linux systems, system security, and more generally integration of the different software packages into a coherent whole.

Community

Linux is largely driven by its developer and user communities. Some vendors develop and fund their distributions on a volunteer basis, Debian being a well-known example. Others maintain a community version of their commercial distributions, as Red Hat does with Fedora.

In many cities and regions, local associations known as Linux Users Groups (LUGs) seek to promote Linux and by extension free software. They hold meetings and provide free demonstrations, training, technical support, and operating system installation to new users. There are also many Internet communities that seek to provide support to Linux users and developers. Most distributions and open source projects have IRC chatrooms or newsgroups. Online forums are another means for support, with notable examples being LinuxQuestions.org and the Gentoo forums. Linux distributions host mailing lists; commonly there will be a specific topic such as usage or development for a given list.

There are several technology websites with a Linux focus. Linux Weekly News is a weekly digest of Linux-related news; the Linux Journal is an online magazine of Linux articles published monthly; Slashdot is a technology-related news website with many stories on Linux and open source software; Groklaw has written in depth about Linux-related legal proceedings and there are many articles relevant to the Linux kernel and its relationship with GNU on the GNU project's website. Print magazines on Linux often include cover disks including software or even complete Linux distributions.[23][24]

Although Linux is generally available free of charge, several large corporations have established business models that involve selling, supporting, and contributing to Linux and free software. These include Dell, IBM, HP, Sun Microsystems, Novell, and Red Hat. The free software licenses on which Linux are based explicitly accommodate and encourage commercialization; the relationship between Linux as a whole and individual vendors may be seen as symbiotic. One common business model of commercial suppliers is charging for support, especially for business users. A number of companies also offer a specialized business version of their distribution, which adds proprietary support packages and tools to administer higher numbers of installations or to simplify administrative tasks. Another business model is to give away the software in order to sell hardware.

Programming on Linux

Most Linux distributions support dozens of programming languages. The most common collection of utilities for building both Linux applications and operating system programs is found within the GNU toolchain, which includes the GNU Compiler Collection (GCC) and the GNU build system. Amongst others, GCC provides compilers for Ada, C, C++, Java, and Fortran. The Linux kernel itself is written to be compiled with GCC. Proprietary compilers for Linux include the Intel C++ Compiler and IBM XL C/C++ Compiler.

Most distributions also include support for Perl, Ruby, Python and other dynamic languages. Examples of languages that are less common, but still well-supported, are C# via the Mono project, and Scheme. A number of Java Virtual Machines and development kits run on Linux, including the original Sun Microsystems JVM (HotSpot), and IBM's J2SE RE, as well as many open-source projects like Kaffe. The two main frameworks for developing graphical applications are those of GNOME and KDE. These projects are based on the GTK+ and Qt widget toolkits, respectively, which can also be used independently of the larger framework. Both support a wide variety of languages. There are a number of Integrated development environments available including Anjuta, Code::Blocks, Eclipse, KDevelop, Lazarus, MonoDevelop, NetBeans, and Omnis Studio while the long-established editors Vim and Emacs remain popular.

-Chris

06142008429, originally uploaded by William WM.

Picked this up at Powell's Technical Books for $2.00!

Chock full of good FORTRAN code and optimizations for S/360 computers. Interestingly enough, the data structures themselves hold up quite nicely (binary trees, linked lists, etc) despite the book being over 35 years old!

In a more "awkish" venture, my old boss who was now at a company that made microprocessor hardware emulators, asked me if I could do a project for him. They were converting from a 6809-based emulator to a 68000-based one and needed to convert thousands of lines of instruction set encode and decode tables from 6809 assembly language to C. He had estimated a month to do the task assuming it would be done in C. I did it in about three days using awk and sed.

...

So, I was now a C programmer and an awk scripter. The problem was that there was a gap in my toolset. Unlike Fortran V where I even found a way to build and execute assembly language code within the Fortran framework, if I wanted to do anything other than process characters, I had to write the code in C. In most cases this wasn't bad but sometimes 99% of a task could easily be done in a few lines of awk but would require a lot of C.

Well, in 1999 I had the opportunity to interview Guido von Rossum, the father of Python. While I had already been playing with Python, my chat with Guido (a lot more than an interview) inspired me to get more serious. The interview actually addresses what is wrong with awk and Perl so I won't go into more detail here.

While my life in the last almost ten years has not been primarily programming, I do turn to Python as my tool of choice. Some of what I have done can be called scripting but not all. For example, I implemented a credit card processing system for Visanet (the nastiest of all possible credit card protocols) in Python. I also have done some work with Karrigell, a web framework implemented in Python.

Ok, I talked about awk's limitations and Guido helped me beat up Perl in the interview. Note that my default comment about Perl is that if you don't know regular expressions and UNIX/Linux shell programming, Perl is not the best way to get to knowing a scripting language. So, what's left? The obvious choice is Ruby.

Well, this is where my long, boring history of my Pascal experience fits in. First, let me say that I like Ruby. It is a nicely-designed and very clean language. If you don't already know Python, you should seriously give it a try. But, is it better than Python? I think not.

Ruby, while not really new, just hasn't done as much work as Python. Much like Pascal 30 years ago, Ruby looks good on paper. Pascal's claim to fame was that there were no surprises. Ruby's is that it is pure object oriented. Those are both good things. But, as Ruby does more heavy lifting, it seems likely to me that it will have to evolve. That is, its purity will get subverted much like the purity of Pascal did.

In any case, I will stick with Python. It has certainly evolved over the years but that evolution feels like taking a solid base, seeing what makes it more useful and cleanly handling the evolution. To me, Python 2.5 is easier to explain to someone that Python 1.5.2.

A very interesting piece; take a look!