Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Best debug strategy #108

Open
sorenchr2011 opened this issue Jul 3, 2022 · 1 comment
Open

Best debug strategy #108

sorenchr2011 opened this issue Jul 3, 2022 · 1 comment

Comments

@sorenchr2011
Copy link

Hi,
Thanks for the great documentation and making this open! I am implementing a custom function and it compiles and is callable.
I always have my input parameters returned and it runs just for 1 iteration with a "0" return state. Chi-square is large.
How do I best trouble shoot this? CPUfit and call from C++? Or is there a simpler way to try to locate the point(s) of error.
Thanks!
Soren

@superchromix
Copy link
Collaborator

Hi,

Sorry for the late response. Yes, debugging is going to be easiest in Cpufit, and this will let you test whether your expressions for the fit functions and derivatives are correct, etc.

cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants