{"action":"opened","issue":{"url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/1080","repository_url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort","labels_url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/1080/labels{/name}","comments_url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/1080/comments","events_url":"https://api.github.com/repos/GRIFFINCollaboration/GRSISort/issues/1080/events","html_url":"https://github.com/GRIFFINCollaboration/GRSISort/issues/1080","id":390314790,"node_id":"MDU6SXNzdWUzOTAzMTQ3OTA=","number":1080,"title":"Errors on TRWPeak","user":{"login":"AndrewMac1","id":5428622,"node_id":"MDQ6VXNlcjU0Mjg2MjI=","avatar_url":"https://avatars1.githubusercontent.com/u/5428622?v=4","gravatar_id":"","url":"https://api.github.com/users/AndrewMac1","html_url":"https://github.com/AndrewMac1","followers_url":"https://api.github.com/users/AndrewMac1/followers","following_url":"https://api.github.com/users/AndrewMac1/following{/other_user}","gists_url":"https://api.github.com/users/AndrewMac1/gists{/gist_id}","starred_url":"https://api.github.com/users/AndrewMac1/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/AndrewMac1/subscriptions","organizations_url":"https://api.github.com/users/AndrewMac1/orgs","repos_url":"https://api.github.com/users/AndrewMac1/repos","events_url":"https://api.github.com/users/AndrewMac1/events{/privacy}","received_events_url":"https://api.github.com/users/AndrewMac1/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-12-12T16:49:25Z","updated_at":"2018-12-12T16:49:25Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"This is just a note on something I saw today. I was fitting peaks with a TRWPeak and I repeated the same command by mistake (pushed up and hit enter) and it gave me a different values for the error on the fits. The central values were the same and the fits were effectively identical, this can be seen in the screenshots. I didn't change any parameters in the fit between repeating the command, but the errors bounced back and forth between two values of +/-1173 and +/-700 seemingly randomly. I looked at the covariance matrix of the fit and tried to reproduce the error but I could not reproduce it. I tried a few other things as well, making sure I defined the fit the same way in each circumstance but still could not reproduce the error. This is primarily a note to let people know that I saw this effect, although if anyone else is able to reproduce it in the future it would be good to understand why this happened. This might be more of a root error minimization issue than a grsisort issue but I think people should still be aware that it was seen. \r\n\r\n**Additional information:** \r\ngrsisort version - 3.1.3.3\r\nroot version - 6.08.06\r\n\r\n**Screenshots:**\r\n<img width=\"574\" alt=\"screen shot 2018-12-12 at 10 38 42 am\" src=\"https://user-images.githubusercontent.com/5428622/49884041-f134ec80-fe01-11e8-9478-dc089443277f.png\">\r\n<img width=\"644\" alt=\"screen shot 2018-12-12 at 10 39 03 am\" src=\"https://user-images.githubusercontent.com/5428622/49884066-014ccc00-fe02-11e8-86bf-d79e2fda710b.png\">\r\n<img width=\"402\" alt=\"screen shot 2018-12-12 at 10 39 35 am\" src=\"https://user-images.githubusercontent.com/5428622/49884357-ac5d8580-fe02-11e8-9520-b6d46252eb33.png\">\r\n<img width=\"415\" alt=\"screen shot 2018-12-12 at 10 39 52 am\" src=\"https://user-images.githubusercontent.com/5428622/49884363-b1bad000-fe02-11e8-9e6d-0076ac2dc67e.png\">\r\n"}}
{"actor":{"display_login":"AndrewMac1"}}