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

Initial automated reporting #4

Open
RobertPincus opened this issue Jul 30, 2020 · 2 comments
Open

Initial automated reporting #4

RobertPincus opened this issue Jul 30, 2020 · 2 comments

Comments

@RobertPincus
Copy link
Collaborator

It would be neat to ensure that each YAML file phase file is sensible. That might mean

  • segment times (other than ground) lie between take-off and landing times
  • only one primary kind per segment(?
  • ??

It would also be neat to make light-weight diagnostics at each push. One might be plan and/or side views of the segments for each flight, organized in some sensible way.

@RobertPincus can set this up to run for each commit once scripts are complete.

@RobertPincus
Copy link
Collaborator Author

Another test: a time window can't belong to two segments of the same kind.

@RobertPincus
Copy link
Collaborator Author

If we adopt the idea of subsets (profile ascending as always part of a profile) we need to check that the two tags are applied to the same segment, or that the subset is part of a longer segment described by the superset.

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

1 participant