If the goal is to simply purge the content of the hole, compressed air is typically sufficient. That said, the wider the hole, and the deeper it is, the harder it is to lift material on air.
To be clear though, I'd love to have one of these rigs on my old project and compare rate of progression and hole quality. Particularly when establishing the hole in sedimentary gravels and clays. I imagine casing will still be required.
One thing that I'd be concerned about is the ability to collect samples if most of the material is being vaporised or melted. Similarly, the cooking of the side of the hole on the way down could make geophysical responses much more difficult to interpret. Sonic velocity would probably increase, televised would probably be harder to interpret, harder to spot hydrothermal infill in sedimentary cover, would it affect gamma tools (probably not)
Edit: also wondering how the hole holds up around aquifers. Does the super heating cause wall instability immediately above the non geothermal aquifers as superheated steam is created? How does this affect the hole stability if we are not casing?
Edit 2: if we are not casing, how does the hole hold up around aquifer sands, loose fill, fractured or brecciated mass?
Edit 3: Also! Do we ream open the top of the hole to down past the last aquifers before the geothermal horizon? If not, how are we stopping stopping aquifers interplay and interaquifer contamination?
perhaps, but usually things like "which fossil species are present" are also utilized to figure out what's going on near the drill bit, like if you're trying to reach oil deposits right along the edge of an old riverbed.
Some shale formations in Michigan, for example, sometimes requires drilling to a 4" thick target. You don't know the exact depth because the depth of that 4" thick layer can vary by many feet from an another spot 100m north/south.
I'm aware that if you search "thickness of Antrim shale" or "thickness of Collingswood shale", Google will happily tell you that it's 20-40 feet thick, but for modern drilling techniques, the economics of the well depend on hitting a much more narrow target than that, which can be delicately guided in by analyzing fossils that come up.
No fossils in granite. Drilling shake shouldn’t require new technology, most shales are easy to drill (except cherts, where again, no fossils.
I doubt this tech would be needed for exploration but for reliable brownfield development.
Sorry, I guess. There were no comments here after a couple of hours and I literally felt bad, so I commented without being very exact in my writing. Regardless, great job, and thank you.
It is SO NICE to see people working on making fast, nice-to-use tools. It's a lovely experience to use diffshub. Thank you for creating it, and than you for the great write-up! (I made it "that far" )
Have you split your 100k loc codebases into smaller crates? If you take a look at eg gitoxide's repo, they've split it in many smaller crates. I think that might help with keeping the scope for the ai small and maybe help with keeping contracts tight and well-defined.
Yes, that absolutely helps (and yes, doing that :) ), I'm going even further and basically hard-enforcing a LOC limit per file too, which helps a lot as well.
The complexities LLMs end up putting themselves in is more about the bigger architecture/design of the program, rather than concrete lines, where things end up so tangled that every change requires 10s of changes across the repository, you know, typical "avoid the hairball" stuff you come across in larger applications...
You could probably use just an X-scanner, and instead of a CCD line sensor, use a regular 2D image sensor if you used a "1 pixel wide" slit aperture to crop the image perpendicularly to the direction that the prism disperses the light. So instead of a single pixel being dispersed, you disperse a line.
You would reduce the time required by the root of the number of pixels you want (assuming a square image).
(This is what we do in momentum-resolved electron energy loss spectroscopy. In that situation we have electromagnetic lenses that focus the electrons that have been dispersed, so we don't have as bad a chromatic aberration problem as the other response mentions).
I would love to see e.g. a butterfly image with a slider that I could drag to choose the wavelength shown!!
> I would love to see e.g. a butterfly image with a slider that I could drag to choose the wavelength shown!!
Here[1] are some 31-band hyperspectral images of butterflies. Numpy/pillow can unpack the .mat files into normal images. Then perhaps vibecode a slider, or just browse the band images?
I knew of the site having explored "First-tier physical-sciences graduate students are often deeply confused about color. Color is commonly taught, starting in K... very very poorly. So can we create K-3 interactive content centered around spectra, and give an actionable understanding of color?"
This is called chromatic aberration, for those who are intrigued.
Given that regular phone cameras have sensors that detect RGB, I wonder if one could notice improved image sharpness if one had three camera lenses (and used single-color sensors) next to one another laterally, with a color filter for R, G and B for each one respectively. So that the camera could focus perfectly for each wavelength.
This is very interesting, but like sibling comments, I'm very curious as to how you run this in practice. Do you just tell Claude/Copilot to do what you describe?
You don't need most of this. Prompts are also normally what you would say to another engineer.
* There is a lot of duplication between A & B. Refactor this.
* Look at ticket X and give me a root cause
* Add support for three new types of credentials - Basic Auth, Bearer Token and OAuth Client Creds
Claude.md has stuff like
"Here's how you run the frontend. here's how u run backend. This module support frontend. That module is batch jobs. Always start commit messages with ticket number. Always run compile at the top level. When you make code changes, always add tests" etc etc
I used it to map out storage locations and refill stations at our online grocery picking stations, then export it to read in using geopandas in order to calculate the shortest distances between all locations!
reply