Opened 15 years ago
Closed 14 years ago
#76 closed bug (fixed)
2D functions from DANSE have # of integration points as a fitting parameter
| Reported by: | srkline | Owned by: | srkline |
|---|---|---|---|
| Priority: | major | Milestone: | Analysis_4.0_Beta |
| Component: | Analysis | Keywords: | |
| Cc: | Blocking: | ||
| Task: | DanseIntegration |
Description
This really shouldn't be. "Enough" points should be used to ensure that the model returns the correct answer. A faster, incorrect answer is misleading at best. According to Lionel, his experience shows that 25 pts is fine for the radius polydispersity, but between 80-100 may be more appropriate for the angular integrations, depending on the range (0-pi/2 would require fewer than 0-pi)
Change History (2)
comment:1 Changed 15 years ago by srkline
comment:2 Changed 14 years ago by srkline
- Resolution set to fixed
- Status changed from new to closed
done, as a "hard" wired 25 points in each Igor function. different numbers could be passed to the XOP as needed.
Note: See
TracTickets for help on using
tickets.
Currently, the functions are wrapped to hide the # of points used, and is hard-wired at 25. Until real testing is done, the "optimal" number won't be known. It may be necessary to have several versions with different # of points, or set through a (documented) global if the speed penalty is not too great.