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.

Sign up for GitHub

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

Jump to bottom

Support arbitrary input/output dimensions #79

Open
tfarago opened this issue Mar 1, 2015 · 3 comments
Open

Support arbitrary input/output dimensions #79

tfarago opened this issue Mar 1, 2015 · 3 comments
Labels
enhancement low-prio question

Comments

@tfarago
Copy link
Contributor

tfarago commented Mar 1, 2015

The task from ufo-filters#66 doesn't care about the dimensionality of the input (it flattens the input). It would be useful to allow "arbitrary dimensionality" of a task, which would set its input/output dimensionality based on its predecessor.
@tfarago
Copy link
Contributor Author

tfarago commented Mar 3, 2015

I found this trick, @matze can I just use that?

@matze
Copy link
Contributor

matze commented Mar 3, 2015

I have to admit … I don't know 😳

@tfarago
Copy link
Contributor Author

tfarago commented Mar 3, 2015

Mathiaaaaaas... 😄 I wondered why I didn't find anything in the docs about it.

MarcusZuber pushed a commit that referenced this issue May 10, 2022
Fix #79: slice correct number of input items
231f1e7 
Before, only the first three-dimensional input item was processed correctly.
After that any more input was ignored. Returning FALSE on each process() causes
generate() to be called and resetting the current count solves the issue
completely.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement low-prio question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@matze @tfarago