2. boot from immutable live system

3. sudo mkdir -p /mnt/sus/infected

4. sudo ddrescue -d -f /dev/sda /mnt/sus/sus.img /mnt/sus/sus.log

5. sudo kpartx -l /mnt/sus/sus.img

6. sudo kpartx -av /mnt/sus/sus.img

7. sudo mount -o loop /dev/mapper/loop0p2 /mnt/sus/infected

8. sudo debsums -sac -r /mnt/sus/infected

9. sudo umount /dev/mapper/loop0p2

10. sudo kpartx -d /mnt/sus/sus.img

11. Submit infected binaries in zip.vir file for forensic de-compilation, and ascertain how payload was dropped.

Every once in a awhile these things happen. Better to redeploy a new clean OS container on the host, and dump the traffic with a remote live packet capture.

Repeat as necessary. =3

Most human daily life runs on habitual scripted behavior, and that is even true within online parasocial interactions. It is why people often continue to shop in the middle of a violent robbery, and why LLM predictive text sounds rational when we project social norms on plagiarized conversational structures gleaned from other users.

Neuromorphic computing may bring about viable AI in the future, but our current LLM trajectory would require >63% of our galaxy energy output to reach a single human-level error rate.

LLM are fairly good at some tasks like context search, but people will need to recognize the Gartner Hype Cycle "Peak of Inflated Expectations" stage eventually. =3

https://en.wikipedia.org/wiki/Gartner_hype_cycle

https://www.newegg.com/p/pl?N=100017489%204016%20601497625%2...

Dram prices and Flash prices are inflated right now, but the pi were never focused on Desktop users. As a platform it no longer makes sense for many use cases. =3

https://github.com/openMVG/openMVG/blob/develop/COPYRIGHT.md

https://github.com/cdcseacave/openMVS/blob/master/COPYRIGHT....

Personally, I recommend COLMAP + CloudCompare + MeshLab, but the Mozilla Public License 2.0 should address IP license issues if the author is also the rights holder. Keep in mind all work done by University Students and Staff is often property of the institution unless otherwise stated. It is a delicate subject.

Best of luck =3

One must be extremely careful when signing off on something as a company representative.

One internal IP lawyer wanted a legal journal subscription, and left the tap running after they left the firm... that one cost $8k if I recall, as the journal sold the delinquent account to a collection agency. Took 3 weeks to verify it wasn't a scam, as the companies usually go quiet without the account number etc.

Some people are wired that way, and run their company on legal cons. Indeed, one doesn't want to have these people around your firm. =3

Our problem domains must obviously differ. Good luck =3

However, until each code area turns 17/21 no one knows for sure. It just looks normal at first, and $12k cheaper than MatLab server host licenses. =3

I discovered that while porting it to a Pi ARM platform years ago (yes it was slow... lol.) Forgot when the IP becomes public domain, but you might want to check that out. If I recall it was unrelated to the COLMAP project design. =3

A "Report" is just a document feature projection.

People may initially think this is in err, then think again... =3

Indeed, if your library dependency constellation works, some will static link to stabilize/freeze their project for more than a few months.

It wasn't that v3 was particularly good, but rather v4 was a mess. I predict v5 inherited that mess, and improved it... lol =3

To enable Intel TBB, CUDA, and CPU specific compiler optimizations... one will almost certainly need to re-build the library, and customize your application build.

Some tasks degrade in performance on a GPU, and others are 740 times faster... ymmv. =3

However, it has a few issues:

1. Patented algorithms that are effectively impossible to license in a commercial setting.

2. Permuted API that change how identically named functions behave over versions.

3. Hardware CUDA version coupling deprecating support every major release.

4. Inconsistent and contradictory documentation in the constant subtle permutations. Downstream projects tend to version lock the lib for really practical reasons.

5. A shift away from core C libraries like ImageMagick & V4l, and into C++ abstractions with legacy Swig wrapper libraries in Java or Python.

6. Perpetual-Beta culture means the library will unlikely ever really fully stabilize.

It is a fun library, until people actually try to deploy something serious. As users will often simply suggest using an old version release if there is a bug.

Everything from Build flags to the API documentation has never fully stabilized. ymmv =3

Sometimes folks have help, sometimes its all debt, and sometimes it pays off eventually.

However, living beyond ones means is almost always unwise. =3

Others spend their lives making decisions out of impulsive narcissism. Unless you are a trust-fund kid, life can have very real consequences if things go sideways.

Most will learn the hard way... only lawyers and politicians get paid for excuses in life. =3

While not a personal preference, most acquire revenue properties as they build equity over time. Assets secure lower loan rates, qualify mortgage fixed-payment schedules on investments, and require good management-companies to handle leases.

Generally, mitigating tax exposures by investing in small businesses is still popular. Sometimes they work, and sometimes they don't... but it is money people will lose anyway if they do nothing. Specifically, my first business investment was a few vending machine locations as a teenager, after a summer dropping hardwood floors.

Everyone starts somewhere, but blindly cloning what others do is usually unwise. ymmv =3