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.

Sign up for GitHub

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

Jump to bottom

Questions. #2

Open
xuyonglai opened this issue Nov 11, 2020 · 2 comments
Open

Questions. #2

xuyonglai opened this issue Nov 11, 2020 · 2 comments

Comments

@xuyonglai
Copy link

Bonjour
I have two questions.

  • In paper , "each iteration starts with a previous solution (initialized with h0 = z) and a set of surfaces to flatten".However, In code, h0 were initialized 0.
    image
    That is to say, before the first optimize, all h var are 0. I do not understand this.

  • If the support stucture are printed ahead , curvislicer can handle with situation that the model bottom are not flat. Right?
@JinOuYongGu
Copy link

I have edited the code and it can handle the situation that the model bottom are not flat. You can see my fork of it.
You need edit only 1 line in main.cpp:
else if (normals[s][2] < 0 || normals[s][2] > 0.97)
edit it to
else

normals[s][2] > 0.97 means that the bottom surface that parallel enougth to print bed. Just remove it and you can see the bottom surfaces can be deformed.

@xuyonglai
Copy link
Author

I have edited the code and it can handle the situation that the model bottom are not flat. You can see my fork of it.
You need edit only 1 line in main.cpp:
else if (normals[s][2] < 0 || normals[s][2] > 0.97)
edit it to
else

normals[s][2] > 0.97 means that the bottom surface that parallel enougth to print bed. Just remove it and you can see the bottom surfaces can be deformed.

I got it. Thank you very much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@JinOuYongGu @xuyonglai