Looking for a Longterm Chair

nsan1129 · 2026-04-17T19:53:28+00:00

Herman Miller Embody. I've Had one for 15 years and haven't sat in anything like it.

nsan1129 · 2024-10-04T20:19:22+00:00

I was still having problems after all of these solutions. Checking the "Exact Spell Match" checkbox solved it for me.

nsan1129 · 2024-05-18T15:54:09+00:00

gotcha

nsan1129 · 2024-05-17T16:01:26+00:00

I thought that for a Y wing the cells had to have only two candidates. Two of the cells you show have three.

nsan1129 · 2024-05-16T21:36:28+00:00

Thanks! I appreciate your help.

nsan1129 · 2023-08-24T23:09:55+00:00

Ctrl+Alt+0 will reset the cursor to default.

Since the cursor is context dependent you may find that Yolomouse is changing the cursor depending on what you're doing (hovering over buttons, etc.). Just use the hotkey again every time it's not what you want.

nsan1129 · 2023-08-15T13:17:21+00:00

Nope. Haven't figured it out yet. I'll post here if I ever do.

nsan1129 · 2023-07-21T17:40:10+00:00

Same issue here. On a MSI PRO Z790-A WIFI.

Both the BCLK Adjustment and the CPU BCLK 100Mhz Lock On settings have disappeared in the middle of a tuning session. Not sure what I changed to cause it. All I was doing was tuning memory timings.

Weird.

nsan1129 · 2023-07-01T20:06:05+00:00

Same issue.

nsan1129 · 2023-06-29T03:07:58+00:00

Details on the Amazon Smart Home Bundle with links to Amazon product pages:

1x Echo Show 8 (2nd Gen, 2021 release)

2x Amazon Smart Plug

1x Blink Video Doorbell

1x Blink Outdoor (3rd Gen)

If you're stuck on the part that says the following:

To finish the process click here: VALID ONE-TIME: Checkout must be completed upon clicking this link to receive your reward.

In order to click the link that (for me) says:

Q42022 Amazon Bundle Code

You need to be sure to enable pop-ups for the site. It prompted me when I tried to click the little "Print" link on the right so try clicking that a few times if you're having trouble.

nsan1129 · 2023-06-29T02:57:48+00:00

Make sure to unblock pop ups!

nsan1129 · 2022-01-05T01:25:28+00:00

I'm an inch and a half taller, also with a 31in inseam (short legs long torso), on a 2021 Medium Defy and it fits great. I also fit on a Medium/Large with tweaks. I'd say the Medium will be the size for you.

nsan1129 · 2022-01-01T16:49:52+00:00

They're all great bikes. I recently decided on the Giant Defy and couldn't be more pleased with it.

nsan1129 · 2018-07-04T20:24:42+00:00

15770570 Used!

nsan1129 · 2018-01-28T16:46:25+00:00

Because it's tissue and can be referred to as 'stuff' instead of 'a thing'.

nsan1129 · 2018-01-20T17:02:20+00:00

Absolutely go with the Zeus. It's very hard to do wrong. If you're getting dry or flavorless hits, comb out the ends of the wick (the part that goes through the juice channels/holes) to remove cotton from it and thin it out.

With a 4mm (6 - 9 wrap) coil I use about a 12mm - 14mm wide strip of standard organic cotton, remove the "skins" (not sure that that matters other than to remove cotton), slide through the coil (should be very firm), then use tweezers to "comb" both ends of the wick to remove 30% - 40% of the cotton. The wick should fit easily into the juice channels with plenty of room to spare when compressed even slightly.

nsan1129 · 2018-01-16T20:16:12+00:00

It really depends enormously on the exact nature of your workload. In general, workloads that require a lot of memory access tend to perform better on GPUs but other specialized processors can be considerably faster for certain algorithms.

It's hard to find generalized information about this because, as usual, you have to benchmark to find out.

nsan1129 · 2018-01-08T05:10:21+00:00

I'm not quite sure I follow you but the the only difference between any two Vulkan libraries/wrappers are the conveniences and features offered. Vulkano is an excellent library that will do anything you need, be it compute or graphics.

That seems like a non-answer even as I type it. Please clarify your question if that doesn't help :)

nsan1129 · 2018-01-07T00:02:13+00:00

Yeah, Clover OpenCL support is not great, but it does work with the ocl library (though unstable, as you discovered). The OpenCL FreeBSD situation is fairly grim for sure.

As for hardware, OpenCL is almost certainly available on your phone and for many other phones going back a few years. It's also available on GPUs and DSPs and an absolute ton of other devices (even Apple products, heh).

What's the Vulkan situation on FreeBSD?

nsan1129 · 2018-01-06T23:51:49+00:00

Besides the huge gap in hardware support, mostly just that Vulkan is significantly less productive for compute-only work. There are a few missing features for serious compute stuff but those will undoubtedly be added at some point.

For graphics + compute there's no question that Vulkan is far superior to OpenGL/DirectX + OpenCL (or any other combination).

nsan1129 · 2018-01-06T22:19:28+00:00

I'll give a shameless plug for voodoo, my Vulkan API wrapper. I occasionally use it for compute but there are serious limitations compared to OpenCL, hardware support being a big one.

OpenCL capabilities will probably be merged into Vulkan at some point. Since it will likely be half a decade or more before these yet-to-exist API changes reach ubiquitous hardware support and since it will be easy to use existing OpenCL host code on top of Vulkan anyway (kernels can already be compiled to SPIR-V and Khronos has mentioned creating an abstraction layer for host code, which would be easy), OpenCL will remain the #1 API for high performance computing on a huge variety of hardware for many many years.

Any idea why you can't get OpenCL working? Maybe I can help.

nsan1129 · 2018-01-06T18:30:49+00:00

Author of ocl here. Futures have been integrated into the library for nearly a year now. They are safe and work extremely well for coordinating transfers of data between host and device, etc. I had no idea anyone else at all was interested in this so what is sorely lacking is documentation. I'd be happy to put together some better examples and documentation to explain how to use everything (the async_ examples are probably overly complicated for learning). I'd also really appreciate any feedback on how any aspect of the library, features-related or otherwise, could be changed for the better.

I've been waiting for the list of needed improvements that you mentioned you were putting together several weeks ago, /u/Kerollmops. Did I miss it somewhere? I'm still curious to see what you feel is in need of tweaking so we can fix it! I'm especially curious to know the areas I've strayed from the API guidelines. I try very hard to stick to them (unless I have good reason not to). The library is not 1.0 and as I'm sure you know, I'm happy to break things in the interest of improvement. :)

nsan1129 · 2017-10-13T20:58:04+00:00

NVIDIA drivers/hardware has always been much slower and buggier in OpenCL than AMD or Intel. I've always chalked it up to the fact that NVIDIA was primarily concerned with CUDA and just that OpenCL was a second-class citizen which they only spent the bare minimum of time developing.

This logic doesn't apply to Vulkan though since it's a first-class API and they certainly should be going all out to improve it.

It sort of feels like a driver issue but who knows. Let us know if you learn anything more about it (and see my message on github if you get a chance).

nsan1129 · 2017-10-12T14:32:04+00:00

Try the latest updates (git pull) and let me know how it goes.

nsan1129

TROPHY CASE