This pull request contains a few fixes and adjustments in preparation for the upcoming release:
1.) A strictQC argument has now been added as an optional keyword argument of the Profile object. The default value is True and is set to this until all developers can agree on a consensus of how to handle some of the odd observed profiles that the SHARPpy GUI is reading in. Setting this to False will cause the Profile object constructor to skip over some of the more strict QC checks on the data being passed to the constructor. This setup is a potential fix to the issues associated with the QC when reading in different data types through the GUI and the script.
2.) When plotting the boundary on the hodograph, the 0-6 km shear and 9-11 km storm relative wind vectors get transposed properly now. This fix was motivated after the boundary motion function was shown in NSHARP.
3.) I have removed (for the time being) the storm mode estimation function that is drawn when you plot a boundary motion on the hodograph. This is due to a couple of odd errors that I noticed when using this function. This functionality will be reinstated once I get time to properly fix it.
This pull request contains a few fixes and adjustments in preparation for the upcoming release:
1.) A strictQC argument has now been added as an optional keyword argument of the Profile object. The default value is True and is set to this until all developers can agree on a consensus of how to handle some of the odd observed profiles that the SHARPpy GUI is reading in. Setting this to False will cause the Profile object constructor to skip over some of the more strict QC checks on the data being passed to the constructor. This setup is a potential fix to the issues associated with the QC when reading in different data types through the GUI and the script.
2.) When plotting the boundary on the hodograph, the 0-6 km shear and 9-11 km storm relative wind vectors get transposed properly now. This fix was motivated after the boundary motion function was shown in NSHARP.
3.) I have removed (for the time being) the storm mode estimation function that is drawn when you plot a boundary motion on the hodograph. This is due to a couple of odd errors that I noticed when using this function. This functionality will be reinstated once I get time to properly fix it.