Custom Query (780 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (10 - 12 of 780)

1 2 3 4 5 6 7 8 9 10 11 12 13 14
Ticket Resolution Summary Owner Reporter
#1223 fixed Expand permitted range of transformed data in Corfunc implementation awashington smk78
Description

User Sam Welborn (UPenn) notes that at present the correlation function analysis doesn't permit the viewing or output of the transforms beyond x=200 Ang, which implies you have no features-of-interest in the scattering at Q<0.032 Ang-1. This limit was inherited from the original Corfunc program and suited the requirements (and computational resources at the time) of those that developed it. But with hindsight it now restricts the applicability and usefulness of this functionality in SasView. Sam's data (attached) has a feature at ~600 Ang, for example.

I suggest a two-step approach:

1) Raise the hard=coded output limit to 1000 Ang: as this should be trivial I've made it a blocker for the 4.2.1 release;

2) In SasView 5, consider adding editable input boxes to the correlation function GUIs to allow the user to define the transform limit (currently set to 100 x Qmax) and the display range discussed above.

#1222 fixed smearing options incorrect on show2D and show1D in fitpage GitHub <noreply@…> butler
Description

only the "no smearing" radio button should be enabled when no model is chosen. This is true when opening a new FitPage but if one immediately clicks on show2D the custom pinhole option is enabled (the only valid option in 2D when no smearing data is available). If the show1D option is now pressed, instead of going back to the original options, both custom pinhole and custom slit are now showing as available (again the only options available if the data has no smearing info).

This is because the _set_smear_buttons() method does not check for the existence of self.model

This should be a trivial fix and given the smear fixing work already in 4.2.1 suggest it get added to that release

#1221 fixed ABS reader does not read in USANS data properly GitHub <noreply@…> krzywon
Description

The change to read in qmean in the ABS reader broke the reading of USANS data. I have already pushed a fix into PR 180, for the NXcanSAS reader.

1 2 3 4 5 6 7 8 9 10 11 12 13 14
Note: See TracQuery for help on using queries.