utilities module
See original GitHub issueA module that houses utility functions useful for hypertools. Instead of attaching directly to the hypertools class, we could keep things organized by nesting these functions in a ‘utils’ module.
Proposed API:
import hypertools as hyp
x = some_data
missing_inds = hyp.utils.get_missing_indices(x)
Thoughts?
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
26 Utilities Module
Convenience method to create a list of parameters for SQL a query. ... Creates a database connection, execute SQL statements and query database...
Read more >Utilities — Python 3.11.1 documentation
The functions in this chapter perform various utility tasks, ranging from helping C code be more portable across platforms, using Python modules from...
Read more >Utilities modules - Ansible Documentation
... Glossary · Ansible Reference: Module Utilities · Special Variables · Red Hat Ansible Tower · Logging Ansible output. Roadmaps.
Read more >Python Utilities | Python Education - Google Developers
The *os* and *os.path* modules include many functions to interact with the file system. The *shutil* module can copy files.
Read more >Module:utilities - Wiktionary
This module exports various general utility functions, which can be used by other modules. pattern_escape. pattern_escape(text). Escapes the magic ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
i like this logic. so maybe we should only have one function –
plot
as the “deep” function, and everything else should go underutil
. e.g. using flags passed toplot
, we can have it align, center the data, reduce to different numbers of dimensions, etc.if the user wants to manipulate the data, they have to do that using
util
functions (e.g.util.reduce
,util.align
, etc.). but withinutil
, i think we should aim to have a flat organization, unless things start becoming very convoluted.my thinking, though, is that this toolbox as a whole should remain relatively light, focusing on plotting.
i could see the
reduce
module expanding out at some point, e.g. to support different data reduction algorithms (PCA, ICA, TFA, T-SNE, TDA, feature-extraction algorithms like LDA or LSA, etc.). or thealign
module could be expanded out (e.g. hyperalignment, ISFC, anatomical alignment, arbitrary other algorithms/functions). but then those would underutil.reduce
andutil.align
, respectively.(we can close this after the pull into master is complete)