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

non-integer bit diameters cause a crash #2

Open
nathanielstenzel opened this issue Apr 3, 2017 · 2 comments
Open

non-integer bit diameters cause a crash #2

nathanielstenzel opened this issue Apr 3, 2017 · 2 comments
Labels

Comments

@nathanielstenzel
Copy link
Owner

A non-integer bit diameters cause a crash. See below.

DONE WITH RENDER
Traceback (most recent call last):
File "bucket_mill.py", line 988, in
bottom = where(filter_grid(bottom,min_value=(min_stl_zstl_detail),input_filter='nearby',size=(2+2bit_diameter)*stl_detail), bottom, do_not_cut)
File "bucket_mill.py", line 729, in filter_grid
mask = ones((size,size))
File "/usr/lib64/python2.7/site-packages/numpy/core/numeric.py", line 192, in ones
a = empty(shape, dtype, order)
TypeError: 'float' object cannot be interpreted as an index

@nathanielstenzel
Copy link
Owner Author

This is at least partially fixed now, but I am not sure if it is fixed in a proper way. There were a few spots of code where I tell it to just use the integer version of the bit diameter. This needs more testing.

@nathanielstenzel
Copy link
Owner Author

nathanielstenzel commented Apr 23, 2017

A final cut test showed movement at the max Y border when using a non-integer bit diameter. That movement looks like it is above Z=0. This should not be a problem unless the clamp is there.

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

No branches or pull requests

1 participant