--
You received this message because you are subscribed to the Google Groups "sympy" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sympy+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/e7898bdb-d1e4-49fd-94c7-66ba8a840511n%40googlegroups.com.
Okay, I apologize for the tone of the conversation and for any offense caused to Jorge Ramos.
Please feel free to ask any questions. I’m happy to explain my opinion in more detail:
Not all expectations of SymPy come from strictly applying algebraic algorithms to specific problems.
Many people use SymPy as a flexible tool to solve mathematical problems, and in that regard, it overlaps with the goals of AI.
Certainly, this overlap could reduce SymPy's "attractiveness" or "competitiveness" to some extent.
I've occasionally participated in product design meetings in the industry.
It’s increasingly difficult to engage people with ideas that rely solely on SymPy or similar computer algebra systems.
People are already seeing the successes of AI products, and their expectations for these products are rising,
especially when new developments come from companies like Google or OpenAI.
Maybe Jorge Ramos or Maaz Muhammad are particularly passionate about SymPy
and feel unhappy with my statements (or maybe not).
I completely understand—it's similar to how someone might react if I were critical of their favorite musician or athlete.
However, I want to note that I’ve spent a significant part of my life working with SymPy.
I rarely make statements based on misunderstandings, and I have no intention of shaming a project that I’ve been deeply involved with.
I’m always trying to learn new things and prepare for changes in the world.
Our existing knowledge can become obsolete with new tools,
and I’ve already noticed that there is a vast amount of knowledge outside SymPy,
that could be used to understand or improve SymPy.
And that's why I'm always watching over movements of AI, as well as Lean.
To be more productive, SymPy itself can enhance its geometry capabilities by incorporating Wu's method or a deductive database approach,
which are useful in addressing geometric challenges.
I’ve also shared the implementation of the Area method with SymPy, which can be searched.
I had a few discussions after Christopher Smith's comments, which I believe could be useful to share:
This also by Hongbo Li(Lee) ?
https://www.issac-conference.org/2017/assets/tutorial_slides/Li.pdf
--
You received this message because you are subscribed to the Google Groups "sympy" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sympy+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/0d3d94ac-b3f9-48b1-bbea-512ce4ce1f22n%40googlegroups.com.
AI achieves silver-medal standard solving International Mathematical Olympiad problems - Google DeepMind
Recently, Google had announced the result that their AI model, AlphaProof and AlphaGeometry can silver medal in IMO problems. Their system is hybrid of symbolic models, and uses proof assistant Lean as backend, which guarantees that the proof can be verified automatically.
ChatGPT had many problems that it can hallucinate the steps of proof, and keep human verifying their result, as well as understaing the steps, so expressing proof as formal proof statements is a gain.
I think that if we want to avoid the losing competition, and make AI systems work collaborative, symbolic computation should be focused to solve only a few 'formal' problems in 100% precision and speed.
I also think that such advances in AI systems can raise concerns about software engineering careers, or educational system, which may be interesting for some readers in the forum.
Also, I notice that software engineering is changing, because AI models can complete a lot of code, and precision is improving, or people are improving the skills of prompting.
It also seems to be deprecating code sharing efforts for open source communities, because code can be generated rather than shared.