search

SBFRF / scaleCinterp_python

Interpolation codes from Plant et al 2002
0 stars 0 forks source link

weights from scaleCinterp are wrong #1

Open SBFRF opened 6 years ago

SBFRF commented 6 years ago

the weights that are output from ScaleC function do not lineup with those data from matlab for the same time period. These weights, output from the python version, do not tail down nicely as they move from the new data domain as expected. This thereby affects the bSpline and integration of the bathy to the background.

@dyoung8 created a work around is in place at this point in which the bathy perturbations are forced 'artificially' to zero to work around this issue.

@dyoung8 am i missing anything?

possible solutions: check a diff between original code and current fork, to look for problems, maybe the problem was created by me?

dyoung8 commented 6 years ago

I think that sums it up...

David L. Young, Ph.D. Research Civil Engineer Coastal and Hydraulics Laboratory (CHL) US Army Engineer Research and Development Center (ERDC) 1261 Duck Rd., Duck, NC 27949 Email: David.L.Young@erdc.dren.mil Phone: (252) 261-6840 x225

From: Spicer Bak [notifications@github.com] Sent: Tuesday, November 28, 2017 4:44 PM To: SBFRF/scaleCinterp_python Cc: Young, David L ERDC-RDE-CHL-MS CIV; Mention Subject: [SBFRF/scaleCinterp_python] weights from scaleCinterp are wrong (#1)

the weights that are output from ScaleC function do not lineup with those data from matlab for the same time period. These weights, output from the python version, do not tail down nicely as they move from the new data domain as expected. This thereby affects the bSpline and integration of the bathy to the background.

@dyoung8 created a work around is in place at this point in which the bathy perturbations are forced 'artificially' to zero to work around this issue.

@dyoung8 am i missing anything?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.