Tootfinder

Analyzing the Performance of a 2.72kWp Rooftop Grid tied Photovoltaic System in Tarlac City, Philippines
Aldrin Joar Rodrigo Taduran, Leo P. Piao
https://arxiv.org/abs/2510.03487

Analyzing the Performance of a 2.72kWp Rooftop Grid tied Photovoltaic System in Tarlac City, Philippines
Residential and industrial areas are using rooftop grid-tied Photovoltaic (PV) systems, which are becoming increasingly popular. This is because solar energy reduces electrical consumption and provides free energy, while also lowering carbon emissions to create a more sustainable environment. This paper aims to analyze the 2.72kW p rooftop grid-tied PV system performance between 2020 and 2023 in Tarlac City, Philippines. The PV generated yearly is measured by Array Yield (YA), Reference Yield (…

DreamState - Awakening - #DreamState #NowPlaying https://muz4now.com/2023/dreamstate-aw

DreamState - Awakening - #DreamState #NowPlaying
Stan Stewart - @muz4now

'I think this is really his time': Why the Raiders need Tyree Wilson to live up to first-round billing https://www.espn.com/nfl/story/_/id/45859555/las-vegas-raiders-defensive-lineman-tyree-wilson-first-round…

Tilastokeskus #energia
https://stat.fi/julkaisu/cm1hsrs6k3d0b07w73wv7p1ea#msdynmkt_trackingcontext=ccfc7ee2-174b-45f4-87f1-e0431fab…

Energian loppukäyttö jatkoi laskuaan vuonna 2023 | Tilastokeskus

Dynamical Excitation as a probe of planetary origins
Brad M. S. Hansen, Tze-Yeung Yu, Neel Nagarajan, Yasuhiro Hasegawa
https://arxiv.org/abs/2510.01332 https://

Dynamical Excitation as a probe of planetary origins
We present a set of numerical simulations of the dynamical evolution of compact planetary systems migrating in a protoplanetary disk whose inner edge is sculpted by the interaction with the stellar magnetic field, as described in Yu et al. (2023). We demonstrate that the resulting final distribution of neighbouring planet period ratios contains only a small surviving fraction of resonant systems, in accordance with observations. The resulting planetary architectures are largely in place by the …

Optimizing Districting Plans to Maximize Majority-Minority Districts via IPs and Local Search
Daniel Brous, David Shmoys
https://arxiv.org/abs/2508.07446 https://

Optimizing Districting Plans to Maximize Majority-Minority Districts via IPs and Local Search
In redistricting litigation, effective enforcement of the Voting Rights Act has often involved providing the court with districting plans that display a larger number of majority-minority districts than the current proposal (as was true, for example, in what followed Allen v. Milligan concerning the congressional districting plan for Alabama in 2023). Recent work by Cannon et al. proposed a heuristic algorithm for generating plans to optimize majority-minority districts, which they called short…

Downward self-reducibility in the total function polynomial hierarchy
Karthik Gajulapalli, Surendra Ghentiyala, Zeyong Li, Sidhant Saraogi
https://arxiv.org/abs/2507.19108 https…

Downward self-reducibility in the total function polynomial hierarchy
A problem $\mathcal{P}$ is considered downward self-reducible, if there exists an efficient algorithm for $\mathcal{P}$ that is allowed to make queries to only strictly smaller instances of $\mathcal{P}$. Downward self-reducibility has been well studied in the case of decision problems, and it is well known that any downward self-reducible problem must lie in $\mathsf{PSPACE}$. Harsha, Mitropolsky and Rosen [ITCS, 2023] initiated the study of downward self reductions in the case of search probl…

LLM coding is the opposite of DRY
An important principle in software engineering is DRY: Don't Repeat Yourself. We recognize that having the same code copied in more than one place is bad for several reasons:
1. It makes the entire codebase harder to read.
2. It increases maintenance burden, since any problems in the duplicated code need to be solved in more than one place.
3. Because it becomes possible for the copies to drift apart if changes to one aren't transferred to the other (maybe the person making the change has forgotten there was a copy) it makes the code more error-prone and harder to debug.
All modern programming languages make it almost entirely unnecessary to repeat code: we can move the repeated code into a "function" or "module" and then reference it from all the different places it's needed. At a larger scale, someone might write an open-source "library" of such functions or modules and instead of re-implementing that functionality ourselves, we can use their code, with an acknowledgement. Using another person's library this way is complicated, because now you're dependent on them: if they stop maintaining it or introduce bugs, you've inherited a problem, but still, you could always copy their project and maintain your own version, and it would be not much more work than if you had implemented stuff yourself from the start. It's a little more complicated than this, but the basic principle holds, and it's a foundational one for software development in general and the open-source movement in particular. The network of "citations" as open-source software builds on other open-source software and people contribute patches to each others' projects is a lot of what makes the movement into a community, and it can lead to collaborations that drive further development. So the DRY principle is important at both small and large scales.
Unfortunately, the current crop of hyped-up LLM coding systems from the big players are antithetical to DRY at all scales:
- At the library scale, they train on open source software but then (with some unknown frequency) replicate parts of it line-for-line *without* any citation [1]. The person who was using the LLM has no way of knowing that this happened, or even any way to check for it. In theory the LLM company could build a system for this, but it's not likely to be profitable unless the courts actually start punishing these license violations, which doesn't seem likely based on results so far and the difficulty of finding out that the violations are happening. By creating these copies (and also mash-ups, along with lots of less-problematic stuff), the LLM users (enabled and encouraged by the LLM-peddlers) are directly undermining the DRY principle. If we see what the big AI companies claim to want, which is a massive shift towards machine-authored code, DRY at the library scale will effectively be dead, with each new project simply re-implementing the functionality it needs instead of every using a library. This might seem to have some upside, since dependency hell is a thing, but the downside in terms of comprehensibility and therefore maintainability, correctness, and security will be massive. The eventual lack of new high-quality DRY-respecting code to train the models on will only make this problem worse.
- At the module & function level, AI is probably prone to re-writing rather than re-using the functions or needs, especially with a workflow where a human prompts it for many independent completions. This part I don't have direct evidence for, since I don't use LLM coding models myself except in very specific circumstances because it's not generally ethical to do so. I do know that when it tries to call existing functions, it often guesses incorrectly about the parameters they need, which I'm sure is a headache and source of bugs for the vibe coders out there. An AI could be designed to take more context into account and use existing lookup tools to get accurate function signatures and use them when generating function calls, but even though that would probably significantly improve output quality, I suspect it's the kind of thing that would be seen as too-baroque and thus not a priority. Would love to hear I'm wrong about any of this, but I suspect the consequences are that any medium-or-larger sized codebase written with LLM tools will have significant bloat from duplicate functionality, and will have places where better use of existing libraries would have made the code simpler. At a fundamental level, a principle like DRY is not something that current LLM training techniques are able to learn, and while they can imitate it from their training sets to some degree when asked for large amounts of code, when prompted for many smaller chunks, they're asymptotically likely to violate it.
I think this is an important critique in part because it cuts against the argument that "LLMs are the modern compliers, if you reject them you're just like the people who wanted to keep hand-writing assembly code, and you'll be just as obsolete." Compilers actually represented a great win for abstraction, encapsulation, and DRY in general, and they supported and are integral to open source development, whereas LLMs are set to do the opposite.
[1] to see what this looks like in action in prose, see the example on page 30 of the NYTimes copyright complaint against OpenAI (#AI #GenAI #LLMs #VibeCoding

On Jiang's Bounded Index Property for products of nilmanifolds
Peng Wang, Qiang Zhang
https://arxiv.org/abs/2507.06132 https://ar…

On Jiang's Bounded Index Property for products of nilmanifolds
In 2023, Zhang and Zhao presented the first examples of aspherical manifolds lacking the Bounded Index Property (BIP) for fixed points. This answered a question posed by Jiang in 1998 in the negative. In this paper, we first extend the notion of BIP to that of iterations of selfmaps (BIP$_k$), and then demonstrate BIP$_k$ for certain products $M\times N$ of nilmanifolds. Finally, we give characterizations for the Lefschetz number, the Nielsen number, and the minimal number of fixed points of se…

More Joutnalists killed in #Gaza by #Israel
#AlJazeera said the attack “is a desperate attempt to silence voices in anticipation of the occupation of Gaza.”

A Dormant Captured Oort Cloud Comet Awakens: (18916) 2000 OG44
Colin Orion Chandler, William J. Oldroyd, Chadwick A. Trujillo, Dmitrii E. Vavilov, William A. Burris
https://arxiv.org/abs/2507.21324

A Dormant Captured Oort Cloud Comet Awakens: (18916) 2000 OG44
We report the discovery of activity emanating from (18916) 2000 OG44 (alternately designated 1977 SD), a minor planet previously reported to be both an extinct comet or an asteroid on a cometary orbit. We observed 2000 OG44 with a thin tail oriented towards the coincident anti-solar and anti-motion vectors (as projected on the sky) in images we acquired on UT 2023 July 24 and 26 with the Apache Point Observatory 3.5-meter Astrophysical Research Consortium telescope (New Mexico, USA). We also in…

Strong converse rate for asymptotic hypothesis testing in type III
Nicholas Laracuente, Marius Junge
https://arxiv.org/abs/2507.07989 https://

Strong converse rate for asymptotic hypothesis testing in type III
We extend from the hyperfinite setting to general von Neumann algebras Mosonyi and Ogawa's (2015) and Mosonyi and Hiai's (2023) results showing the operational interpretation of sandwiched relative Rényi entropy in the strong converse of hypothesis testing. The specific task is to distinguish between two quantum states given many copies. We use a reduction method of Haagerup, Junge, and Xu (2010) to approximate relative entropy inequalities in an arbitrary von Neumann algebra by those in finit…

Nearly Optimal Bounds for Stochastic Online Sorting
Yang Hu
https://arxiv.org/abs/2508.07823 https://arxiv.org/pdf/2508.07823

Nearly Optimal Bounds for Stochastic Online Sorting
In the online sorting problem, we have an array $A$ of $n$ cells, and receive a stream of $n$ items $x_1,\dots,x_n\in [0,1]$. When an item arrives, we need to immediately and irrevocably place it into an empty cell. The goal is to minimize the sum of absolute differences between adjacent items, which is called the \emph{cost} of the algorithm. It has been shown by Aamand, Abrahamsen, Beretta, and Kleist (SODA 2023) that when the stream $x_1,\dots,x_n$ is generated adversarially, the optimal cos…

Good Morning #Canada
Day #8 of The Dirt on Canadian Farming takes us back east to New Brunswick, which is not that "new" BTW. If it seems like we're jumping around the country in this series, with no logic, well, congratulations, you're paying attention.
New Brunswick's agricultural and agri-food sector reached a record of $1.23 billion in farm cash receipts in 2023, with potatoes, blueberries, maple syrup, and dairy all key products. Within that number lies good and bad news. The province had one of the largest decreases in farm operators in the country, but profits per farm have increased. Blueberry farms increased, and the province is 2nd in Canada in production. In 2024, New Brunswick announced the Agricultural Sustainability Program to assist farmers with reducing tillage, maintaining ponds and wetlands, and protecting pollinator habitat, critical and marginal landscapes, trees, riparian areas and crop management.
#CanadaIsAwesome #Farming
https://www150.statcan.gc.ca/n1/pub/95-640-x/2016001/article/14803-eng.htm