51–60 of 65 posts
My biggest criticism of this work is that it does not consider C++. Most of the big HPC projects today are written in C++, not C, and to the best of my knowledge this transition happened in the 90s.
My experience is limited to one single field, but all weather prediction models and climate models that I know of, are in Fortran. And I would count them as big HPC projects.
GitHub repo with all of the code: https://github.com/mrfloya/thesis-ba Most interesting part of the thesis, for me, is page 42: > In this case it was even an advantage that the Rust version was developed last since it revealed a critical error in the other implementations. Null strikes again!
n1_idx, ok1 := g.nodeIdx[n1]
n2_idx, ok2 := g.nodeIdx[n2]
if !ok1 || !ok2 {
Earlier quoted context omitted.
Not Fortran?
I have not done a census of the various libraries around, but all of the free finite element libraries in common use (deal.II, libmesh, and FEnICs come to mind first) are written in C++. I suspect Fluent and Abaqus are written in C (maybe Fortran?) but they are a bit older. Trilinos is another C++ example, while PETSc and HYPRE are written in C. My tentative conclusion from this is that newer projects tend to use C++…
Most users are usually fine with whatever the GUI allows and a bit of Python, but for those of us developing new models, Fortran is probably the most useful language, followed by C++.
Earlier quoted context omitted.
Yes, because the point is being able to write (on a resume): successfully presented thesis on "Evaluation of C, Go, and Rust in the HPC environment". The advisors should have encouraged a smaller and more manageable scope with a more thorough methodology where the results would actually be worth something.
The goal is for the student to get some experience with performing their own research wherever that may lead them. This is actually a pretty impressive piece of independent work for an undergrad.
You mean it has nothing to do with learning correct methodology or actually doing real research?
The problem with reading this in BS thesis form is that it hasn't gone through the wringer enough. Most of the performance comparison results vs C are bogus because (to its credit, as noted), the author accidentally compiled some important support libraries for the C version without optimization and used those on the cluster. Oopsie. As briefly mentioned in the previous chapter this performance regression might have…
Hey author of the thesis here. You are correct this was definitely an oversight and I would have redone the measurements if time allowed for it. However I just want to state that the libaries were built with optimizations just not on the target platform which might not have been clear from the qoute.
Earlier quoted context omitted.
The goal is for the student to get some experience with performing their own research wherever that may lead them. This is actually a pretty impressive piece of independent work for an undergrad.
> The goal is for the student to get some experience with performing their own research wherever that may lead them. You mean it has nothing to do with learning correct methodology or actually doing real research?
Earlier quoted context omitted.
> The goal is for the student to get some experience with performing their own research wherever that may lead them. You mean it has nothing to do with learning correct methodology or actually doing real research?
"Correct methodology" and "real research" are very subjective things. We often judge too harshly, and as long as the paper is not misleading, you can judge it's merits directly without resorting to non-science.
That's exactly the attitude emblematic of the portion of academics producing worthless output.
Here is a recent reference: http://www.nature.com/news/psychology-journal-bans-p-values-...
Not a methodological problem?
Earlier quoted context omitted.
"Correct methodology" and "real research" are very subjective things. We often judge too harshly, and as long as the paper is not misleading, you can judge it's merits directly without resorting to non-science.
> "Correct methodology" and "real research" are very subjective things. That's exactly the attitude emblematic of the portion of academics producing worthless output. Here is a recent reference: http://www.nature.com/news/psychology-journal-bans-p-values-... Not a methodological problem?
The article submitted was not peer reviewed, and could very well be bad science, but I think accusations of non-science are not very productive and do not provide feedback in how to do better.
GitHub repo with all of the code: https://github.com/mrfloya/thesis-ba Most interesting part of the thesis, for me, is page 42: > In this case it was even an advantage that the Rust version was developed last since it revealed a critical error in the other implementations. Null strikes again!
He would have found the problem in Go too if he was using the comma-ok form: n1_idx, ok1 := g.nodeIdx[n1] n2_idx, ok2 := g.nodeIdx[n2] if !ok1 || !ok2 { When you do not use the comma-ok form, you are specifically asking the map to return the zero value for non initialized elements (which is something fine to do in many cases).