Skip to content
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

Changing setting_desiredPointDensity has no effect on CPU usage. #27

Open
bot-lin opened this issue Sep 19, 2022 · 1 comment
Open

Changing setting_desiredPointDensity has no effect on CPU usage. #27

bot-lin opened this issue Sep 19, 2022 · 1 comment

Comments

@bot-lin
Copy link

bot-lin commented Sep 19, 2022

I have played around the setting_desiredPointDensity variable and seen that changing the value of setting_desiredPointDensity has no effect on CPU usage.
I did it by adding the point density option into the function MainSettings::parseArgument in the MainSetting.cpp file .

    if(1 == sscanf(arg, "pointdensity=%d", &option))
    {
        
        setting_desiredPointDensity = option;
        printf("POINT DENSITY: %d.\n", option);
        
        return;
    }

When set setting_desiredPointDensity to 1000 (GUI has been disabled)
Screenshot 2022-09-19 at 20 07 01

When set setting_desiredPointDensity to 100

Screenshot 2022-09-19 at 20 09 11

@lukasvst
Copy link
Owner

Are you sure that the variable is not overwritten when you set the prefix (argument prefix=0), see https://github.com/lukasvst/dm-vio/blob/master/src/util/MainSettings.cpp#L221 ? This might depend on the the order of the commandline arguments.
You can also set the point density in the Pangolin GUI with the slider during runtime.

Otherwise, are you using realtime execution (preset=1) or non-realtime (preset=0)?
In the latter case DM-VIO will process the sequence as quickly as possible so you should see a difference in execution time, not in CPU usage.

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

No branches or pull requests

2 participants