-
Notifications
You must be signed in to change notification settings - Fork 3
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
Deprecate TransferFunctionHeader Class #109
Comments
This is actually a somewhat handy convenience class, the issue is that it duplicates data that are available elsewhere, in particular, all the data in this object seems to come from the processing Config() Thus, it would be best if this class were always generated by the processing config. The TransferFunctionHeader attrs that are called are the following:
|
TransferFunctionHeader is now generated only by the Processing class. This allowed the removal of a helper function that made the header from processing. Also added decimation level as an attr to the header. [Issue(s): #109]
Transfer Function Header is now consolidated into something that is generated as a method of Processing class. The only change to still consider is making this a dict rather than a class - changing it to an mt_metadata object. However, that task will be more easily done while migrating the Processing class into mt_metadata which is o be addressed during the FC implementation. |
If aurora's transfer_function class always has a processing_scheme instantiated when header is called, we can access header that way, via a method inside the transfer_function base class. To make this all work on the new fc branches, which should import the processing scheme from mt_metadata, and to avoid circular imports (from aurora) we will need to make TransferFunctionHeader a class that lives in mt_metadata. A good candidate for this would be a ListDict (or python-box) |
- eliminate standalone calls to initialze tf_header - make transfer function base class init in terms of (decimation level, processing scheme) rather than (tf_header, processing scheme) - add tf_header as @Property of transfer function class - make TransferFunctionHeader an mt_metadata ListDict rather than a standalone class [Issue(s): #109]
- also commented out one test in fix_issue_139 so that all tests will pass for PR [Issue(s): #109]
replace with method emtf_tf_header in processing class [Issue(s): #109]
This class has been completely deprecated and replaced with a ListDict that is returned by the emtf_tf_header method in processing.py |
This class has been completely deprecated and replaced with a ListDict that is returned by the emtf_tf_header method in processing.py |
See Issue #18. The TransferFunctionHeader object is not needed as we get this information from the mth5 now as dictionaries.
If we want to eliminate TransferFunctionHeader, we need to change the places where the code uses it to get that data from another object. The TransferFunction object would need to be able to provide:
Helpers in coding this:
rgreppy tf_header
yields:
rgreppy TransferFunctionHeader
yields:
The text was updated successfully, but these errors were encountered: