Skip to content

Conversation

@3n3l
Copy link
Contributor

@3n3l 3n3l commented Jan 15, 2026

Before this we always passed True to make_float_cg_solver(...)
instead of the verbose value.

Issue: #8707

Brief Summary

SparseCG was always printing information about convergence without a way to
turn off, this now respects the value of verbose that is passed in via ti.init(...), as it should be.

Walkthrough

We now pass the value of verbose to make_float_cg_solver(...)

Closes #8707


Note

Ensures CG solver logging adheres to ti.init(verbose=...).

  • SparseCG.__init__ now uses get_runtime().prog.config().verbose when creating _ti_core.make_cucg_solver, _ti_core.make_float_cg_solver, and _ti_core.make_double_cg_solver instead of always passing True.

Written by Cursor Bugbot for commit 4b6e2d1. This will update automatically on new commits. Configure here.

@3n3l 3n3l changed the title fix: SparseCG was not respecting verbose value [misc] feat: SparseCG now respecting verbose value Jan 15, 2026
@3n3l 3n3l changed the title [misc] feat: SparseCG now respecting verbose value [misc] SparseCG now respecting verbose value Jan 15, 2026
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.

Is there any way to make SparseCG not print out all the information all the time?

1 participant