Typo LAMDA --> LAMBDA

[flatstik]

bz/make_line.F90:    points(npoints)*5 =  (/"GAMMA", "DELTA", "LAMDA", "SIGMA" /), &
reactions/ef.F90:   !  SOLVE ITERATIVELY FOR LAMDA
reactions/ef.F90:   !  INITIAL GUESS FOR LAMDA IS ZERO EXCEPT NOTE THAT
reactions/ef.F90:   !  LAMDA SHOULD BE LESS THAN EIGVAL(1)
reactions/ef.F90:10030   format (1 x, "LAMDA THAT MAXIMIZES ALONG TS MODES =   ", f15.5)
reactions/ef.F90:        write (iw,*) "NUMERICAL PROBLEMS IN BRACKETING LAMDA", eone, bl, &
reactions/ef.F90:        write (iw,*) "TOO MANY ITERATIONS IN LAMDA BISECT", bl, bu, &
reactions/ef.F90:        call mopend ("TOO MANY ITERATIONS IN LAMDA BISECT IN EF")
reactions/ef.F90:        write (iw,*) "TOO MANY ITERATIONS IN LAMDA BISECT", bl, bu, &
reactions/ef.F90:        call mopend ("TOO MANY ITERATIONS IN LAMDA BISECT IN EF")
reactions/ef.F90:10040 format (1 x, "LAMDA THAT MINIMIZES ALONG ALL MODES =  ", f17.9)
reactions/ef.F90:    write (iw,*) "NUMERICAL PROBLEMS IN BRACKETING LAMDA", eone, bl, bu, &
reactions/ef.F90:   !           BOTH LAMDA SEARCHES FAILED, GO FOR FIXED LEVEL SHIFTED NR
reactions/ef.F90:        write (iw,*) "TOO MANY ITERATIONS IN LAMDA BISECT", bl, bu, lamda, &
reactions/ef.F90:        call mopend ("TOO MANY ITERATIONS IN LAMDA BISECT IN EF")

[godotalgorithm]

This may be more of a programmer conceit than a typo (so that all of the Greek letters regularly in use have 5 characters), but it really doesn't need to be like that. One way or another, this will be corrected in the next patch release, tentatively near the end of this week.

This might be a good opportunity to learn about how to make a Pull Request on GitHub, as fixing this problem is almost completely trivial (the points strings would need to be resized from 5 to 6). There is certainly a small learning curve to making a Pull Request, but it is a useful skill to have.

[godotalgorithm]

Fixed by #56.