The results of calling plume(...) and puff(...) are pretty hideous and can be slow to print. Unfortunately, I made the bad life choice of using this as a lazy way of unit testing a bunch of stuff -- instead of checking that parameters are being initialized correctly I just check that the REPL string is the same since it includes printing out the floating point representations of everything.
A generic function could be written that takes a PlumeSolution or PuffSolution type and prints out a nice summary, like exists for Scenarios. Tackling this would also require a bunch of doc tests to be changed to maintain test coverage.
The results of calling
plume(...)andpuff(...)are pretty hideous and can be slow to print. Unfortunately, I made the bad life choice of using this as a lazy way of unit testing a bunch of stuff -- instead of checking that parameters are being initialized correctly I just check that the REPL string is the same since it includes printing out the floating point representations of everything.A generic function could be written that takes a
PlumeSolutionorPuffSolutiontype and prints out a nice summary, like exists forScenarios. Tackling this would also require a bunch of doc tests to be changed to maintain test coverage.