2 ms·
Well, actually, there might be something about Fortran that makes it harder to maintain than other new programming languages. I don't know but it would have be
by ilaksh 6y ago
Well, actually, there might be something about Fortran that makes it harder to maintain than other new programming languages. I don't know but it would have been interested to hear such details in this article.
I believe if there is a lot of math in a simulation codebase that can't easily be verified and you aren't sure if it's all necessary, then you should not assume that the simulation is correct. So there is where I think the instinct to modernize could lead to objectively better software.
The math that needs to be verified and might need to be changed should be easy to find and change and verify. To improve the feedback loop, having an interactive visualization may be objectively much better than a batch job that requires a long wait and another program to create a graph.
So I don't know the actual program, but it's quite possible that you would be able to more effectively predict the weather if you changed it completely to work like this:
1. Pull out the core equations and put them in a UI (not necessarily editable structurally).
2. Add an option to select different equations/modeling strategies. Show the equations prominently.
3. Make the parameters for the equations show up in the UI.
4. Convert the system to use CUDA or OpenCL and get them a brand new Nvidia 3090 or something.
So now they have an interactive parallelized fast simulation where the equations/strategies and parameters used are prominently displayed.
I think the objection is going to be that now it's harder to change the equations. And if they really change the equations a lot then that is a valid argument. If they change the equations once every ten or twenty years, or just forget about the old ones and ignore their effects while piling on more equations, then that argument doesn't necessarily hold water.