-
Notifications
You must be signed in to change notification settings - Fork 58
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 all ROS_RATE occurences to ROSParam #99
base: indigo-devel
Are you sure you want to change the base?
Conversation
Great work! @pranaypratyush changing params over so many files is really appreciable 👍 |
@pranaypratyush Use BTW, Good work 👍 |
@pranaypratyush TODO:
|
Shouldn't I use |
Yeah @pranay you should do that
|
3a12fc7
to
ebe0dbb
Compare
@pranaypratyush @prudhvid ROS_ERROR is for printing, it's one of the log levels (like In python the exception itself is called |
@icyflame What about in c++ ? C++ doesn't show stack traces ( I think ). So do I use RuntimeError there too ? |
I think there's a mechanism. |
btw @pranaypratyush Next time around google before coming here! |
I actually google before asking here. Why the hell do you think there is so much time gap between the comments ? I found out that ' |
Um, so apparently, the stack trace can be seen by using |
7be450c
to
9e824d6
Compare
- Modified all occurences of ROS_RATE in .cpp files to accept a ROSParam double instead of always using a default value. - Fixes auviitkgp#98
- Modified all occurences of ROS_RATE in .py files to accept a ROSParam double instead of always using a default value. - 'yaml' file is yet to be added. - Fixes auviitkgp#98, only for `.py` files
- Created a new `yaml` file under `Scripts/launch/yaml/ros_rate_param.yaml`. - Modified all `.launch` files to load the `.yaml` file. - Fixes auviitkgp#98, adds `yaml` file
- Modifies `.py` files to throw `RuntimeError` and show stack trace when `/ros_rate` not found. - Modifies `.cpp` files to throw `runtime_error` when `/ros_rate` not found. - Reverts back legacy `.launch` files to original state. - Other fixes regarding `ros::NodeHandle`. - Fixes auviitkgp#98, exception handling and debug commit
9e824d6
to
1d8ed92
Compare
|
else: | ||
rate = default_rate | ||
|
||
try: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
try and except are not at the same indentation level.
@pranaypratyush See the above line comments, and fix them. Also, revoke the changes done to legacy / unused files using This will make the diff more streamlined. |
sys.exit(0) | ||
|
||
r = rospy.Rate(temp_rate) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aniket11bh @kshitijgoel007 @VishnuDuttSharma We should change these rates to the global constant right?
No, you should not change these rates. Because But, we can change the rate at which sensor data is published by the node. Which is not written separately in our current code. Also, need to fix the problem of DVL package not getting any data somtimes. |
@pranaypratyush there you go. Revoke the changes in the sparton, nqDvl packages as well. Use |
So do I edit my last commit or create a new commit ? |
New commit. |
- Also debugs some indentation issues that crept in during the last commit.
@pranaypratyush Still to revert trax, sparton, nqDvl. Also, run the |
So I am reverting all changes to all files under |
@pranaypratyush Rebase this branch. Since this PR was taking too long, another PR ( #101 ) was merged into the main branch. That moves all the unused files into |
@icyflame Ok so I have reverted all files in |
@pranaypratyush LGTM. We will merge this once we have tested this on the vehicle. |
@pranaypratyush If you are testing the vehicle, you must test this out. And if it works, then we should immediately merge it. Not having it on master could cause problems later. |
@pranaypratyush @Nightfury18 This has been tested I think. The diff looks fine to me, and I will merge it by tonight unless one of you can bring up an issue with the PR :) |
No description provided.