Conversation
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request refactors the Equivalent Acceleration Spectrum (EAS) calculation within the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request adjusts the calculation of the Effective Amplitude Spectrum (EAS) to apply Konno-Ohmachi smoothing after the EAS component calculation, which is the correct approach. The change is logical and well-explained. My review includes one suggestion to address code duplication introduced by this change, which would improve the maintainability of the code.
Based on a discussion about FAS smoothing for EAS we should apply the konno smoothing after the EAS component calculation. Sadly this will slow down the calculation due to having to apply smoothing twice in the function, but I see no way around it :(
https://uceqeng.slack.com/archives/C0C0QPGDR/p1773555712228999?thread_ts=1773553959.094039&cid=C0C0QPGDR
The differences from what I have seen is not much but it's meant to the the proper way for EAS.
