-
Notifications
You must be signed in to change notification settings - Fork 20
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
detrend! fails with NodalData #54
Comments
Testing the fix now. I'm adding automated tests for all processing operations on NodalData (except ungap and merge, which are currently inapplicable). Since the structure has significant differences from SeisData and EventTraceData, I want to be sure that you don't run into problems further down the line. Incidentally, how do views of an Array{Float32, 2} (equivalently, Matrix{Float32}) behave on GPU with your package? |
Views work just the same as normal arrays but I believe they have to be contiguous. Views do not interact well with transposes or reshapes at the moment - JuliaGPU/Adapt.jl#21 |
Perfect. I'm pretty sure I have no transpose or reshape calls in SeisIO processing functions at the moment. Eventually, as your group gets further into nodal arrays, you'll be able to write NodalData processing methods into the submodule for two-dimensional FFTs on the underlying |
Fixed on dev |
Fixed on master and in the new release. Will close this issue as soon as Julia Registrator merges my PR(s). |
On the dev branch
with the test TDMS data
detrend!
failsI believe this is an issue with the definition of
dtr!
Using the
NodalData.x[i]
syntax returns aSubArray
type:but
dtr!
only acceptsArray
s. Changingdtr!
to acceptAbstractArray
asfunction dtr!(x::AbstractArray{T,1}, ti::Array{Int64,2}, fs::Float64, n::Int64) where T <: AbstractFloat
should fix this:works! Should be an easy change.
The text was updated successfully, but these errors were encountered: