2015-12-02 15:02 GMT+01:00 Parkinbot <

[hidden email]>:

> An approach like this is highly dependend on the problem.

>

> - How many students do you have?

> - How many different solutions will the problem have, if it is solved in a

> straight way? How probable is it to find the same solution (i.e. just naming

> differences allowed).

Actually, more than a few.

> - How many different solutions are syntactically equivalent (e.g. ordering

> of union-elements)

That's what I'm not sure.

> - How many different solutions are semantically equivalent (is problem

> completely characterized?)

It is.

> Up to 100 students: I'd recommend to just look at the codes for 10 minutes

> (6 secs each). With this you could exctract suspicious solutions for closer

> inspection, which would cost you another 20 minutes or so.

I've tried that, but I simply cannot hold that much information in my

head. It's slightly less than 100.

> Writing a "usable" software will cost you month!

That's why I just try to use what's already available.

> And how would you validate

> it?

I would inspect the code manually, after I find similarities in the

CSG tree. Than I would get the students to explain to me why they did

this and that, and to change the module to act differently, etc.

Thanks for all the feedback.

_______________________________________________

OpenSCAD mailing list

[hidden email]
http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org