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

Fixed tests #51

Merged
merged 14 commits into from May 7, 2017
Merged

Fixed tests #51

merged 14 commits into from May 7, 2017

Conversation

ChristopherRabotin
Copy link
Owner

Tests will fail until ChristopherRabotin/smd#120 is merged.

@coveralls
Copy link

Coverage Status

Coverage decreased (-15.5%) to 73.472% when pulling e899562 on issue35b into cf5c77b on master.

…ut that PropUntil stalls.

This is a strange issue: if measurements are separated by exactly the time step, then it will stall and not propagate at all. If add a full time step, it'll propagate *a bit* and then stall until there is a large delta between the previous and the following step. Weird af.
…t happens, still investigating. Added a WG to try to compensate, does not help, so let me try to fix this without a wait group.
…ough. The weird situation is that I change the pointer, and it seems to work for exactly that one call, but then at the end PropUntil it doesn't care about the change that I did. WTF? I will need to check in PropUntil that the state has been updated correctly.
@coveralls
Copy link

Coverage Status

Coverage increased (+0.1%) to 89.162% when pulling ca856fb on issue35b into cf5c77b on master.

…al. Otherwises, they're out of sync. Weird af. Don't know what is up. I think there may be a way to make this sequential where the gorouting also does the full update of the KF when a measurement exists and then have the channel reading function not do anything when there is no measurement. I'm starting to think that is my only hope (and it already sounds like disgusting code).
@coveralls
Copy link

Coverage Status

Coverage increased (+0.1%) to 89.162% when pulling 0d360d0 on issue35b into cf5c77b on master.

BUG: Changing the time step will lead to a negative wait group, which is further evidence that something is going on where one go-routine is advancing faster the other one.
0015 2017-01-01 09:49:20 +0000 UTC state: [-5043.047850508302  3559.0460654109465   3286.876581144037  -3.715706446671131  -6.448704059501171   1.282882872645048]
0015 2017-01-01 09:49:22 +0000 UTC orbit: [-5050.467503249387 3546.140371857773 3289.4346631090925] [-3.7039434176182806 -6.456984476348821 1.2751980995803665]
@coveralls
Copy link

Coverage Status

Coverage increased (+0.1%) to 89.162% when pulling 09a9a87 on issue35b into cf5c77b on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.1%) to 89.162% when pulling ed86ddf on issue35b into cf5c77b on master.

@coveralls
Copy link

Coverage Status

Coverage increased (+0.1%) to 89.162% when pulling 7eacb1a on issue35b into cf5c77b on master.

@ChristopherRabotin ChristopherRabotin merged commit 85e79d1 into master May 7, 2017
@ChristopherRabotin ChristopherRabotin deleted the issue35b branch May 7, 2017 16:22
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

Successfully merging this pull request may close these issues.

None yet

2 participants