Skip to content

Fix the issue of using '_flinalg' in NFINDR#15

Open
rguliev wants to merge 1 commit intoctherien:masterfrom
rguliev:fix-flinalg-issue-14
Open

Fix the issue of using '_flinalg' in NFINDR#15
rguliev wants to merge 1 commit intoctherien:masterfrom
rguliev:fix-flinalg-issue-14

Conversation

@rguliev
Copy link
Copy Markdown

@rguliev rguliev commented Mar 18, 2025

Fixes #14

From scipy 13.0 on, sp.linalg._flinalg is not available.
Which is fine, because it's not meant to be used directly:)

This pull request replaces sp.linalg._flinalg determinant function with sp.linalg.det to fix error. Might become a slower, I haven't checked the performance.


For more details, open the Copilot Workspace session.

Fixes ctherien#14

From scipy 13.0 on, `sp.linalg._flinalg` is not available.
Which is fine, because it's not meant to be used directly:)

This pull request replaces `sp.linalg._flinalg` determinant function with `sp.linalg.det` to fix error. Might become a slower, I haven't checked the performance.

---

For more details, open the [Copilot Workspace session](https://copilot-workspace.githubnext.com/ctherien/pysptools/issues/14?shareId=XXXX-XXXX-XXXX-XXXX).
@sputnik2481
Copy link
Copy Markdown

Quick question just for clarification, when that returns it returns a scalar (hence the determinant aspect) why is the value still have the [0] following it? Including that didn't allow my test to run.

Thank you!

@ctherien
Copy link
Copy Markdown
Owner

ctherien commented Mar 29, 2026 via email

@ctherien
Copy link
Copy Markdown
Owner

ctherien commented Mar 29, 2026 via email

@sputnik2481
Copy link
Copy Markdown

It was a hack, not a good idea Le ven. 27 mars 2026 à 14:38, sputnik2481 @.> a écrit :

sputnik2481 left a comment (ctherien/pysptools#15) <#15?email_source=notifications&email_token=AEBAWNJQ2YWHH5SUW4HSV4D4S3DB7A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJUGQ2TCNJUGY42M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOS2XA4S7MNXW23LFNZ2F633QMVXF6Y3MNFRWW#issuecomment-4144515469> Quick question just for clarification, when that returns it returns a scalar (hence the determinant aspect) why is the value still have the [0] following it? Including that didn't allow my test to run. Thank you! — Reply to this email directly, view it on GitHub <#15?email_source=notifications&email_token=AEBAWNJQ2YWHH5SUW4HSV4D4S3DB7A5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJUGQ2TCNJUGY42M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOS2XA4S7MNXW23LFNZ2F633QMVXF6Y3MNFRWW#issuecomment-4144515469>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEBAWNI3VINAVQEBAWQEIAD4S3DB7AVCNFSM6AAAAACXCMNG4WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNBUGUYTKNBWHE . You are receiving this because you are subscribed to this thread.Message ID: @.
>

Yes that's what I thought, as this function returns a singleton value eg a scalar so putting the [0] after it will always throw an error because that's the wrong object type. To fix this you must remove the [0] after as it does not have an index because its just a singleton integer value.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Fails with scipy 1.13.1

3 participants