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

Suggestions for features and changes #81

Open
AmeyV05 opened this issue Feb 20, 2023 · 1 comment
Open

Suggestions for features and changes #81

AmeyV05 opened this issue Feb 20, 2023 · 1 comment

Comments

@AmeyV05
Copy link

AmeyV05 commented Feb 20, 2023

Based on my usage and the features some other tidal analysis software have, I think, the following will be helpful:

  1. A flag to switch off the produced output while analysis and prediction. OR preferably save the output in a log file like done in dflowfm with a .dia file.
  2. Tidal ellipse parameters as output instead of the amplitude and phase can be a nice feature. But for that, a tidal analysis should be done on u and v together. In fact, doing a tidal analysis on currents should be done with u and v together as opposed to the current u and v separately.
  3. Confidence interval output and Signal to Noise ratio output can be helpful since data with a lot of uncertainties can be flagged off with these values. See, T-Tide or U-Tide.
  4. Possibility to include a trend in the analysis. Currently, it is assumed that tides don't change over time. But would be nice if we could input a trend, say linear etc in the analysis. See https://agupubs.onlinelibrary.wiley.com/doi/full/10.1029/2022JC018845 and T-tide.
  5. A nice harmonic analysis to have will be the tidal harmonic analysis of GNSS buoy data. This is somewhat different than harmonic analysis on tide gauges since in this case the buoy is spatially varying. Very few software actually have this feature.
@veenstrajelmer veenstrajelmer changed the title Suggestions for features and changes. Suggestions for features and changes Jun 27, 2023
@veenstrajelmer
Copy link
Collaborator

veenstrajelmer commented May 17, 2024

@AmeyV05 minor update: with the last release (hatyan 2.8.0) usage of the logging module was implemented. Therefore, you can set the logging level like in the example notebook. The default logging level is to only show warnings, which is probably what you are looking for with your first suggestion.

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

No branches or pull requests

2 participants