-
Notifications
You must be signed in to change notification settings - Fork 54
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
FDataGrid.__call__
any (compatible) shape?
#562
Comments
Sorry, I have trouble understanding the proposed behaviour, can you show an example? |
For example, suppose you have
Is it a bit more understandable? It is essentially a situation I faced in implementing #561. |
For future reference in case we revisit, I make things more clear. The proposed version is that :
We can also discuss about the best position for |
So, I am toying with generalizing the functions in https://github.com/GAA-UAM/scikit-fda/tree/feature/ndfunction, and I am starting to modify the evaluation. What I want to achieve is:
This is a bit difficult to reason about, so I would appreciate any suggestions given all these constraints. |
So, for the aligned non-grid case (the easiest to reason about), we would have:
|
Now, the unaligned case has exactly the same out-shape, but It would have been great to be able to discern between aligned and unaligned from the shape of the evaluation points alone, without the need of an Also, in this proposed API there is no discussion about broadcasting at all. We should probably discuss if/when broadcasting should be allowed and how. |
Hi,
Currently,
FDataGrid.__call__
only takes shapes(n_samples, dim_domain)
or(dim_domain,)
(or()
whendim_domain == 1
). I think it would be natural to allow anyshape + (dim_domain,)
to allow for multiple dimension evaluation without going through the trouble of flattening before and unravelling after.What do you think?
Élie
The text was updated successfully, but these errors were encountered: