-
Notifications
You must be signed in to change notification settings - Fork 9
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
Features #246
base: patches
Are you sure you want to change the base?
Conversation
- this will help disambiguate from time series Channel objects - minor updates to doc strings - remove an unneeded return None
- Add some typehinting for DecimationLevel - working on finding if we can delete Decimation class
- once correctly dtyped, circular imports were encountered. - this was fixed by creating frequency_bands.py - also add FrequencyBands to __init__.py - alphabetize imports in __init__.py
- move get_fft_harmonics into window.py from decimation_level.py - add fft_harmonics method to Window and replace other imports and usages
- try to group the decimation-related attributes together at the top, and the STFT related attrs at the bottom
- this may not be needed and this json is slated for deletion, but until ready to delete this keeps the dual decimation classes close
- this is one of two main replacements that needs to be done on #235 - the next main replacement will be in FCDecimation
- add pass-through getters and setters for decimation_level and decimation_factor, - allowing FCDecimation to assing/access via self.time_series_decimation - remove attrs decimation_level and decimation_factor from fc decimation.json - update attrs in time_series_decimation.json
Fix issue 238 housekeeping (continued)
- this is for consistency - alternatively we can rename mt_metadata/transfer_functions to mt_metadata/tf
- add some tests for this class
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## patches #246 +/- ##
===========================================
- Coverage 84.98% 84.86% -0.12%
===========================================
Files 270 274 +4
Lines 20515 20535 +20
===========================================
- Hits 17435 17428 -7
- Misses 3080 3107 +27
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
- Defined a typehint SupportedNomenclature list - Added a test to verify that SupportedNomenclature typehint helper is consistent with the list of actual nomenclatures in CHANNEL_MAPS - also added NIMS system to CHANNEL_MAPS object - some minor updates to docstrings and typehints
- (except for skipping python 3.12 testing)
- band.width - band.fractional_bandwidth - band.Q
This PR will allow the ability to create features for FC's.
There is some book keeping as well as additional code.
A prototype json for defining weighting schemes based on features of the data is in aurora issue 61. To realize this we will need:
name
orid
), and it hasparameters
. These are not defined for the abstract base class, but instead are defined individually for each feature, such as "coherence", "multiple_coherence", "mahalanobis_distance", etc.weighting_curve
, that controls how weights are assigned for a given featureex
,ey
,hz
), so each output variable will be associated with a list of features, as well as aweighting_strategy_parameters
, which maps to a keyword. The simplest case would bemultipilcation
, i.e. simply multiply the weights from each feature together, but the keyword can map to more complicated methods in future, possibly also involvingweighting_strategy_parameters
.