wjs018

I have a PhD in physics, primarily working on fluids and now I work in industry on fluid dynamics. Having just read the abstract, I can already tell that this paper is one of those that borders philosophical about the author's view of their field. Nothing wrong with that though as we physicists tend to wax poetic from time to time.

The question about when we can consider turbulence solved is an interesting one. I still work in the field and for most useful applications of fluid dynamics, I would consider it a solved problem. Not to say that the NS equation is solved analytically, but rather that the field has built up a toolbox of phenomenological models and CFD systems that are more than good enough for the range of scales that we typically work with. The bigger problem for CFD in this space is optimization, an issue where GPUs have proven to be invaluable. Only in the past couple years have the major CFD software packages started supporting GPU computation, speeding things up 2-10x depending on the specifics.

I think that turbulence is an issue really at the extremes of scales at this point (very tiny, very large, small dt, hypersonic, etc.). Also, I think that it would be difficult in a system with complex forces acting on your fluid, like in a plasma where E&M forces are so significant. So, good luck all you folks working on fusion reactors!

Fair enough. App development is far beyond my programming capability and I am happy to defer to expertise in this regard.

@freamon@preferred.social is the one primarily working on the api, pinging them to bring this to their attention. There is also a matrix chat for piefed dev where I have seen api discussions happen.

My understanding as a non-dev is that the api is ~~95+%~~ mostly the same as lemmy (intentionally so). The rest is mostly there, but with some kinks still to work out. Right now, preferred.social is the only piefed instance running a build with the api turned on for testing.

Karma on piefed isn't visible to the users, only to the instance admin. So, I don't really see the incentive to farm it the same way as on reddit. What I can see on my (and others) account is my "Attitude" or the ratio of upvotes to downvotes:

I'm not a biologist, but if I understand your question correctly, you are basically looking for land-based invertebrates that also lack a hardened exoskeleton (like insects). This would basically consist of small, soft animals like snails, slugs, leeches, tardigrades, and tons of different types of worms.

The reason that you don't see large examples of this in land-dwelling creatures is that skeletons or exoskeletons become way more necessary without a medium like the water in the ocean to help support a body. The rigid structure provides an attachment point for musculature to create the mechanical levers we use to manipulate our limbs.

Not sure where this falls on lemmy's roadmap or if there is a github issue for it, but you can turn off notifications in piefed per post or comment. You can also enable notifications for posts/comments that aren't your own if there is a thread you want to keep tabs on.

Xiaolan is such a sweet cinnamon roll. The spin-off from her POV is likely to be a lot less dramatic than the main story and more moe antics.

The theory that the lead maintainer had (he is an actual software developer, I just dabble), is that it might be a type of reinforcement learning:

• Get your LLM to create what it thinks are valid bug reports/issues
• Monitor the outcome of those issues (closed immediately, discussion, eventual pull request)
• Use those outcomes to assign how "good" or "bad" that generated issue was
• Use that scoring as a way to feed back into the model to influence it to create more "good" issues

If this is what's happening, then it's essentially offloading your LLM's reinforcement learning scoring to open source maintainers.

Really great piece. We have recently seen many popular lemmy instances struggle under recent scraping waves, and that is hardly the first time its happened. I have some firsthand experience with the second part of this article that talks about AI-generated bug reports/vulnerabilities for open source projects.

I help maintain a python library and got a bug report a couple weeks back of a user getting a type-checking issue and a bit of additional information. It didn't strictly follow the bug report template we use, but it was well organized enough, so I spent some time digging into it and came up with no way to reproduce this at all. Thankfully, the lead maintainer was able to spot the report for what it was and just closed it and saved me from further efforts to diagnose the issue (after an hour or two were burned already).

Wow, I hadn't realized until you pointed it out that you can't delete pm's (I guess without getting admins to fiddle with the db). I still use my lemmy account to moderate some lemmy communities, but I am appreciating using piefed as my threadiverse consumption platform more and more.

Welcome to lemmy! I just wanted to shout out Piefed, a fediverse software similar to lemmy (that I am posting from) that is actually written using flask!

I am very new at using flask, but have found that the flask community on reddit has been one that I have had to dip into from time to time as I have been noodling away at a project. So, it's nice to see one on here as well.

You have clearly never driven on 93 through Boston where the person you replied to said they are from (aka the Big Dig). It is basically an entire highway that is underneath the city. There are many on and off ramps, lanes suddenly become exit only, complex multi-lane exits that branch...it's intimidating. As somebody that has lived in the Boston area for 15 years now, I still mess things up.