some JuMP solvers are noisy even when configured to their most quiet level

Open
  • Is something wrong?
#25 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
julia
Domain
data

Research direction

Start by locating the calls to external optimizers in the Julia package and compare their console behavior with the issue's capture_stdout example. Done means the affected solvers no longer produce unwanted console output when configured at their quietest level, while still returning their results.

Written by the indexing model from the issue text.

Description

Some of the external optimizers we use create a ton of junk console output. Consider using a redirection to quiet them up.

example solution:

function capture_stdout(f)
    # return f()
    stdout_orig = stdout
    flush(stdout)
    (rd, wr) = redirect_stdout()
    r = f()
    close(wr)
    redirect_stdout(stdout_orig)
    return r
end
Dominant language
Julia
Stars
20
Forks
8
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from JuliaGraphs/GraphsMatching.jl

All issues in JuliaGraphs/GraphsMatching.jl

Similar issues

More Julia issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.