Vincent Lostanlen
Vincent Lostanlen
Hm, i don't know. Then yes, a field for the algorithm is needed: (just like for `out_type`) Maybe refactor `scattering` this way? ```python def scattering(self, input, sc_algorithm): self.check_input(input) phi, psi...
@edouardoyallon ... help ? 🙏🏻
it's not clear to me why you'd want this to be an example and not a core module?
> Having this as an example is a good baby step; it motivates these discussion, maintainers get exposed to code that might be used for the feature, it teaches others...
yes. i confirm, i'm running into an installation with appdirs
not happy about those two missed lines. will address. also, will simplify swap (no need for is_complex)
@MuawizChaudhary i haven't started documentation. one thing that is relatively easy to do and would be nice to have would be to thoroughly audit which functions are public vs which...
This will cause a huge increase in memory footprint, and might break compatibility if whatever downstream application assumes that all coefficients have the same resolution. Unless you want to oversample?
> Since this codebase is primarily useful for research purposes, in general I think it would be nice to be able to tinker with the inner states of the system...