Anne Heimes
Anne Heimes
## problem currently it is failing because v3 is not allowed anymore. ## solution changing to v4 fixes the problem. I tested it on a local project.
replaces #838, a new branch needed to be created (and therefore a new PR) from develop, because the diffs were broken in a couple of PRs related to the BaseClass....
### Which issue(s) are closed by this pull request? Contributes #838 ### Changes proposed in this pull request: - replaced internal data handling in Coordinates with ``'_data'`` combining x,y,z and...
we discussed that we could move [pyfar.dsp.filter.fractional_octave_frequencies](https://pyfar.readthedocs.io/en/stable/modules/pyfar.dsp.filter.html#pyfar.dsp.filter.fractional_octave_frequencies) to constants and separate the nominal from the exact frequencies. for the nominal we could also include the standadized frequencies which came up...
> ## further ideas > One could also go further and define a abstract parent class for all pyfar classen, this class forces all childs to implement certain methods such...
[pyfar.utils.concatenate_channels](https://pyfar.readthedocs.io/en/develop/modules/pyfar.utils.html#pyfar.utils.concatenate_channels) does not support pyfar.Coordinates. Perhaps we could add support for this; the operation should be performed on the Cartesian coordinates and the weights, if not None.
This is an issue with accours if the ``weights`` are set and if the cshape of the coodinates object changes. ## Example ```python coordinates = Coordinates(1, 2, 3, weights=0.5) coordinates.x...
maybe we should discuss the history in a pr this time, because a lot of things happend in this release