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

Tickets/sitcom 1131 #2

Merged
merged 17 commits into from May 14, 2024
Merged

Tickets/sitcom 1131 #2

merged 17 commits into from May 14, 2024

Conversation

boutigny
Copy link
Contributor

This is a Pull Request to review both the Tech. Note and the associated notebook.
Tech Note has been read by Doug Neil.

@boutigny boutigny requested a review from b1quint April 25, 2024 16:53
Copy link

Check out this pull request on  ReviewNB

See visual diffs & provide feedback on Jupyter Notebooks.


Powered by ReviewNB

index.rst Outdated

.. Metadata such as the title, authors, and description are set in metadata.yaml
This technote uses data from the VMS, dc accelerometers and IMS to estimate the effect of the Fan Coil Units (FCUs) are likely to have on image quality
Copy link
Member

Choose a reason for hiding this comment

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

Could you replace VMS with Vibration Monitoring System (VMS)?

Copy link
Member

Choose a reason for hiding this comment

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

Same with IMS and Independent Measurement System (IMS)?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

index.rst Outdated

This technote uses data from the VMS, dc accelerometers and IMS to estimate the effect of the Fan Coil Units (FCUs) are likely to have on image quality
Primarily we use the Vibration Monitoring System (VMS) of the M1M3 for more information see the VMS confluence page (link here).
The VMS data are stored in a single hdf5 data file (/sdf/data/rubin/shared/mtm1m3_test_files/vms_data/2023/12/M1M3-2023-12-07T00:00.hdf) acquired on 2023/12/07. A description of the
Copy link
Member

Choose a reason for hiding this comment

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

Could you put single-back-quotes before and after the path to convert it into code-style? This formatting can improve readability. Something like this:
/sdf/data/rubin/shared/mtm1m3_test_files/vms_data/2023/12/M1M3-2023-12-07T00:00.hdf

Copy link
Contributor Author

@boutigny boutigny May 6, 2024

Choose a reason for hiding this comment

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

single back quotes gave a ugly result so we put the text in a block of code

index.rst Outdated

**This technote is a work-in-progress.**
This technote uses data from the VMS, dc accelerometers and IMS to estimate the effect of the Fan Coil Units (FCUs) are likely to have on image quality.
Copy link
Member

Choose a reason for hiding this comment

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

Small suggestion:

This technical note analyzes data from the VMS, dc accelerometers, and the IMS to assess how the operation of Fan Coil Units (FCUs) might impact image quality.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

index.rst Outdated

Data quality
============
We have checked that the TMA was not moving during this test (Azimuth: -25.95 deg - Elevation: 89.95 deg) and that the mirror was raised (MTM1M3.logevent_detailedState == ACTIVEENGINEERING)
Copy link
Member

Choose a reason for hiding this comment

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

I recommend adding single-back-quotes here too:
MTM1M3.logevent_detailedState == ACTIVEENGINEERING

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Same as above --> we made a block of code

index.rst Outdated
We have checked that the TMA was not moving during this test (Azimuth: -25.95 deg - Elevation: 89.95 deg) and that the mirror was raised (MTM1M3.logevent_detailedState == ACTIVEENGINEERING)
with Hard Point in standby mode.

We also checked that during the whole duration of the test, the Force Balance System was turned off.
Copy link
Member

Choose a reason for hiding this comment

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

I would simplify this sentence:

We also checked that the Force Balance System was turned off during the whole duration of the test.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

done

Copy link
Member

@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 added a few comments but, in overall, this is very good. As I was reading, I was wondering if the ~ 40Hz could be associated with the fans themselves. It seems that 2550 RPM is equivalent to 42,5 Hz. On top of that, I wonder if we do not see the RPM reflected in the PSD. Wouldn't that be expected?

@boutigny
Copy link
Contributor Author

boutigny commented May 6, 2024

Thank you very much for the review. We added a comment about the peak at 42 Hz appearing in some of the plots when fans run at 100% speed. It is difficult to be sure of what we are seeing here but as you say it looks pretty natural to see this peak.

@b1quint
Copy link
Member

b1quint commented May 7, 2024

My final recommendation after running the notebook locally would be to try to have the x-labels with the time stamps with a consistent label formant. The plot produced right before the section "PSD Analysis" section has a good format.

Another option, maybe for the future, would be to define a reference time and convert the x-axis into seconds. This is easier to work with and, sometimes, easier to read. Of course, this means that we need to print this reference time somewhere. But you are already doing that in the titles.

@boutigny
Copy link
Contributor Author

Thanks for the review.
I have corrected the plots with time stamps in order to get the same format for all of them

Copy link
Member

@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.

It looks good now. Thank you!

@boutigny boutigny merged commit 9a67953 into main May 14, 2024
2 checks passed
@boutigny boutigny deleted the tickets/SITCOM-1131 branch May 14, 2024 15:22
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

4 participants