PyTLiDAR - Test Report - 5/31/2025
Questions:
- Do users of the program already know what the parameters are?
- Is the end goal for this to be a .exe file? What will happen to the console output?
Issues:
- The final html report did not seem to use the set intensity value that I selected. I set an intensity threshold of 50000, and I saw that the report had the full tree model. I was expecting only the trunk as I saw in cloud compare.
- Plot text is cutoff on the generated .pdf files
- Saw a crash occur with parameters set to 1.0. This will occur if the user accidentally unchecks the Generate Values with the default startip.
Minor Issues:
- You are able to resize the window to the title bar
- Typo in instructions
-
Potential Suggestions:
- I remember seeing tooltips mentioned. Is that in scope for this GUI?
- A user using this tool for the first time might enter values while reading the instructions. Maybe the options and inputs could have the same ‘flow’ as the instructions.
- It might be confusing to someone using this for the first time that clicking the batch processing automatically loads the next screen to view the point cloud. Perhaps there could be a ‘next’ or ‘confirm’ button at the bottom to give them a chance to confirm all their inputs.
- It might be confusing to someone using this for the first time that clicking the batch processing automatically loads the next screen to view the point cloud. Perhaps there could be a ‘next’ or ‘confirm’ button at the bottom to give them a chance to confirm all their inputs.
- There is no indicator like a popup to user for the scenario where the parameter inputs are empty. Causes a value error since something in the program is trying to read an empty string.
- Maybe the .pdf files could have the same title as the html, showing the specific parameter they refer to so that you can find the one you want easier.
- Are we able to change the parameters in this window? Might make it easier without needing to reload the point cloud, unless processing step is needed before visualizing (?) .
