Changes between Version 3 and Version 4 of DevNotes/Obsolete/v3p1PunchList


Ignore:
Timestamp:
Jun 28, 2015 4:29:49 PM (9 years ago)
Author:
butler
Comment:

—

Legend:

Unmodified
Added
Removed
Modified

  • DevNotes/Obsolete/v3p1PunchList

    v3 v4  
    1 = Release !SasView 3.1.0 Punch List = 
     1= !SasView 3.1.0 Release Punch List = 
    22This is a running list of things to address for release 3.1 
    33 
    4 * Remaining tickets 
     4=== Remaining tickets=== 
    55[[TicketQuery(status=accepted|assigned|new|reopened&milestone=SasView_3.1&group=priority&col=id|summary|milestone|status, table)]] 
    66 
    7 * from Richard 
     7=== Outstanding Questions (mostly from Richard) === 
    881. “report” button does nothing (nor for Steve King on build 83) 
    99  
    … …  
    1717  
    18186. If I set up 3 data sets with constraints, say have M2.radius=M1.radius, M3.radius=M1.radius but then fix M1.radius at say 30 ang, I would expect the constraints to still work, but I get error message on hitting Fit in constraints page.  
    19   
     19{{{  
    2020                Traceback (most recent call last): 
    2121  File "sas\perspectives\fitting\fit_thread.pyc", line 82, in compute 
    … …  
    3535  
    3636 None 
    37   
     37}}}  
    3838OK the work around for this is to also fix M2.radius etc manually. However if I do that and then hit Fit on constraints page, nothing happens not even an error message. So if I “Remove” the constraints on M2.radius and M3.radius, “Fit” now attempts to work but comes back with same error message as above in red, presumably because it now has an issue with radius.width which is still constrained and fitting. Indeed if I remove the constraints on radius.width the fit now works, but with independent values for the polydispersity. 
    3939