You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when I get to the last line I get the following error:
"ERROR: BoundsError: attempt to access 141-element scale(interpolate(OffsetArray(::Array{Float64,1}, 0:142), BSpline(Cubic(Line(OnGrid())))), (-15.0:0.1:-1.0,)) with element type Float64 at index [-0.9980221350275645]"
which is coming from around here since zfinal=0.0 appears hardcoded.
Can be persuaded otherwise but it would be nice if we allowed arbitrary final redshift for the perturbations? I will continue using 0 for now since this is not a priority, but this is something to maybe come back to later.
The text was updated successfully, but these errors were encountered:
@jmsull, I can fix this! I wrote the current RECFAST to replicate the original version as closely as possible, in a way that is not very flexible. This is also related to fixing the differentiability of the RECFAST implementation. The steps would be
Crank up the precision, lower the stepsize, and try to find a high-accuracy representation of the solution that the RECFAST code is trying to solve for (it makes various different approximations in different epochs)
Rewrite the stepping that is currently done in the dynamic-step-size method that OrdinaryDiffEq.jl uses
Make sure that they converge to the same solutions
Lower the precision parameters to reach the same level of accuracy as RECFAST, but with the different method
If I run the following
when I get to the last line I get the following error:
"ERROR: BoundsError: attempt to access 141-element scale(interpolate(OffsetArray(::Array{Float64,1}, 0:142), BSpline(Cubic(Line(OnGrid())))), (-15.0:0.1:-1.0,)) with element type Float64 at index [-0.9980221350275645]"
which is coming from around here since zfinal=0.0 appears hardcoded.
Can be persuaded otherwise but it would be nice if we allowed arbitrary final redshift for the perturbations? I will continue using 0 for now since this is not a priority, but this is something to maybe come back to later.
The text was updated successfully, but these errors were encountered: