Next-release changes on Mumps Wrapper

[williampiat3]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/22246770757. Examine the logs at this URL for more detail.}

[williampiat3]

@conda-forge-admin, please rerender

[fbordeu]

Hello, can you point me to the commit in Muscat that use python-mumps?

[williampiat3]

Hello, can you point me to the commit in Muscat that use python-mumps?

The commit is not yet public. Basically I replaced the NativeMumpsSolver.pxd by a MumpsSolver.py that has the same API but that uses python-mumps.
Ideally we should remove altogether the wrapper to directly use python-mumps however to smooth the transition (Mostly for OpenPisco) I created a class that has the same API than the legacy CMumpsSolver (The naming was by the way terribly confusing, the previous CMumpsSolver stood for "C interface for the Mumps Solver" and was actually the interface for Dmumps).

Switching to python-mumps has several advantages:

• support for DMumps (Double precision), ZMumps (Complex double precision), SMumps (Simple precision) and CMumps (Complex simple precision). Where previously only DMumps was available
• MPI support for solving large systems on multiple nodes on Linux and OSX
• The package is externally maintained
• Support for sparse RHS

[williampiat3]

I don't think I'll spend too much time on the feedstock for now, it's a bit early. I will wait for the commit to go public

[fbordeu]

Nice job. Be careful, merging this branch in the feedstock will produce new version of the packages, so this needs to be merged into the branch preparing the next release.

[williampiat3]

OSX build seems to be failing "only" due to dependencies
Windows build fails for no clear reason for me. I am willing to lend a hand @Laureleen06

[Laureleen06]

Hello, I know how to fix windows build but I do not know why python-mumps is looking for mumps-seq between 5.6.2 and 5.6.3 it is very limited

[williampiat3]

mumps-seq is still an undirect dependency (because it is a dependency of python-mumps)
For OSX there is a conflict on python3.10 I would like to make a test with only python>=3.11

[Laureleen06]

What I understand is that we should give more flexibility to libscotch

[williampiat3]

python-mumps has a rather restrictive dependency on python as I see, the current package only support python >= 312 (Sorryyyy)

[williampiat3]

Testing to make a python-mumps build for python <=3.11:
conda-forge/python-mumps-feedstock#30

[fbordeu]

python-mumps has a rather restrictive dependency on python as I see, the current package only support python >= 312 (Sorryyyy)

Do you know why?

[williampiat3]

@conda-forge-admin, please rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipe/meta.yaml:

• ❌ The feedstock has no .ci_support files and thus will not build any packages.

For recipe/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/22247013423. Examine the logs at this URL for more detail.}

[Laureleen06]

@conda-forge-admin, please rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/22448882217. Examine the logs at this URL for more detail.}