[ENH]: Rename 'table' to 'vector' in storage API #181
No reviewers
Labels
No labels
CRITICAL
Stale
WIP
bug
concept
coordinate
dataset
dependencies
documentation
duplicate
enhancement
github_actions
good first issue
help wanted
invalid
maintenance
maps
marker
mask
on hold
parcellation
preprocess
question
ready
storage
template-space
triage
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
juaml/junifer!181
Loading…
Reference in a new issue
No description provided.
Delete branch "refactor/storage/table-to-vector"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Are you requiring a new dataset or marker?
Which feature do you want to include?
Currently we support:
We are using "tables" to store "vectors". That is, 1 dimentional arrays. However, we have a whole logic set to allow for tables with different number of rows per element, as in timeseries. This does not make any sense. We should support:
How do you imagine this integrated in junifer?
row_col_namesfromstore_vectorextra:
be consistent with
col_namesandrow_names. Currently timeseries and vectors will have acolumnsparameter, while matrix hascol_namesandrow_namesDo you have a sample code that implements this outside of junifer?
No response
Anything else to say?
No response
Codecov Report
100.00% <ø> (ø)93.48% <91.30%> (-0.02%)?Flags with carried forward coverage won't be shown. Click here to find out more.
100.00% <ø> (ø)100.00% <ø> (ø)100.00% <ø> (ø)92.00% <ø> (ø)92.30% <ø> (ø)81.81% <80.00%> (ø)94.53% <80.00%> (ø)95.55% <90.00%> (-1.75%)95.00% <100.00%> (ø)100.00% <100.00%> (ø)