"Both parts centered on X axis, Do i understand is correctly that both parts should be placed exactly on X and Y axis will be intersecting the gap between them, that means that parts will be facing each other by the side of size y? The first option is correct the distance will be reserve + lock_z. ![]() "In case of reserve > wall_thick, teeth will not render." Does it means that teeth wont render, but distance of boxes reserve + lock_z will still as it is, or is the box supposed to behave like if the lock_z = 0? See the text :“In case of it wont fit into corner with desire radius rad, the radius will be lowered to the smallest acceptable value.” How is the box supposed to look like when rad > x/2 or y/2 In case you will cheat, or you will not understand your own code, your classification will be -100 points, that means that you will get F. Based on quality of your code, you can gain 0 to 20 points. ![]() We use automatic test, which includes limit values of arguments. If you want to submit your task after proper deadline, make sure that your namespace on EDUX is blank, otherwise the classification will go throught, by the date of proper submission term. It is possible to consult and upload your task on EDUX however you want. Illnes or accident close to deadline will not push your deadline forward.Īfter classification (which will be after deadline), you cannot fix your task. In case of long term illnes, it is possible to setup special date. Late submission is possible to 23:59:27, late submission counts for half of the points. The archive must contains all the necessary files, (files containing your modules, or STL), generated STL files of your box doesnt belong to archive. It must be downloadable by this kind of link or Place link pointing to archive to you namespace. Name the file box.scad, achive it to root directory of box.zip and upload this archive to your personal namespace on EDUX. Any manipulation with $fn, $fs a $fa is also forbidden. It is forbidden to use any external libraries, including the MCAD library. Magical constants must be self explaining, or populated with comments. Repetitive code constructions must be implemented in it’s own modules and for-loops. The modul must have written so it could be used with use directive - It must not store any constants outside module.Įnsure that you keep given argument values! CodeĬode must be well written, it must be logically indented throught the whole file. Render to right place is crucial, because of automatic test. The bottom part of box shall be moved in positive direction of X axis, the top part of box to the opposite side. Ensure that you will keep the directions and dimensions x and y accordingly by the picture above (named logically). In case of to_print is true, both of the parts, will be rendered on their flat side, lying on on XY surface, both parts will sit on z=0, side by side centered on X axis, the space between them will be equal to print_space, this value is calculated between both outer walls of each box part, with it’s center in axis origins. ![]() The lid will be rendered on the top of box, it also needs to reflect the reserve argument. In case of to_print is false, the box must be placed to XY surface, the bottom of box must be at z=0 and centered so Z axix would go right through the middle of box. Module box(x=30, y=30, z1=10, z2=5, rad=15, wall_thick=2, lock_z=2, reserve=1.5, to_print=true, print_space=5)Įarlier undefined arguments affects place of the box in space
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |