2,178 karma · joined December 27, 2014
I'm not sure how this test would have proven anything, especially with such a small sample size. As another poster mentioned, this very much sounds like a test for sensory motor latency, which is absolutely a nontrivial thing for this sort of test.
If the test you described was done against trained shooters, I'd imagine the conclusion would likely be the opposite.
Hmm.. couldn't this be just a result of the dogs not having marked the territory where the invisible fence is? As in, it's just territory essentially open for the taking?
At least near me, there are "ketamine centers" that already to ketamine clinics - $500 per session, and insurance doesn't cover it. Ends up being around $3000. I haven't done it, so I can't comment on its effectiveness.
It's pretty lame that the cost difference is so large. I guess the barrier is a psychiatrist's willingness to prescribe. Maybe all of this research will open up psychiatrists to prescribe take-home ketamine more readily?
You're forgetting that bash really just calls other code. So you can combine two language's stdin/out functionality (eg, Python or Node) to pair code together. Sure, it won't be fast, but it can do quick wonders as an ad hoc data pipeline.
For anyone curious, here are my research notes: https://docs.google.com/document/d/1iu_evesAD8hiSjAsZ5l7h6zr...
About a year ago, I went through TSA and asked to opt out of the body scans in place of a pat down.
Another agent on the side watched the whole thing and made kissing faces my way the whole time while making gay jokes.
It was extremely belittling. Fuck TSA.
When I worked in adtech, I had a flip phone up until the point that my boss made me get a smartphone so that I could get hipchat. It's believable to me, because I was only inches away from having a burner phone myself.
Just because you haven't seen it, doesn't mean it's not happening.
That said, my "creative projects" are a pretty involved - two of them include FOIA lawsuits.
1. Had to build a Minecraft computer and figure out its interface. The computer came with git and curl commands, so that's how I downloaded files.
2. Every block had to be pulled apart and every pixel had to be mapped to it's voxelspace dimensions.
3. Some blocks had extra logic which caused random transparent pixels to show up, so I had to find and exclude those from samples (flowers were the biggest contributor). This was a bulk of the work, because there was no simple way to find which blocks had extra logic. I even pulled out jad to find any sort of useful pattern, but there really wasn't any.
4. Had to do some k-map stuffs to find the closest color to each pixel from all images.
5. Create a file for each block, which all had to include the original block's color for that specified dimension.
6. Import each file one by one because the computer had limited diskspace.
7. Place each block manually.
It ended up working surprisingly well and could be scaled to any size. Problem was, even looking at a printed block used a LOT of resources at both server and client side. So I scrapped the project.
Fun stuff, especially with that being the first sort of image processing work I've ever done.