Hacker Newsnew | past | comments | ask | show | jobs | submit | bocklund's commentslogin

Is there an additional arXiv paper? The abstract referenced at the bottom refers to a completely different paper.


We’re still waiting for arXiv, but the pdf is at the top.


Actually, LLNL (the site of El Capitan) has a process for requesting Dedicated Application Time (a DAT) where you use up to a whole machine, usually over a weekend. They occur fairly regularly. Mostly it's lots of individual users and jobs, like you said though.


> where you use up to a whole machine

i mean rick stevens et al can grab all of polaris too but even so - it's just a bunch of nodes and you're responsible for distributing your work across those nodes efficiently. there's no sense in which it's a "single computer" in any way, shape or form.


The same way that you're responsible for distributing your single threaded code between cores on your desktop.


No. Threads run typically in the same address space. HPC processes on different nodes typically do not.


Define address space.

Cache is not shared between cores.

HPCs just have more levels of cache.

Lest you ignore the fact that infiniband is pretty much on par with top of the line ddr speeds for the matching generation.


>Lest you ignore the fact that infiniband is pretty much on par with top of the line ddr speeds for the matching generation.

You can't go faster than the speed of light (yet) and traveling a few micrometers will always be much faster than traversing a room (plus routing and switching).

Many HPC tasks nowadays are memory-bound rather than CPU-bound, memory-latency-and-throughput-bound to be more precise. An actual supercomputer would be something like the Cerebras chip, a lot of the performance increase you get is due to having everything on-chip at a given time.


There are four sentences in your comment.

None of them logically relate to another.

One is a question.

And the rest are wrong.


Really? How about: "This pointer is valid, has the same numeric value (address) and points to the same data in all threads". The point is not the latency nor bandwidth. The point is the programming/memory model. Infiniband maybe makes multiprocessing across nodes as fast as multiprocessing on a single node. But it's not multithreading.


>Cache is not shared between cores.

I feel sorry for you if you believe this. It's not true physically nor is it true on the level of the cache coherence protocol nor is it true from the perspective of the operating system.


Tell me you've never run a distributed workload without telling me. You realize if what you were saying were true, HPC would be trivial. In fact it takes a whole lot of PhDs to manage the added complexity because it's not just a "single computer".


If you think parallelizing single threaded code is trivial ... well there's nothing else to say really.


Is there like a training program available for learning how to be this obstinate? I would love to attend so that I can win fights with my wife.


Maybe llm_trw is your wife?


Steels can undergo a transition to becoming brittle when they get cold (called a “ductile-to-brittle” transition). It’s important to know what the properties would be like in this regime and -70C is enough to get there (even 0C can be enough, depending on the alloy).

The reason this person may have thought the -70C test eqs stupid is because a sub will never be working in conditions much colder than the freezing temperature of water (which is not strongly pressure dependent, btw), since the water would want to freeze - not good for the boat.


Networking and connections get university students good jobs. Aptitude and drive are what makes them good at those jobs.

I think the post you responded to was talking about the latter type of “success” at universities, but both are valid metrics of success.


I believe you are talking about excellence which is correlated to, but not necessarily concommitant with success.


It's not "initial conditions" as in time=0. Thermodynamic state variables are path independent, so "initial conditions" in this context means the conditions of the reference point in the process from the point you start measuring.


Several new HPCs are already using AMD [1] and that trend will probably continue if AMD continues to put out competitive products.

[1] See the Top 500 list that, by my count, has 26 of the top 100 HPC systems using AMD EPYC CPUs as of their June 2021 listing https://www.top500.org/lists/top500/list/2021/06/


Seaborn is based on matplotlib and has basically the same semantics of matplotlib with better styling defaults and a wider API for different plots.

For a ggplot grammar-of-graphics style library in Python, I really like Altair: https://altair-viz.github.io/


The semantics differ and the API is actually more restricted (and friendly), not wider, but yes, I agree it is not grammar of graphics. However, as much as I love the grammar of graphics, it is important to point out there are other good ways to make stat plots besides it. Seaborne, bokeh, statsplots.jl, algebraofgraphics.jl, and others.


At least for the AR-15 platform (the weapons pictured in the article), only the part that bears the serial number is regulated. Everything else can be bought freely and legally. For the AR-15, that part is the lower receiver.


A project I work on has a `RELEASING.rst` in the repo, which I include in the docs [1]. It contains a checklist of steps with the code. The actual deployment is automated with a GitHub Action to deploy to PyPI.

The checklist makes sure I hit all the things I need to do. There's still places to screw up the manual steps, replacing the right versions, etc. It's not perfect and there's a bunch of things I want to improve still. I try to write it clearly enough so that someone who's never released a project ever just needs to follow the steps.

[1] https://espei.org/en/latest/releasing.html


The abstract of that paper includes:

> Due to the inhibition of van der Waals adhesion at the liquid interface, the electrode was remarkably resistant to deactivation via coking caused by solid carbonaceous species.

MOXIE is solid state technology and having solid C reaction products would very likely deactivate the cell by clogging up the triple phase boundaries where the reactions occur.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: