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

Add new instrument notebook. #28

Merged
merged 2 commits into from Jan 20, 2023
Merged

Add new instrument notebook. #28

merged 2 commits into from Jan 20, 2023

Conversation

jbkalmbach
Copy link
Member

Documents how to use the new instrument configuration setup when running the Gen 3 AOS pipeline.

@review-notebook-app
Copy link

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

Copy link

b1quint commented Dec 15, 2022

The new notebook is very clear. Thank you for that! I wonder if it is intended to cover the requirements in the LVV-T2228 test case (Step 7 in the Test Script). If not, it is good (I added minor suggestions to the notebook).

@jbkalmbach
Copy link
Member Author

Thanks Bruno! For some reason it looks like your comments didn't show up on the ReviewNB version of the notebook. Can you look and make sure you can see them still?

As for LVV-T2228 it looks like this new update will help in that test case, especially the part where you can set the Defocal Offset configuration to None so that it will be automatically detected from the exposure. This would help in the T2228 where you are pistoning the camera a set amount. Instead of having to manually update that, the new code will know from the exposure headers.

@review-notebook-app
Copy link

View / edit / reply to this conversation on ReviewNB

b1quint commented on 2023-01-17T21:31:11Z
----------------------------------------------------------------

I believe that we should specify if the reader should execute this notebook in the summit lsp, TTS or USDF. I am not sure if it is implicit, but new people might join the project in the future and they might not know this. Maybe you can even write this at the top of this file since there are other places that includes paths.


Copy link

@b1quint b1quint left a comment

Choose a reason for hiding this comment

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

I think this looks good to me. It would be helpful to specify which test environment the reader can use to run this notebook. In any case, I approve this PR.

@jbkalmbach jbkalmbach merged commit 53888b1 into develop Jan 20, 2023
@jbkalmbach jbkalmbach deleted the tickets/DM-30189 branch January 20, 2023 00:23
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