GVradar_level2.ipynb is a great notebook! As someone who has worked with Python and meteorology data before I knew exactly how to get it up and running.
However, this notebook could be improved for folks new to the package in a few ways.
The first Markdown:
"Download Data from NEXRAD AWS: Run last cell FIRST"
Great information, I know what this means. -> scroll to the bottom and run the last cell first -> ... -> the last cell is a blank cell!
Running this cell would not fulfill the purpose of making "get_kwargs", "get_kwargs_product", and "make_movie_mp4" available at the beginning of the notebook (although running the cell above it would). A small thing but it could be made more clear by just deleting this blank empty cell!
Another small thing is the input and output of the notebook. The intended first cell is currently "In [26]" which could also be confusing to someone first starting out! Rerunning the notebook so this is "In [1]", "In [2]", ... "In [6]" might the intended path through the notebook more clear.
My guess is this notebook was run all the way through a few times as a test before being uploaded to Github. (My guess is it was probably uploaded saving outputs from the 6th time through!)
GVradar_level2.ipynb is a great notebook! As someone who has worked with Python and meteorology data before I knew exactly how to get it up and running.
However, this notebook could be improved for folks new to the package in a few ways.
The first Markdown:
"Download Data from NEXRAD AWS: Run last cell FIRST"
Great information, I know what this means. -> scroll to the bottom and run the last cell first -> ... -> the last cell is a blank cell!
Running this cell would not fulfill the purpose of making "get_kwargs", "get_kwargs_product", and "make_movie_mp4" available at the beginning of the notebook (although running the cell above it would). A small thing but it could be made more clear by just deleting this blank empty cell!
Another small thing is the input and output of the notebook. The intended first cell is currently "In [26]" which could also be confusing to someone first starting out! Rerunning the notebook so this is "In [1]", "In [2]", ... "In [6]" might the intended path through the notebook more clear.
My guess is this notebook was run all the way through a few times as a test before being uploaded to Github. (My guess is it was probably uploaded saving outputs from the 6th time through!)