-
Notifications
You must be signed in to change notification settings - Fork 767
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logging and Code Coverage #658
Comments
Have you considered presenting GTSAM to Google Summer of Code to have extra hands helping in this kind of topics? I could give you a hand as a mentor in case you decide to participate. |
@jlblancoc I have zero cycles :-) If you want to do this, I fully support it! You are a GTSAM primary by now :-) |
Hmm... I could help you with the registration process, etc. since I've been through it in past years. https://github.com/borglab/gtsam/wiki/Ideas-page-for-GTSAM-Google-Summer-of-Code-2021 Please, confirm whether we can have by the next Friday:
Best, |
PS: project ideas may be based on some pending issues / PRs, or brand new ideas, etc. |
OK, let me take a look and give a think. Do you have a list of projects you want to mentor? |
I have a bunch of project suggestions. Things like getting the QP solver working, better examples from existing datasets, wrapper features and some old issues that we've basically put on the backburner. I'll update the Wiki page during my lunch break today. |
It's a bit too late now. Focus on your A->B |
Less work for me, plus I made a breakthrough on the URDF issue I was having so the A->B is progressing quickly. |
Varun: my advice is, try to write down those project ideas in the wiki, in
your spare time, so they will help next year's proposal. But don't let this
distract you from whatever is your key goal now! :-)
Best
|
You're right @jlblancoc. I just saw your comments on this issue today morning, so replied in case this was time sensitive. 😊 |
Feature
Request to add in:
Motivation
Logging will help us print exceptions, warnings and other useful information while at the same time providing a switch which will not impact performance.
Code coverage will ensure we are unit test driven in our development.
Pitch
This feature will require quite a bit of CMake competency, but it should be straightforward enough. Any user should then be able to add various logging statements throughout the codebase (or via a simple include such as
<gtsam/base/logging.h>
.The code coverage module will be invoked via a Github Action that will allow us to place a Markdown badge on the README.
Alternatives
Additional context
The text was updated successfully, but these errors were encountered: