61·
10 months agoEvery projection between a sphere, or even sphere section to a plane is going to have distortion. You can make tradeoffs between different distortion types, but you wont eliminate them.
- 0 Posts
- 13 Comments
Joined 3 years ago
Cake day: September 10th, 2023
You are not logged in. If you use a Fediverse account that is able to follow users, you can follow this user.
38·10 months agoThey contained the impact. Root causing or “understanding” should come after impact mitigation. If needed find a safe way to reproduce the bug without customer impact.
We reverted the refactoring, deployed, un-banned the CEO, and set about analysis.
I’m not disagreeing. The report isn’t clear. This is written by people asking Congress for a budget cut.
NSF programs indirectly impact millions of people, reaching PreK-12 students and teachers, the general public, and researchers
The actual impact to the pipeline may be far larger.
Graduate students provide enormous value for their cost in funding. I’d like to better understand how k-12 students contribute here. Those students make up 88.7k of the reduction. How much do these students contribute and at what cost?
I’m in no way against inspiring the next generation. My question is aimed at correctly interpreting this table. The NSF is a worthwhile expense, but let’s understand the data we have.
Relevant XKCD
The source is worth a quick read. It’s very tongue in cheek.
It’s one backed by a lot of data. One example is from the Android project.
The percent of vulnerabilities caused by memory safety issues continues to correlate closely with the development language that’s used for new code. Memory safety issues, which accounted for 76% of Android vulnerabilities in 2019, and are currently 24% in 2024, well below the 70% industry norm, and continuing to drop.
https://security.googleblog.com/2024/09/eliminating-memory-safety-vulnerabilities-Android.html
There’s an argument that critical infrastructure software vendors are already meeting standards for basic, non-memory related items. Yes, there are other categories, but memory safety is one that’s harder to verify. Moving to memory safe languages is an ensure a category of correctness. This excludes usage of unsafe escape hatches.
422·2 years ago#DonaldTrumpIsAHumanToilet
3·2 years agoSorry for not having a direct answer for your question.
First, are these videos using Dolby Vision? If so try a google search for “Dolby Vision green tint”.
Second, if this really is a corruption issue, are you sure you really want to write something custom to fix this? What else is wrong in those files that you haven’t noticed yet? It seems unlikely that they would all corrupt consistently. Did something transform them since they were last in a known good state? Do you have other means to revert that transformation?
Finally, if you do want to continue down your current path there’s a light discussion on the topic in this stack overflow thread. You’re going to need to contend with how videos are compressed, i.e. not every frame is actually stored. You’re likely going to loose some quality or bloat the file size through applying a correction process. If you find the right tools and want to minimize loss and bloat, you may need to use different solutions for different codecs.
We have a mathematical model, Navier-Stokes (NS), that seems to describe motion of fluids well. In practice NS and related approximation models with simpler numerical solutions can be used to derive useful results. In that sense we can simulate turbulence for some sets of conditions and get useful approximations out. In general it’s still an open problem if NS has, given an initial velocity field, a solution that is globally defined and smooth. Practically this means we don’t know one way or the other if NS has initial conditions under which the velocity or pressure fields of the solution tend to infinity in finite time. This is the unsolved Navier-Stokes problem.
https://en.m.wikipedia.org/wiki/Navier–Stokes_existence_and_smoothness
7·3 years agoAccording to the Form 4 filed with this sale, the trade was planned at least as of May 19 using a 10b5-1.
The sales reported on this Form 4 were effected pursuant to a Rule 10b5-1 trading plan adopted by the Reporting Person on May 19, 2023.
I’m going to whoosh the joke for a moment.
Avoid allocating memory in sig segv handlers. I worked at a company once that had written their own handlers that tried to print a stack trace. I was fortunate enough to find a machine in a test environment that segfaulted while allocating memory. The handler then caused a deadlock in a call to malloc (through new). I ended up rewriting the handler to fix two sources of memory allocation. First I preallocate enough space to do string manipulations in the handler. Second I made eager calls to a few libc functions used in the handler to avoid memory allocation from lazy binding from ld.so.