Changes between Initial Version and Version 1 of Ticket #1102, comment 2

Ticket #1102, comment 2

initial	v1
1	1	While we seem to be closing in on the best way to handle the resolution, the latest change does not entirely fix things. While it now seems to work correctly for reasonable resolutions for extreme cases it does not as shown by the attached report explaining the testing between IGOR and !SasView.
2	2
3		The problem occurs for a data set where the resolution cutoff at -2.5 sigma would be beyond zero and thus in negative territory which is never possible. ~~It looks like that truncation is causing problems though whether it is also what is causing the unexpected behavior is not clear at this point~~. The traceback call is
	3	The problem occurs for a data set where the resolution cutoff at -2.5 sigma would be beyond zero and thus in negative territory which is never possible. The new code is throwing an error whenever trying to calculate the resolution smeared model. Whether from the truncation or not is unclear but it should be noted that the error is thrown for both data sets. The traceback call is
4	4	{{{
5	5	20:39:29 - INFO : sasmodels.kernelpy: 39: load python model power_law