Philip L. Roe (1938 - 2026)

Hiroaki Nishikawa (also a Fortran programmer) wrote on X,

Phil Roe (1938–2026), Professor of Aerospace Engineering at the University of Michigan, was my advisor during my doctoral study. I greatly admired his thorough approach: he was never satisfied with simply getting a scheme to work, but would dig into the underlying reasons why it worked until he fully understood them, always striving for excellence. Now so many wonderful memories are coming back to me.
One day, when he handed me a book and said, “You should read this,” I replied, “Then I’ll return this one,” handing back a book I’d borrowed earlier, and Professor Roe said, “Conservation! (Conservation!)” and we both laughed.
After graduation, I worked as a postdoc with him for about six years. One day, he came over to me and said, “I’ve derived a third-order approximation,” showing me his handwritten notes. I replied, “Well, I’ve derived a fifth-order approximation,” then he said, “You win!” and we both laughed.
In the photo, I’m holding a regular dodecahedron that he made himself by carving it from wood. He gave it to me as a gift when I left Michigan. I asked him, “Could you sign it so people know who made it?” but then he replied, “I can’t do that. It would break the symmetry.” and we both laughed. I still treasure that dodecahedron to this day.

4 Likes

I have only read two or three papers by Roe; he helped me indirectly with his replies on Stack Exchange in a thread about implementing a finite volume method in axisymmetric coordinates.

Here are two quotes that I saved from his works. One his from his autobiography:

These days the Finite Element method provides a popular viewpoint because, with only finitely many degrees of freedom, we can define an approximate solution everywhere. All processes of interpolation, integration and differentiation can be uniquely determined by operating on the function that is determined by the trial functions and their amplitudes. However, it was not immediately apparent how to combine this with a physically motivated strategy.

In the Finite Difference method on the other hand, the solution is defined only at points, and we are allowed to fill in between the points in whatever way we please. I began to consider the question, if you are given two adjacent points in a finite difference method, what assumptions should you make about what happens between them? The traditional approach is simply to assume that they are connected through some sufficiently differentiable function, but in compressible flow they might be separated by a shock. It seemed to me then, and does so still, that the Finite Difference viewpoint has the merit of honesty, admitting that there is a limit to what we can infer from finite information, and this leaves us with some ”wiggle room”.

And a second is a reply to the question “What are the conceptual differences between the finite element and finite volume method?”, where Roe writes:

The basic difference is simply the meaning to be attached to the results. FDM predicts point values of any aspect of the solution. Interpolation between these values is often left to the imagination of the user. FVM predicts averages of conserved variables within specific control volumes. Hence it predicts the integrated conserved variables and can be shown to converge to weak (discontinuous) solutions. FEM gives a set of discrete values from which an approximate solution can be deduced unambiguously everywhere by invoking a set of basis functions. Usually, but not necessarily, the variables involved are conservative. It is possible to have finite difference methods that are conservative in some sense, according to a particular quadrature rule.

These are matters of definition. There are many variations of all three methods. Not every method is cleanly of one type, and the details vary between application areas. Researchers inventing a new method employ those tools that will help to provide the properties that they are looking for. It is, as you seem to have found, difficult to find an authoritative discussion and it would be difficult for me to provide one. The best advice that I can give is to continue reading, without expecting a totally clear answer, but giving credence to the things that make sense to you.

1 Like

I do not want to “heart” this post, and I certainly do not want to “thumbsup”, or “laugh”, or “clap”. I feel like in the long run, Fortran community is going to be the first programming community that needs a RIP emoji.

May you rest in peace, Dr. Philip L. Roe.

1 Like

Truly sad news. Dr. Roe was one of those rare pioneers whose work fundamentally changed how we do CFD. To me his work on Riemann solvers and the resulting explosion in research in that area that his work inspired is one of the major accomplishments in the history of CFD. I never met him but did get to hear him give papers and speak a couple of times. He came across as a true scholar and gentleman.

1 Like

I know, I thought about it too. Then I “hearted” it to appreciate Ivan posting it.

1 Like

CFD was never mentioned in my undergraduate physics program, and I wish I had studied it. I asked an ex-physicist decades later why CFD was not part of the physics curriculum (at least in the U.S.), and he said that when a branch of physics becomes useful it gets transferred to the engineering department.

1 Like

“when a branch of physics becomes useful it gets transferred to the engineering department.” And when a branch of mathematics becomes useful it gets transferred to the physics or computer science department.

1 Like

This is outside of my area of study, so I’m unsure how to think of this. I would think that the study of Navier-Stokes equations, Reynolds number, laminar flow, turbulence, etc. are all legitimate topics of physics. But then when those equations are numerically approximated, with finite difference methods, finite element methods, with variable step differential equation methods, etc. it steps outside of physics into numerical analysis. Then when those are applied to actual applications, designing aircraft, or jet engines, or race cars, or oil refineries, etc. it is no longer just an academic problem and it becomes an engineering problem. Certainly the introduction of computers must have scrambled all of this over the last 50 years. How do people in this field think of those different aspects of this problem?

I have said occasionally that computer science is the study of everything you can do in a computer except floating-point arithmetic. I was a student in NZ and UK where the dividing line between maths and physics has been blurred for a long time. I once spent a sabbatical at Imperial College London working on bubbles rising in liquids in the maths department and found helpful people there and in chemical engineering and metallurgy (think of a blast furnace). Hawking and Dirac both earned their pay in a faculty of mathematics. Newton would have earned his there too if Cambridge had had faculties in his time. Going back about 2000 years, Archimedes did both pure mathematics (approximating to pi) and theoretical engineering (stability of floating boats). He never had to deal with university admin though :slight_smile:

2 Likes