Vacuums are bad at dissipating heat.
They're also very good at not stopping infrared radiation.
Fledgling? They're an ESA member and have been building rockets since there's been space programmes. Ignoring that drone part for a second the only thing they'd have to figure out is how to strap a warhead to one of their rockets, clear a launch site, do some maths, and press the button.
Not really, no, the texture is never grainy. Micrograins, kinda, but never big lumps. Closest equivalent is Skyr. Consistency between cream cheese and yoghurt, taste more like cottage cheese.
About the only AI company currently alive that I'm sure will survive is CivitAI. Huggingface probably, too. Both are, in the end, in the datacenter business. Huggingface has exposure to VC BS in their client base, they might be in trouble if a significant number suddenly go belly-up but if they have any sense they'll simply not overextend. And, well, they, too, can switch to cat pictures.
About 1000V per millimetre air gap, give or take.
Jet fuel indeed doesn't burn hot enough to melt steel. Forging temperature, OTOH, no issue.
Yep that's what nvidia marketing seems to be calling their denoiser nowadays. Gods spare us marketing departments.
Tensor cores have nothing to do with raytracing. They're cut-down GPU cores specialising in tensor operations (hence the name) and nothing else. Raytracing is accelerated by RT cores, doing BVH traversal operations and ray intersections, the tensor cores are in there to run a denoiser to turn the noisy mess that real-time RT produces into something that's, well, not messy. Upscaling, essentially, the only difference between denoising and upscaling is that in upscaling the noise is all square.
And judging by how AMD has done this stuff before nope they won't do separate cores, but make sure that the ordinary cores can do all that stuff well.
The trick to nixos, in this instance, is to use a python venv. Python dependencies are fickle and nasty in the first place, triply so when talking about fast-churning AI code, I tried specifying everything with nix, I succeeded, and then you have random comfyui plugins assuming they can get a writeable location by constructing a path from comfyui's main.py. It's not worth it: Let python be the only dependency you feed in, let pip and general python jank do the rest.
5500 here. I can't use any recent rocm version because the GFX override I use is for a card that apparently has a couple more instructions and the newer kernels instantly crash with an illegal operation exception.
I found a build someone made buried in a docker image and it indeed does work, without override, for the 5500 but it's using all generic code for the kernels and is like 4x slower than the ancient version.
What's ultimately the worst thing about this isn't that AMD isn't supporting all cards for rocm -- it's that the support is all or nothing. There's no "we won't be spending time on this but it passes automated tests so ship it" kind of thing. "oh the new kernels broke that old card tough luck you don't get new kernels".
So in the meantime I'm living with the occasional (every couple of days?) freeze when using rocm because I can't reasonably upgrade. Not just the driver crashes, the kernel tries to restart it, the whole card needs a reset before doing anything but display a vga console.
The biggest mistake was to not have full female-only battalions in the Afghan army.
Even more voter movement charts.
Bonus: "Do you think Germany's economic situation is good or bad?"
not even asking about personal economic conditions, just the overall state there's a massive fucking difference in perception.
Seems so, yes, really shouldn't surprise that the basic idea is known in the UK. Certainly not something you can get for breakfast over there, though, had to survive on nothing but full English because the purpose of their croissants is to spite the French and don't get me started on weetabix. Actually, coming to think of it quark is probably the only thing it'd actually work in.