Crucial Computer Program for Particle Physics at Risk of Obsolescence
quantamagazine.org
quantamagazine.org
But if the code were available... then you could quickly test out if something is worth pursuing.
So another way of handling this to contribute advancement at scale is "exercise left to the reader", and then we readers should publish too.
R&D in big tech should contribute as academia does.
We have our "Chief Scientists" and "Principal Engineers" titles that recognize, essentially, a tenure track, that should be on the merits of publishing code implementing new techniques.
https://bioconductor.org/packages/release/bioc/html/edgeR.ht...
This seems very pessimistic view. FORM was written by mortal humans (with much cruder tools!) in the first place, there is no reason to believe it couldn't be done again if need be and even improved in the process; its not some irreplaceable artifact descended from heavens.
On the other hand, I imagine it would take bit more than just maintenance to make the 30 year old C codebase welcoming for new physicists to work on.
Take Electron,
I'd rather not, thanks. Unless you meant in the sense of "take it out back and shoot it", in which case we're bloody trying already, it's not that easy.
I have a hunch that FORM is not made up of easy to grok software designs or it would probably be true that other folks would have contributed in a bigger way regardless of academic stimuli. If that is indeed the case, as is common in research-academia software product, then tie a bow on it and send it off to the Smithsonian.
I would be really quite surprised if some enterprising 19 year old whiz-bang genius from Iceland didn't re-write it in Mathematica.
Still would be a net loss for science, as a critical piece of software infrastructure would become tied to Wolfram's proprietary black box. Also I think academic software benefits less often from a random precocious outsider fixing things, because in addition to good programming knowledge, it requires a fair amount of subject matter expertise, what is rare to be found both in the same person.
A bug in the code would throw doubt on every paper published with it so the expected value for any individual rewriting it or making any modifications is extremely negative for their career.
Sure, but how long will that take and how robust will the result be? Given the description of the design, it basically sounds like it does efficient block-level storage management in order to handle the petabytes of data that it might need to churn through, so basically you're reimplementing a DB storage engine, which is no small feat to get right and performant.
Furthermore, is there a test suite to validate that the FORM2.0 yields the same results for all past papers?
These problems are not unsolvable but they're not trivial either.
Yet another example of administrators imposing a one-size-fits-all rule and elevating convenience over quality. Every academic I know hates how academia works, but they balk every time I suggest networking with people outside their disciplinary silos to dethrone the administrators. It's like the smartest people in the world are stymied by the idea of a collective action problem that requires working across disciplinary boundaries. For a long time I thought I was missing something fundamental about the complexity of the issue, but after 10 years of asking it seems to literally be that individuals are afraid of getting punished and they don't have any ideas beyond supporting the occasional strike action (that will leave things more or less as they are). I don't get it.
You'd have thought something more efficient would've turned out by now, since there was barely a sensible definition of efficiency back then.
There is some work in that direction (look up 'Amplituhedron') but overall it's not that surprising that physicists are using computers to do the same math with much more precision than they could before rather than shaking up the fundamental mathematical tools of their field which have stood since the 1600s.
It’s at risk of neglect/disrepair/falling behind. If it’s important enough and something breaks hard you better believe someone will pick it up, but not until it’s a forced issue.
I mean not only computer hardware, which is also non cheap, but budgets for experimental hardware, which not all countries can handle.
So, if program is really important, they could rearrange budgets and give some finances for software.
It looks like it's basically a fancy term-rewriting system.
wonder what is this application memory management scheme mentioned in the article is ? Overlay as in those days? https://en.wikipedia.org/wiki/Overlay_(programming)
Hm. I thought Stirling's approximation shows they are approximately of same growth?