Remastered 1964 films show origins of Stanford Linear Accelerator Center
www6.slac.stanford.edu
www6.slac.stanford.edu
Andy recently remastered these. I hadn't seen the first one before, but the second one is 100% work 42 minutes of your time. The narration is great, the topic is great, the pictures are great. Unlike current videos, it's happy to dwell on shots for more than 2 seconds, in silence, while people are actually working - instead of the pretend-working for a camera shot with dialog or futuristic music to fill the silence.
I really wish they'd have created more of these types of videos over the years, but $84k in today's dollars for a video would be a lot of EPO budget these days, in addition to 42 minutes being an eternity. It's a great documentary, and, I think, a treasure.
You might think a CS research group is a little odd at a linear accelerator center, but one of the things we learned when the forefront of particle physics moved to the LHC is that we have to diversify. So SLAC's mission is a lot more broad now than it was at the time. Also, I'd make the observation that there are a lot of problems in programming languages, compilers, OSes, etc. that are a lot less solved than you might think, and because a relatively small fraction of the CS community is paying attention to scientific computing there are a lot of areas that are surprisingly underdeveloped compared to the relatively well beaten path of commercial computing.
Contact info in profile if interested.
I've developed programs for:
Gathering and analyzing climate data at scale
Sample collection robotics
Low power data logging
SDR
and many more.
The really cool thing is that you dont need a phd in CS to be effective and enable other scientists success.
One question for you, eslaught:
Do you have any specific requirements that would immediately disqualify a candidate?
I would reframe this slightly: What are the fundamental open problems in computer science that prevent our existing tools from working for scientists more generally? E.g. are there constraints (like the need for high performance in certain applications) that break assumptions or tradeoffs made elsewhere in CS? Personally, I believe there are such constraints, and that's why techniques which may work for CS in other application areas don't always work so well in scientific computing---and conversely why some of the historical solutions in scientific computing look so backwards to the rest of the CS community.
For us, it's not just about helping one particular group of scientists (though, obviously our work is heavily informed by working closely with scientists at the lab), it's about bringing about a sea change in the way science is done, by improving the tools we use it do it (be those programming languages, compilers, libraries, frameworks, visualization techniques, AI/ML, or whatever).
> Do you have any specific requirements that would immediately disqualify a candidate?
We're new enough that I'm not sure we've got a crisp answer to this, but if you mail me I can ask around if there are specific points you have concerns about.
That's being rather modest. Those who know anything about the origins of HTTP and the WWW won't think it's odd at all!
He had agreed to advise me on construction of my fusion reactor prototype, but that was several years ago, and I was unable to obtain funds to proceed.
I love stuff like that. I went to nautical school with a girl whose first name was Dory and a guy whose last name was Schiff.
https://www.symmetrymagazine.org/article/november-2014/the-n...
The whole facility is really a holy temple of science (hushed tones, historical scientific relics in glass cases, etc) and a pinnacle of engineering.
youtube-dl https://www.youtube.com/watch?v=9I4GxICAcBs