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

DM-18610: Add fields, limited mutability, and trim/assembly-state tracking to cameraGeom #28

Merged
merged 1 commit into from Nov 4, 2019

Conversation

czwa
Copy link
Contributor

@czwa czwa commented Sep 18, 2019

This now says suspectLevel = 0, which means it blanks everything. Disable doSuspect.

Copy link

@natelust natelust left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Your commit title is too long. There is a comment that is a question which seems to mean its an actionable item. Does that mean this is not really done? Does it mean that there needs to be a ticket spawned? If the latter create the ticket and put that in the comment instead of a question. Fixing it would be even better (if it is trivial) or creating a ticket and then doing it.

The camera config does not set a suspect level, so we should not be
doing suspect masking.
@czwa
Copy link
Contributor Author

czwa commented Oct 3, 2019

I've updated the commit to be more direct. It looks like this has relied on the previous amplifier implementation setting SuspectLevel to NaN, and then relying on ip_isr to ignore this. Explicitly disabling isr.doSuspect when the camera definition does not define a SuspectLevel seems the most appropriate solution.

@czwa czwa merged commit ee3235e into master Nov 4, 2019
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