{"push_id":717972068,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"eaa16d5a6e28caecc83cbb5915ff865e2539b2f8","before":"4eb4d6f11f4272f7a80d094f8ce299dcadc876bc","commits":[{"sha":"eaa16d5a6e28caecc83cbb5915ff865e2539b2f8","author":{"email":"c11a44a1fabb337fb7ce9ca89aebdfeaf2cfb793@baylor.edu","name":"Blake Schultze"},"message":"Reconstruction working with experimental Edge Phantom data\n\nThe issue preventing properly executing GPU image reconstruction using\nthe large experimental Edge Phantom data set appears to have been\nresolved by increasing the MAX_INTERSECTIONS for an MLP path to 1280.\nThis was initially increased to 1024 and this ran properly for several\nhours, but this eventually stopped working.  It is unclear at the moment\nwhy this occurred, there were many things changed in this time including\nthe height of the reconstruction volume and 1 aspect of the MLP\nendpoints routine, but restoring these to their previous implementations\ndid not appear to help.  The radius of the reconstruction volume appears\nto have the most impact on this issue and this was increased during\ntesting so it is possible that this or 1 of the other parameters had in\nfact been changed between the time when it worked and when it ceased to\nwork, only time and more investigation will tell.\n\nWhen it was running properly there were at least several intervals\nbetween executions and it appears that error tend to occur in groups of\nexecutions particularly when they are ran with little time between.  I\nam beginning to wonder if the repeated consecutive executions are\noverheating the GPU and causing malfunctions that would not normally\noccur because there does seem to be some correlation between these\nevents which I had been viewing as random, but perhaps they are not.","distinct":true,"url":"https://api.github.com/repos/BlakeSchultze/pCT_Reconstruction/commits/eaa16d5a6e28caecc83cbb5915ff865e2539b2f8"}]}