I just wanted to make note that I updated the above information about the 1600 sensors. They are 12 bit, not 16 bit.
You are not alone. I thought this was a transient issue as a re-compile of master fixed it for me, but that was on an older build than what you are using. There have been at least 3 reports of this now, here is the other thread:
Perhaps it was only a reboot of the system that cleared it and something else is going on that sets this bad state.
Is the guider properly respecting the dither, or is it noticing the guide stars jump after guiding is enabled again, and the spike is correcting the mount back to pre-dither tracking?
If the error is in the codebase, yes. If the error is in a website or other resource outside of the codebase, it is probably best to post the error on the forum.
How do I submit a bug report or other issue to the development team?
Before you submit a bug to the team, there are a few things that you should do first that are greatly helpful.
1. Search the forum for keywords about your bug. Others may have encountered it as well, and can help you.
2. Search the below links to see if anyone has already reported your issue. Add comments if you have additional information that would be helpful.
3. If you do not find anything on the forum or existing reports about your issue, make a post about your findings in the proper forum category. This helps others that may encounter the issue and will usually get the attention of a developer familiar with the code, for comment.
4. If a solution is not found in any of the 3 lines above, then below, please find the links for reporting issues.
Thank you for your help. This project continues to improve because of contributors. A bug report is a helpful contribution.
If your issue is in INDI:
Report an issue with INDI
If your issue is in the INDI 3rd party device drivers:
Report an issue with INDI 3rd party drivers
If your issue is in kstars or Ekos:
kstars and Ekos bug reports at KDE
PR = Pull Request also known as a Merge Request or MR. If you make changes or fixes to the code and you would like to have the repository management team take a look at the changes for inclusion in the code base, you can submit a PR/MR with the fix. The PR makes it easier for the team to get your fix into place in the code. I mentioned this because you did your own sleuthing in the code and found the problem. You understand the fix, and have proposed a solution. Submitting a PR would entail setting up a development environment for INDI development, forking the repository on github, making the change against your fork, and then creating the PR to have the team review the change. There is a section in the top menu, under "Manufacturers" to assist in setting up an INDI development environment.(which I think I am going to propose we change to "Creators", or something that sounds less industrial).
If you are not comfortable doing this for any reason, a bug report where the sleuthing has been done is the next best thing, so thank you!
You are welcome. Also, PRs are welcomed if you feel so inclined.
I looked for this after the site was updated, but never found it. I ended up having to do some internet sleuthing.
In the top nav bar
Given your cartoon, the proper answer here is "yes."
Truly though, either is fine. Perhaps we do it this way. If a simple fix, add to this thread. If it may take some discussion or solicitation of input from others, create a new post.