Change Details

What if tomorrow thousands of people contribute and model diy parts for the axiom with the Github repository? This could change the industry. I already see a lot of people uploading lens adapters, caps, extension tubes on 3D sharing platforms. I have used svn for years with large assemblies for the building industry (see [[ http://www.readcube.com/articles/10.1002%2Fad.1705?r3_referer=wol&tracking_action=preview_click&show_checkout=1&purchase_referrer=onlinelibrary.wiley.com&purchase_site_license=LICENSE_DENIED_NO_CUSTOMER | link ]]) , although im quite new and already quite in love with GitHub. Here are the tricks I have learned with Building information Modeling, things that might make it easier to collaborate with a large number of people. - We need a common disposition of parts across all platforms. For that we need an origin XYZ, and I believe we also need a ref plane for the image sensor. {F982} We could also create a map, with the current/atwork assembly always position with the microzed lower corner on the origin, and then additional parts in the corresponding region, like in the picture. That way it is like having a big table with all the parts to make the camera you want. {F981} I can upload .3dm, .obj, .CATpart, .Iges, .stp files with the same origin reference. - Then comes naming convention. I will suggest a formatting like this : AXM_BET_KUB_V02_100515_PC2 For example, here we are looking at the PCB n°2, in the Kubrick II (if we stick with directors name), at a file that was created on the 10th of May 2015. That way, we can classify easily the information, and even if its a bit tedious to name or read, it might be worth it. Please let me know what you think of this. and lets try to make a 3D collaboration system that can branch off in a network of projects!

What if tomorrow thousands of people contribute and model diy parts for the axiom with the Github repository? This could change the industry. I already see a lot of people uploading lens adapters, caps, extension tubes on 3D sharing platforms. I have used svn for years with large assemblies for the building industry, although i am quite new and already quite in love with GitHub, i think maybe we can exchange a few methods, and discuss on how to organize the information and the models. Here are the tricks I have learned, things that might make it easier to collaborate with a large number of people. - We need a common disposition of parts across all platforms. For that we need an origin XYZ, and I believe we also need a ref plane for the image sensor. {F982} We could also create a map, with the current/atwork assembly always position with the microzed lower corner on the origin, and then additional parts in the corresponding region, like in the picture. That way it is like having a big table with all the parts to make the camera you want. the only thing you need is a translated value in X, Y and Z associated with the part. {F981} I can upload .3dm, .obj, .CATpart, .Iges, .stp files with the same origin reference. they could be linked to a disclaimer for contributors. - Then comes naming convention. formatting could look like this : AXM_BET_KUB_V02_100515_PC2 For example, here we are looking at the PCB n°2, in the Kubrick II (if we stick with directors name), at a file that was created on the 10th of May 2015. That way, we can classify easily the information. ex : AXM_BET_ALT_V03_100515_MCZ Please let me know what you think of this. and lets try to make a 3D collaboration system that can branch off in a network of projects! I dont know if it is possible to establish these standards in an open source community, but that could really be beneficial for new comers, and archive.

What if tomorrow thousands of people contribute and model diy parts for the axiom with the Github repository? This could change the industry. I already see a lot of people uploading lens adapters, caps, extension tubes on 3D sharing platforms. I have used svn for years with large assemblies for the building industry (see [[ http://www.readcube.com/articles/10.1002%2Fad.1705?r3_referer=wol&tracking_action=preview_click&show_checkout=1&purchase_referrer=onlinelibrary.wiley.com&purchase_site_license=LICENSE_DENIED_NO_CUSTOMER | link ]]) , although i am quite new and already quite in love with GitHub, i think maybe we can exchange a few methods, although im quite new and already quitand discuss on how to organize the in love with GitHubformation and the models. Here are the tricks I have learned with Building information Modeling, things that might make it easier to collaborate with a large number of people. - We need a common disposition of parts across all platforms. For that we need an origin XYZ, and I believe we also need a ref plane for the image sensor. {F982} We could also create a map, with the current/atwork assembly always position with the microzed lower corner on the origin, and then additional parts in the corresponding region, like in the picture. That way it is like having a big table with all the parts to make the camera you want. the only thing you need is a translated value in X, Y and Z associated with the part. {F981} I can upload .3dm, .obj, .CATpart, .Iges, .stp files with the same origin reference. they could be linked to a disclaimer for contributors. - Then comes naming convention. I will suggest a formattingformatting could look like this : AXM_BET_KUB_V02_100515_PC2 For example, here we are looking at the PCB n°2, in the Kubrick II (if we stick with directors name), at a file that was created on the 10th of May 2015. That way, we can classify easily the information. That way, we can classify easily the information, and even if its a bit tedious to name or read, it might be worth it.ex : AXM_BET_ALT_V03_100515_MCZ Please let me know what you think of this. and lets try to make a 3D collaboration system that can branch off in a network of projects! I dont know if it is possible to establish these standards in an open source community, but that could really be beneficial for new comers, and archive.