News for hackers. Stuff that matters.
Re:Global Forecast System source code by noobermin on Saturday January 31, 2015 @01:38PM (#8977541)
Fortran 90 is still the language computational stuff is made in today. I'm not convinced, however, that that choice is really for performance reasons over cultural reasons.

Still, Fortran 90 is hell of a lot better than Fortran 77, which unfortunately is the language of choice for some of the people I'm being asked to work with.

Re:Global Forecast System source code by upmygreen on Saturday January 31, 2015 @03:40PM (#8978024)
I'm a part of this community. I assure you speed in number crunching is a huge reason this is written in F90.
Re:Global Forecast System source code by tankenmate on Saturday January 31, 2015 @04:53PM (#8978225)
Indeed, automatic (and largely implicit) use of SIMD and OpenMP by the compiler is very very good with F90 compared to almost all other widely used languages.
Re:Global Forecast System source code by noobermin on Saturday January 31, 2015 @08:34PM (#8978809)
I'm curious (really curious, although this might sound like a troll), have you ever tried a benchmark test on this? Things like this [0] come up every so often, and make me wonder about the efficiency advantage for coding in Fortran.

This is also relevant and insightful [1]. The top answer talks about Fortran's strict aliasing semantics.

[0] http://unriskinsight.blogspot.com/2014/06/fast-functional-go...

[1] http://stackoverflow.com/questions/146159/is-fortran-faster-...

Re:Global Forecast System source code by greglindahl on Saturday January 31, 2015 @10:24PM (#8979054)
[0] is a classic example of comparing programming languages attacking a problem with different algorithms.

I see that the author insults Fortran a couple of times, and I don't seen any indication that they tried to implement the better algorithm in Fortran. Did I miss something?

Re:Global Forecast System source code by Loic on Sunday February 01, 2015 @05:38AM (#8979623)
If you look at Julia[0] they have quite a lot of performance benchmarks and you will see that Fortran is always at or near the top. What is really important, from a numerical code point of view, is that with Fortran it is easy to be at the top by operating on matrices and vectors etc. You do not have to torture your mind and think too much to optimize your code, "remove the IF in the loops" is often just what you need.

I am writing code in Fortran 77/90 every day, I really really enjoy it. Calling your Fortran code from Python is also so easy that you can really have clear cut between data management in Python and computational work in Fortran.

[0]: http://julialang.org/

Re:Global Forecast System source code by panamafrank on Saturday January 31, 2015 @02:31PM (#8977734)
inertia would have something to do with it, like there's an 'anal.sh' file which even made it into the documentation.

I can't seem to access the SVN repo, I wonder how/if they unit tested it all.

Re:Global Forecast System source code by 123456anon on Saturday January 31, 2015 @03:21PM (#8977952)
As somebody that used to work at NOAA (not at NCEP, but worked with a lot of people at NCEP).

No, there is no unit testing!

anal.sh is short for analysis.