Custom Query (780 matches)
Results (1 - 3 of 780)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #929 | fixed | Problem deleting data in first fit page | krzywon | Adamo |
| Description |
If send data to FitPage1 and then try to delete it, the FitPage1 deletes and "points" to FitPage2. As soon as you send other data to Fitting, the following error appears: Fitting set_data: in method 'AuiNotebook_GetPageIndex', expected argument 2 of type 'wxWindow *' |
|||
| #261 | fixed | Default number of bins in Phi average is not ideal | Adrian Rennie | |
| Description |
20 is a poor default choice as it gives 18 degree bins. Something that was divisible by 4 and 6 would be better (most likely symmetries). Thus 36 would probably be good, but that may be too fine a division for most data. 18 is a good compromise - 20 degree bins including bins centered on 0, 90, 180 and 270 degrees. |
|||
| #850 | fixed | Custom pinhole smearing is broken? | krzywon | Federica Sebastiani |
| Description |
Federica Sebastian - student at LU noticed a problem with the custom smearing in SasView? 4.0.1 … Setting values in custom pinhole smearing gives a different answer to loading the same values from a data file. Some instruments do not provide resolution information - hence the need for the custom smearing. Taking data set and calculating a, say, 8% dQ/Q and putting that in the file as the 4th column behaves as expected. Generating a custom pinhole smear with *the same dQ_low and dQ_high* as the dataset with "fake" resolution column gives a completely different answer and blows the curve out. Attached images are for the attached data set with (a) resolution from dQ data which was faked in the file. (b) resolution from a custom pinhole smear using the same dQ_low and dQ_high |
|||
