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

USS Survey #97

Closed
NoFoolLikeOne opened this issue Oct 8, 2018 · 3 comments
Closed

USS Survey #97

NoFoolLikeOne opened this issue Oct 8, 2018 · 3 comments
Assignees
Projects

Comments

@NoFoolLikeOne
Copy link
Contributor

NoFoolLikeOne commented Oct 8, 2018

The survey in the Canonn plugin will log USS drops but will also allow logging of USS from supercruise without drops.

USS Drops can be marked as confirmed however supercruise reports are manual and therefore considered suspect.

We could use USS drop data to prove that the type and threat level are valid combinations and request confirmation if it is in any way suspect.

Counts of USS types/threat are not important.

We will need to update the strapi model with appropriate statuses and we will need a mechanism for validating manual submissions.

Also keeping track of the time spent in supercruise would be useful for the perspective of Hrafnagud which needs to know if a system has been surveyed to count it as complete.

@NoFoolLikeOne NoFoolLikeOne created this issue from a note in Roadmap (Reporting) Oct 8, 2018
@NoFoolLikeOne NoFoolLikeOne moved this from Reporting to EDMC-Canonn in Roadmap Oct 8, 2018
@NoFoolLikeOne NoFoolLikeOne self-assigned this Oct 8, 2018
@derrickmehaffy
Copy link
Contributor

How useful is the data on USS from supercruise? Realistically I don't see any benefit, and would be difficult to "validate" as they are non-static

@NoFoolLikeOne
Copy link
Contributor Author

We used it on Hrafnagud to survey systems quickly. So people went to the target system specified in the patrol, Then they flew around for 15 minutes reporting all the USS they saw and then moved on to the next. If the system had no NHSS after an hour of supercruise (4 commanders doing 15 minutes each) then we took it off the patrol list and marked it as not having any NHSS It means that even if you were just passing through in a hurry you could still contribute.

Validation issues are around errors selecting the wrong threat level. The code does preselect the most likely threat level for you which makes it easier to get it right. We could produce a list of confirmed type and threat combinations to validate against and if we have USS of interest in a system eg NHSS 0 1 or 2 for instance but no USS Drop then we could send someone out there to try and confirm a drop.

@derrickmehaffy
Copy link
Contributor

Decided to remove normal USS in favor of NHSS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Roadmap
EDMC-Canonn
Development

No branches or pull requests

2 participants