Skip to content
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

gdx, gdy, gdz are not exactly "space increments in estimation space" #94

Open
abukaj opened this issue Mar 27, 2019 · 0 comments
Open

Comments

@abukaj
Copy link
Member

abukaj commented Mar 27, 2019

According to:

kCSD-python/kcsd/KCSD.py

Lines 473 to 474 in 2ce755a

nx = (self.xmax - self.xmin)/self.gdx
self.estm_x = np.mgrid[self.xmin:self.xmax:np.complex(0, nx)]

kCSD-python/kcsd/KCSD.py

Lines 637 to 640 in 2ce755a

nx = (self.xmax - self.xmin)/self.gdx
ny = (self.ymax - self.ymin)/self.gdy
self.estm_pos = np.mgrid[self.xmin:self.xmax:np.complex(0, nx),
self.ymin:self.ymax:np.complex(0, ny)]

kCSD-python/kcsd/KCSD.py

Lines 929 to 935 in 2ce755a

nx = (self.xmax - self.xmin)/self.gdx
ny = (self.ymax - self.ymin)/self.gdy
nz = (self.zmax - self.zmin)/self.gdz
self.estm_pos = np.mgrid[self.xmin:self.xmax:np.complex(0, nx),
self.ymin:self.ymax:np.complex(0, ny),
self.zmin:self.zmax:np.complex(0, nz)]

the actual increments are (xmax - xmin) / (nx - 1) and so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant