Summary: dry contact with nearly any laboratory glove will lead to sample contamination and over estimation of microplastics.
They found one type of clean room gloves that contaminate less.
Is there any indication on how bad this really is?
305 karma · joined December 10, 2020
Is there any indication on how bad this really is?
Use cases for this? Maybe to validate you own statistics computation?
The Kodim dataset is pretty useless nowadays. If you build an algorithm that runs on this dataset (or the Lena image) it will be pretty bad on other images. Think of data dependent things like compression, segmentation, inpainting or such. The specific characteristics of these "small" images are unlike a cellphone Jpeg or DSLR raw.
Once you introduce a HDL and start optimizing, I would expect more than half of the transistors to be redundant. But you would end up with a circuit that you will not understand any more.. But that could give an important lesson in chip design and HDL compilers.
Use case: I was out, picking wild lingonberries in the forest with a group of ~10, some kids. At a "secret" location, with everyone wandering off in a direction they see more of them. Shouting did not help much.
Electronic warfare is not about listening, but just seeing the location of the emitter. If you had someone with a different thermal camera/ camera with SWIR, you might see that something is just not right.
It is a clever mechanism to separate a wide range of parts. Like a vi Rating feeder, but without adjusting the device for different object sizes. It is a rotating tube, slightly angled.
How would that help? Say - you have just one tube to seperate parts. You drop your first box of washers and route them into a sequential storage. They you do the next box with bolts on the same device and drop them into another sequential storage.
They dispensing remainds still manual as mitxela showed.
I don't know any better, but the screw counting mechanism seems awkward. Imagine the set has 10 components..
I'm surprised there is no standard solution to this - like a tape and reel solution? A counting and dispensing gun that works for different sizes? But how much more would anyone pay for M3 bolts on a tape?
Helmke had a tube feeding his dispensers in one of the videos, with bolts lengthwise. That tube idea could be used for a manual dispenser - imagine a drink dispenser, but giving 3 bolts. Maybe easier to store away, but just as awkward to load.
We are well beyond where a dedicated individual can try an idea, show that it is better and expect that others can pick it up (e.g. in standardization). It is not sufficient to run a few dozen images and judge by yourself, you are expected to demonstrate the benefit integrated into the latest reference encoders and need a sponsor to join standardization efforts.
For educational purpose? Sure - do whatever you want - but any discussion "is it novel" or "is it useful for others" is moot, unfortunately.
It is more like an OpenClaw rusty clone
Do you have the GPU running all day at 200W to scan for wake words? Or is that running on the machine you are working on anyway?
Is this running from a headset microphone (while sitting at the desk?) or more like a USB speakerphone? Is there an Alexa jailbreak / alternative firmware as a frontend and run this on a GPU hidden away?
- processing: while there is no post processing, it needs scene depth information which requires pre computation, segmentation and depth estimation. Not a one-shot technique and quality depends on computational depth estimates being good
- no free lunch. The optical setup needs to trade in some light for this cool effect to work. Apart from the limitations of the prototype, how much loss is expected in theory? How does this compare to a regular camera setup with lower aperture? F/36 seems excessive for comparison.
- resolution - what resolutions have been achieved? (maybe not the 12 MPixels of the sensor? For practical or theoretical reasons? ) What depth range can the prototype capture? "photo of Paris Arc de triumphe displayed on a screen". This is suspiciously omitted
- how does the bokeh look like when out of focus? At the edge of an object? The introduction of weird or unnatural artifacts would seriously limit the acceptance
Don't get me wrong - nice technique! But to my liking the paper is omitting fundamental properties
While this methods has no post processing, it requires a pre processing step to pre-calture the scene, segment it, estimate depth an compute the depth map.
You try to compute something that supercomputer can't - by not computing it? Instead the formula is stored in a data structure. But once you need to access all the values you still have something that does not fit the memory and needs to be computed.
I can't judge on the Java side, but suggest to pick a better example on how this can be useful.
Rough estimate - with an excellent 0.5" angular resolution and 35km triangle this could work.
Did you buy all these colors and paint and scan them? Did you analyze the shopping images of the bottles and classify them into hex colors? Or maybe just group by the color names given in the storefront listing?
Vastly different efforts, different "accuracy", but still, each methods has its use. But knowing what to expect would be nice.
I think this software-only post is meant for IP cameras / surveillance cameras. Internet is the oposite of closed circuit.
Maybe CCTV is used as a synonym for surveillance now in some regions of the world, but certainly confusing for a non-native speaker.
Mobley plotted two graphs of the solar irradiation and a black body fit. The only difference is supposed to be the x axis with a plot over frequency or wavelength. This is a non-linear mapping and a different shape is expected. But the result is that the peak irradiation level is at either 501nm or 882nm (when converted back). That can't be right. The labeling of the x axis does not change the maximum.
What he meant to do was to plot either the solar irradiation in W m^-2 nm^-1 or as the number of photons. With lower energy photons (towards the red) the same irradiation level will consist of more photons. This shifts the maximum number of photons towards higher wavelengths. 880nm sounds plausible.
A few questions remain unanswered though: What can the current plant already do? It sounds like a multi-day sequential process per batch. How many batteries could that give?
The mixed metal product also contains nickel-manganese-cobalt. But certainly with a lot of other stuff and not in the exact ratio you would put in a battery. Even if we were to continoue with NMC batteries (LFPs are more common today). It looks like a first concentration step to get the interesting 10% of the rock. What separation process still remains? I expect a concentrate still to be much more useful than bare rock.
What are the overall economics? I understand that you won't need the separate mining as Olivine is considered waste and has already been piled up. But is that an economic benefit? (cheaper?) Environmental? Or time to market? (you don't need another mining permission for more capacity).
Is it just a more green but more expensive extraction from unused Olivine? Or will this replace all other dirty extractions mining soon? (too good to be true)
However, the examples indicate that if you have a loop that is executed over and over, the setup cost for configuring the fabric could be worth doing. Like a continuous audio stream in a wakeup-word detection, a hearing aid, or continous signals from an EEG.
Instead of running a general purpose cpu at 1MHz the fabric would be used to unroll the loop, you will use (up to) 100 building blocks for all individual operations. Instead of one instruction after another, you have a pipeline that can execute one operation in each cycle in each building block. The compute thus only needs to run at 1/100 clock, e. g. the 10kHz sampling rate of the incoming data. Each tick of the clock moves data through the pipeline, one step at a time.
I have no insights but can imagine how marketing thinks: "let's build a 10x10 grid of building blocks, if they are all used, the clock can be 1/100... Boom - claim up to 100x more efficient!" I hope their savings estimate is more elaborate though...
If you didn't catch the reference, this is referring to the recent vibe coding incident where the production database got deleted by the AI assistant. See https://news.ycombinator.com/item?id=44625119
There is no silver bullet - you can't just build a 10bn$ nuclear bomb programm and call it a day. All the other means are still needed to transition away from fossil fuel.
The earlier we start the better.
There is open distributed monitoring for all kinds of signals, like seismometer networks, weather, ads-b... Is there anything like this for the power network? Like a reference design or an esp32-shield?
How would it look like if we were serious?
I would make it three phase, with direct coupling to also see the exact voltage changing over the day. Sometimes we have issues with local voltage rising too high and PV inverters shutting off. I'd like to see and log this. An audio ADC should be good, but needs three channels.
For distributed sensing and logging, you would need a reasonable accurate time synchronization. Raw ntp over internet might not be good enough, at least not for localizing fault propagation issues over the whole continent. Better stick a 5€ GPS module on there.
Anybody seriously working on this..?
Let's say you build single photon detectors and ultra precise time stamping. Would that get us near? Today, maybe we don't have femtosecond time stamping and detectors yet. But that is something I can imagine being built! Timing reference distribution within fs over 100s of km? Up to now, nobody needed that I guess.
The Cob array of leds is the problematic choice, while on paper you get a lot of light, you don't get a point source.
If you look at the large theater projectors, I remember laser sources (but no speckle, is this pumped phosphor?) or expensive xenon bulbs. At least 10years ago...
I remember a solution (car headlights?) of decoupling the phosphor (for converting uv to while light) from the UV Led. So you have multiple diodes pumping a small piece of phosphor for a nice bright point source. Not sure how this can be replicated open source.
Another approach (studio led lights) wasomething with glass mixing rods? You insert the light of multiple leds into a glass rod, and a uniform beam emerges. But I guess this was more to improve CRI, rather than to increase brightness/point source.
It will be hard to overcome a lot of gaps in education
- where is a phone (he seems to have signs "phone inside"), what kind of device am I even looking for, visually?
- is this operational? did someone forget this on the wall?
- how do you operate the dial?
- do you even remember a phone number that is useful now? When the smartphone suddenly stops working?
Sadly, I would probably score 2/4 and not rely on it.
Going to this kind of resolution, the only practical use case is with cameras. You record some frames and later want to check the exact timestamp. This is even useful for a single image, not just high speed cameras.
But taking images is not just a single point in time. There is an exposure time and it is hard to measure absolute timings on start and end of exposure. With a segment clock display, the numbers will blur. For this a row of LEDs is fine - just light up one at a time. In the image you will see multiple leds on at once, giving you verification of start and stop.
But again, I needed just one clock and built it already.
The description confused me, as it describes the use of a real Lidar measurements to detect "change" in the terrain. But certainly, it can't be a temporal change before and after... to detect medieval settings in the data. Is the area still changing differentlybetween scans over multi year's? I don't think so.
I think this is visualization code highlighting natural VS. human train structures, at known locations of old settlements? Showing different approaches on how to visualize the man-made heights in the terrain.
But still, I'm lost how this could help finding new ones..