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

How to do a initial test for 'Cleveland' problem #3

Open
BITcats opened this issue Jan 26, 2024 · 1 comment
Open

How to do a initial test for 'Cleveland' problem #3

BITcats opened this issue Jan 26, 2024 · 1 comment

Comments

@BITcats
Copy link

BITcats commented Jan 26, 2024

Thank for your outstanding works. I am currently working on utilizing your library to address the Cleveland problem, and I've encountered some challenges when I do a initial test for the 'Cleveland' problem with the code from the branch 'cleveland'. I was wondering if you could provide guidance on recommended methods for conducting initial tests on the Cleveland problem.

The two videos in the README provide some useful guidance. I attempted to make some modifications to the code, but I cannot guarantee if they are correct.

  • I replaced lines 23 and 24 in the 'cleveland14a-default-data.h' file with the following code:
static F l_[io::pp::nviews][io::ncoords2d_h];
static const F l_correct_[io::pp::nviews][io::ncoords2d_h];
  • I noticed that 'cleveland14a-default-data.hxx' lacks data about a free line. What can I do to fill it?
  • What additional tasks do I need to perform to ensure './minus-cleveland -g' can run correctly?
@h1063135843
Copy link

Same problem, why print_usage in minus-chicago and minus-cleveland output same content? Does it means both problem take 3 points and tangents as input? But it is said in paper that the cleveland problem handles with 3 points and 1 free line.

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

2 participants