Global / local rope wavelength

[copybara-service]

Global / local rope wavelength

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[IFaTaK]

Comment on frequency vs. wavelength usage

I noticed that the PR introduces a lot of mentions of frequency, but in several cases, the BASE_FREQUENCY variable is passed into functions expecting a wave_length argument. This creates an inconsistency—should we standardize on either frequency or wavelength across the codebase?

If we are moving towards "frequency," maybe function arguments and related variable names should reflect that change for clarity. Otherwise, if "wavelength" was the original intended concept, BASE_FREQUENCY, global_base_frequency, local_base_frequency, rope_base_frequency should be replaced by BASE_WAVELENGTH, global_base_wavelength, local_base_wavelength, rope_base_wavelength.

Would love to hear your thoughts on how we can make this more consistent! 🚀