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

flexbe_logs #92

Open
joeaaron opened this issue Dec 10, 2019 · 4 comments
Open

flexbe_logs #92

joeaaron opened this issue Dec 10, 2019 · 4 comments

Comments

@joeaaron
Copy link

hi, I wonder where can I find the log files.

If I run the command rosun flexbe_widget evaluate_logs, nothing happens.

@pschillinger
Copy link
Member

Logging of state transitions is disabled by default to not spam the file system. In order to enable it, set the respective argument in the launch file of the onboard engine:

roslaunch flexbe_onboard behavior_onboard.launch log_enabled:=True

Each behavior execution will then create a new file in the log folder, by default ~/.flexbe_logs.

Also note the recent PR #90 to fix the help text of the evaluate_logs script.

@joeaaron
Copy link
Author

OK, Thanks for the reply.
Then, another question:
Container has 3 types, I can not really understand Prority, is there any examples?

@pschillinger
Copy link
Member

You can consider a Priority container as an interrupt routine inside a Concurrency container. More generally, whenever a Priority container is entered, no other states will be active outside of this container (their "pause" events will be triggered and "resume" when the Priority container is exited). Other than that, it is the same as a Statemachine container.

@joeaaron
Copy link
Author

Thanks for your kind reply.
I've watch the video Use userdata key remapping to pass runtime data between states.
But it's too complicated for me. If I just want to use the CalculationState to accomplish this. How to make it?

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