You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An error in the be_polyelectrolyte model was identified prior to release 4.2.0 and corrected. The error has been carried since 1998 and there was no quick and easy external validation of that change, partly because the implementation doesn't exactly follow the paper. It would be good if somebody could go through the paper and ensure that the code follows so that the disclaimer note in the docs can be removed.
{
"status": "new",
"changetime": "2018-09-28T17:32:06",
"_ts": "2018-09-28 17:32:06.332106+00:00",
"description": "An error in the be_polyelectrolyte model was identified prior to release 4.2.0 and corrected. The error has been carried since 1998 and there was no quick and easy external validation of that change, partly because the implementation doesn't exactly follow the paper. It would be good if somebody could go through the paper and ensure that the code follows so that the disclaimer note in the docs can be removed.",
"reporter": "butler",
"cc": "",
"resolution": "",
"workpackage": "McSAS Integration Project",
"time": "2018-09-28T17:32:06",
"component": "SasView",
"summary": "be_polyelectrolyte model needs proper validation check",
"priority": "critical",
"keywords": "",
"milestone": "SasView 4.3.0",
"owner": "",
"type": "defect"
}
The text was updated successfully, but these errors were encountered:
Added check for self.model to _set_smear_buttons and more info logging.
Smear buttons should now be enabled depending on 2D vs 1D, model or not,
and resolution data available or not.
Addresses #1222
An error in the be_polyelectrolyte model was identified prior to release 4.2.0 and corrected. The error has been carried since 1998 and there was no quick and easy external validation of that change, partly because the implementation doesn't exactly follow the paper. It would be good if somebody could go through the paper and ensure that the code follows so that the disclaimer note in the docs can be removed.
Migrated from http://trac.sasview.org/ticket/1186
The text was updated successfully, but these errors were encountered: