Help disabling 'wall_time' output using DenseQRSolver

[Brendon Tower]

Hello,

I've using ceres solve to DenseQR problems. For some reason, I still see 'wall_time.cc:74' output messages in stdout, even when I use the following options:

options.logging_type = ceres::SILENT;

options.minimizer_progress_to_stdout = false;

I've also made this call at the beginning of my application:

google::InitGoogleLogging(argv[0]);

For reference, the output I am seeing looks like this:

DenseQRSolver::Solve

                                   Delta   Cumulative

                           Setup :    0.00000      0.00000

                           Solve :    0.00004      0.00004

                        TearDown :    0.00000      0.00004

                           Total :    0.00000      0.00005

Am I missing something?

Thanks in advance!

Brendon

[Sameer Agarwal]

Are you using miniglog? or glog?

--
You received this message because you are subscribed to the Google Groups "Ceres Solver" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ceres-solver...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ceres-solver/CAMxwhVb_aDW9b%3D11jmP%3DnEPpZfzx%3DoOksP7xOTbjJsYQiCYGaA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Brendon]

We are using minilog.

[Sameer Agarwal]

1. Consider using glog. It is much nicer and does not have these problems.

2. If you insist on using miniglog, then you can manipulate a compiler macro "MAX_LOG_LEVEL" to control miniglog's verbosity.

https://github.com/ceres-solver/ceres-solver/blob/master/internal/ceres/miniglog/glog/logging.h#L304

Sameer

To view this discussion on the web visit https://groups.google.com/d/msgid/ceres-solver/1d2070e4-821f-4fb3-ba45-f997589d6757%40googlegroups.com.

[Brendon]

Thanks Sameer, I appreciate your prompt responses. I will start by modifying the MAX_LOG_LEVEL, if that doesn't solve it I can look at moving over to glog instead. Thanks again!

[Brendon]

Quick update: adjusting MAX_LOG_LEVEL in logging.h has resolved my issue. Thanks again Sameer!

[Taylor Braun-Jones]

On Fri, Feb 24, 2017 at 11:37 AM, 'Sameer Agarwal' via Ceres Solver <ceres-...@googlegroups.com> wrote:

2. If you insist on using miniglog, then you can manipulate a compiler macro "MAX_LOG_LEVEL" to control miniglog's verbosity.

For FDA-approved medical devices glog adds yet another piece of SOUP (Software Of Unknown Provenance) and all validation paper work that entails. It would be great if Ceres had a simple CMake flag to adjust the logging severity for Ceres internal non-templated code. Setting CMAKE_CXX_FLAGS is inconvenient because you blow away the CMake default value (or have to know and hard-code that value).

What do you think about this patch?

https://ceres-solver-review.googlesource.com/#/c/9560/?

Taylor

[Sameer Agarwal]

Thanks Taylor that patch sounds useful, I will let alex review it.

--

You received this message because you are subscribed to the Google Groups "Ceres Solver" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ceres-solver...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ceres-solver/CAKfKJYuRENmWLCYY9AhY8tCGs_wLjbK_AyieRvEyb-1ZLu7H4A%40mail.gmail.com.

[Alex Stewart]

This should now be merged into master - thanks Taylor.

-Alex

To view this discussion on the web visit https://groups.google.com/d/msgid/ceres-solver/CABqdRUDSdYR%3DaTKxA%2BT3jtrVQ_4%2BGzfACt%2B3F-g5Mu1oqE6_4g%40mail.gmail.com.