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-28184: gen3 crosstalk generation does not set DET_NAME correctly. #70

Merged
merged 2 commits into from Jan 5, 2021

Conversation

czwa
Copy link
Contributor

@czwa czwa commented Jan 4, 2021

Fix bad metadata that wasn't fully tested.

@czwa czwa requested a review from plazas January 4, 2021 22:16
Copy link
Contributor

@plazas plazas left a comment

Choose a reason for hiding this comment

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

Looks good. Maybe you can comment/clarify in the Jira ticket what was actually wrong?

'detector': detectorId,
}

finalResults = self.solver.run(ratios, camera=camera, outputDims=outputDims)
Copy link
Contributor

Choose a reason for hiding this comment

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

Why were the output dimensions not needed before, but now they are being passed? What difference does it make?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I didn't think they were needed, because I had thought that the calibChip was the name, and so could be used to set the _detectorName attribute. Constructing an outputDims for gen2 also reduces possible differences.

@czwa czwa merged commit b7080ec into master Jan 5, 2021
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