-
Notifications
You must be signed in to change notification settings - Fork 21
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
Pullrequest #42
Pullrequest #42
Conversation
Conflicts: tools.py
Conflicts: artview/components/menu.py artview/components/plot.py execute_two.py
remove the example plugins improve window placement in standard script add -F option to open file directly, no dialog change standard field from 'reflectivity' to pyart.config.get_field_name('reflectivity') add test to avoid breaking down dow to incorrect field calculate_attenuation and phase_proc_lp plugins name to capital letters
…nto pullrequest Conflicts: artview/components/plot_radar.py artview/components/tools.py
…nto pullrequest Conflicts: artview/components/__init__.py artview/components/plot_radar.py
… pullrequest Conflicts: artview/__main__.py artview/components/menu.py artview/components/plot_radar.py artview/core/common.py artview/parser.py artview/plugins/exemple1.py artview/plugins/exemple2.py setup.py
… into pullrequest Conflicts: artview/__init__.py
msg = "This is not a recognized radar file!" | ||
radar_warning = False | ||
grid_warning = False | ||
if self.mode in ("radar","all"): |
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.
What does "all" mean here?
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.
radar and grid
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.
Gotcha.
if ntilt < 0: | ||
ntilt = len(self.rTilts)-1 | ||
elif ntilt >= len(self.rTilts): | ||
ntilt = 0 | ||
self.Vtilt.change(ntilt) |
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.
What's going on with the if statement here? When would ntilt be less than 0?
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.
This will and is happening when pressing down even if tilt already equal 0. Note this line has no test for that. The only reason we haven't notice this is because python is saving us by allowing negative index, now I'm just doing this looping around explicit, so I don't have to test Vtilt. Notice I have a list with valid values for the Vvariables, and Vtilt shouldn’t have negative values.
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.
Interesting, I had not caught this.
Okay, I'm going to accept the changes. I've found a couple little bugs that I'll start as issues. |
This is United Pull Request (#28 #37 #39 #40 and #41)
changes include but do not restrict to:
@nguy you may merge this one