This looks wonderful, I've dreamt of something like this back when I was in academia!
You mention some advanced stuff like abstract index notation which is usually the hardest part to get right with things like simpy and even mathematica, how does your package handle simplifications of complex tensor expressions (GR, hydrodynamics, etc.)?
dinunnob 6 hours ago [-]
You can specify symmetry/antisymmetry patterns for tensor index slots and it takes advantage of that to speed up the calculations. This part was pretty important for me so i spent some time thinking about it. I wanted to try to put xACT’s patterns in but it would have been quite the undertaking.
dinunnob 6 hours ago [-]
It could definitely be better though
viraptor 1 days ago [-]
> The "Pipe" approach (Cleaner for agents
How did you verify the benefit?
dinunnob 7 hours ago [-]
Not rigorous, but intuition derived from expression string complexity for postfix operations vs standard sympy style. I’ll take this out, readme was written from sleazy used car salesman advertising point of view. Was more rigorous in examples/test
dinunnob 5 hours ago [-]
removed claim from README
OutOfHere 1 days ago [-]
Please never use `from something import *`, not even for a demo. It is not explicit, not maintainable, and goes against all Python guidelines. Certainly never expect any user to use it either.
cl3misch 1 days ago [-]
FWIW the afaik most common symbolic math Python library sympy does that on the first page of their tutorial. I think in this space it's pretty common.
I have to admit that I still like to use the ancient
from pylab import *
in scripts that only I will ever see. It makes it so much easier to use numpy in a "tool of thought" way. I would never do this in a library, though.
OutOfHere 1 days ago [-]
Two wrongs don't make a right. It risks significant ambiguity in longer snippets or files, and is therefore bad practice.
dinunnob 7 hours ago [-]
Yeah, you’re not wrong. Makes the syntax a bit annoying here (goal was to lower barrier of entry for physicists). I agree this is bad practice.
OutOfHere 6 hours ago [-]
In the limiting sense, especially when a user mixes your snippet with snippets from other packages, the barrier of entry becomes greater due to the resolution ambiguity, not less.
dinunnob 5 hours ago [-]
fixed in the readme. thanks -
while we are talking imports ... how did `import pyspark.sql.functions as F` ever get past the pep police
marcelbundle 1 days ago [-]
You would be suprised on how many large scale project I saw this beauty lamao, not saying that this is okay, people just dgaf
Confirm2754 4 days ago [-]
[dead]
Rendered at 22:57:53 GMT+0000 (Coordinated Universal Time) with Vercel.
You mention some advanced stuff like abstract index notation which is usually the hardest part to get right with things like simpy and even mathematica, how does your package handle simplifications of complex tensor expressions (GR, hydrodynamics, etc.)?
How did you verify the benefit?
https://docs.sympy.org/latest/tutorials/intro-tutorial/intro...
I have to admit that I still like to use the ancient
in scripts that only I will ever see. It makes it so much easier to use numpy in a "tool of thought" way. I would never do this in a library, though.while we are talking imports ... how did `import pyspark.sql.functions as F` ever get past the pep police