131–140 of 175 posts
Earlier quoted context omitted.
Is there an equivalent command for doing things like 147 days from today or days since 21 jun 2021 or 88 days after 15 Aug 2021? This is the one thing I really wish was in Spotlight (I use spotlight for unit conversion and calculations which is really handy).
To clarify, I was thinking a quick command line thing. Right now, I do it in a browser (both DuckDuckGo and Google produce the answer easily enough).
We once had a customer who would call us in a panic a couple of times a year saying our inspection equipment was experiencing unusually high false rejects and they were generating very high scrap rate. By the time we got a technician on site the next day, everything was working flawlessly and the customer couldn't reproduce the problem either. This went on for almost three years with various levels of escalation to t…
I had a similar issue in my industrial automation class. We were sorting cylinders by diameter and height as they went down the conveyor belt. PLC controlling motors, sensors, etc. My group got everything setup, built our program, and everything worked fine. Waited a few minutes for the TA to verify, but it failed. We changed a few things, it worked, but failed when he came over. Another group looked over our code, n…
I don't think it was entirely wasted time, though. You can't plan to teach that kind of lesson ("Look outside of your usual blinkered problem-solving-space"), it happens when it happens.
As this whole thread shows, most of us learn it during our careers at some point but you were lucky enough to learn it before you even started.
Earlier quoted context omitted.
A bit unrelated, but another fun one, "We can't send mail more than 500 miles": https://web.mit.edu/jemorris/humor/500-miles
The "magic" switch: http://www.catb.org/jargon/html/magic-story.html
Earlier quoted context omitted.
So much time and money wasted by not recording the camera. Could've simply reviewed the footage from the right timestamp and immediately discovered what was wrong. All you had to do was take a still picture every time the system makes a rejection.
Looks like a cool solution, when issue is known )
But if you have a problem only happening sometimes, then you surely want all the data you can get from all sensors recorded, so looking at the saved video ofthe error time seems a nobrainer, but maybe it was not so easy to make them recording something. We do not know the setup.
We once had a customer who would call us in a panic a couple of times a year saying our inspection equipment was experiencing unusually high false rejects and they were generating very high scrap rate. By the time we got a technician on site the next day, everything was working flawlessly and the customer couldn't reproduce the problem either. This went on for almost three years with various levels of escalation to t…
Earlier quoted context omitted.
The end of that article is a good reminder of the units command, I've been using Google for units conversion for so long that I forgot about the standalone units . It even comes standard with OSX.
Is there an equivalent command for doing things like 147 days from today or days since 21 jun 2021 or 88 days after 15 Aug 2021? This is the one thing I really wish was in Spotlight (I use spotlight for unit conversion and calculations which is really handy).
$ date -d 'today + 147 days' +%F
2022-02-23
$ echo $(( ($(date +%s) - $(date -d '2021-06-21' +%s)) / 86400 ))
100
$ date -d '2021-08-15 + 88 days' +%F
2021-11-11Earlier quoted context omitted.
I knew a guy who was a computer tech early in his career. One of his rounds was on a military base, and they had just moved their computer room up one floor. They started having problems with their tape drive, it would just randomly pop up an error while they were using it. He tried mightily to diagnose the problem but couldn't figure it out. Finally he took a break and walked to the nearest window and looked out. He…
I sent my Commodore 64 for repairs more than once only for them to find nothing wrong until we realised it was the buildup of static electricity from being stored under our big TV - it "broke" when we didn't use it for a while but watched lots of TV. It'd be "fixed" by the time it took before the repair people got around to it. The symptom was that it started "typing" automatically.
Earlier quoted context omitted.
For those who are interested, this is why you usually have two dishes/aerials, vertically displaced, so that when one has destructive interference between the direct and reflected signals, the other has constructive interference. I learned something about this when writing data compression and encryption software for radar surveillance systems, where there were multiple radars over a moderate coverage area, all sendi…
in modern point to microwave systems, unless the budget is really high, or the path is very long, it's rather unusual to have a vertical spatial diversity setup. much of the problem of losing link due to fade is accommodated by modern radios that have advanced variable modulation and FEC, which can operate anywhere between 4096QAM 5/6 and QPSK 1/2.
I'd be interested to know what you think is a very long link ... 10km? 100km? I can't say too much more about where we were.
We once had a customer who would call us in a panic a couple of times a year saying our inspection equipment was experiencing unusually high false rejects and they were generating very high scrap rate. By the time we got a technician on site the next day, everything was working flawlessly and the customer couldn't reproduce the problem either. This went on for almost three years with various levels of escalation to t…
This is something that I've also heared from hot axle box detectors for trains. Their solution: plant a tree.