Mantis - ALGLIB
|
|||||
Viewing Issue Advanced Details | |||||
|
|||||
ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
806 | Interpolation | minor | have not tried | 2018-03-30 16:06 | 2018-04-06 13:08 |
|
|||||
Reporter: | SergeyB | Platform: | |||
Assigned To: | SergeyB | OS: | |||
Priority: | normal | OS Version: | |||
Status: | resolved | Product Version: | |||
Product Build: | Resolution: | fixed | |||
Projection: | none | ||||
ETA: | none | Fixed in Version: | 3.14.0 | ||
Programming language: | Unspecified | ||||
|
|||||
Summary: | 0000806: FIXED: LSFit solver sometimes returns incorrect error estimates (HPC edition of ALGLIB for C#) | ||||
Description: |
LSFit solver performs actions which violate reverse communication protocol (reallocates one of the communication fields during optimization process). Although solution itself is detected/returned correctly, corrupt error estimates can be returned as result. This issue is relevant only for HPC edition of ALGLIB for C# (commercially licensed managed wrapper around native computational core). Managed edition and C++ edition can tolerate protocol violation. |
||||
Steps To Reproduce: | |||||
Additional Information: | |||||
Relationships | |||||
Attached Files: | |||||
|
|||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2018-03-30 16:06 | SergeyB | New Issue | |||
2018-03-30 16:06 | SergeyB | Status | new => assigned | ||
2018-03-30 16:06 | SergeyB | Assigned To | => SergeyB | ||
2018-03-30 16:06 | SergeyB | Programming language | => Unspecified | ||
2018-04-06 13:08 | SergeyB | Summary | LSFit solver sometimes returns incorrect error estimates (HPC edition of ALGLIB for C#) => FIXED: LSFit solver sometimes returns incorrect error estimates (HPC edition of ALGLIB for C#) | ||
2018-04-06 13:08 | SergeyB | Description Updated | |||
2018-04-06 13:08 | SergeyB | Status | assigned => resolved | ||
2018-04-06 13:08 | SergeyB | Fixed in Version | => 3.14.0 | ||
2018-04-06 13:08 | SergeyB | Resolution | open => fixed |
There are no notes attached to this issue. |