Difference between revisions of "Google Summer of Code/Project Ideas"
(added BRL-CAD core C++ interface) |
|||
(107 intermediate revisions by 34 users not shown) | |||
Line 1: | Line 1: | ||
If you want to work on '''computer-aided design (CAD), geometry, or graphics''', you've come to the right place! Help us improve open source CAD. | If you want to work on '''computer-aided design (CAD), geometry, or graphics''', you've come to the right place! Help us improve open source CAD. | ||
− | Well prepared proposals have an ''outstanding'' chance | + | Well prepared proposals from capable students have an ''outstanding'' chance of getting selected. We consider proposals for all skill levels ranging from simple to crazy hard and everything in between. [https://lists.sourceforge.net/lists/listinfo/brlcad-devel Introduce yourself], and we'll help you plan one right for you. |
− | + | Remember that project descriptions are just ''initial ideas''. You must expand with [[Summer_of_Code/Application_Guidelines|considerably more detail]]. Change the goals to fit your experience and interests. See our '''[[Summer_of_Code/Checklist|checklist]]''' to get started. | |
− | + | This year, BRL-CAD is coordinating with five other communities that will get 1-2 students each to help bridge our work and encourage collaboration. Projects that help exchange data or share code are desired! | |
− | + | ||
− | + | {|- | |
− | + | |align="center" width="15%"|[http://brlcad.org/w/index.php?title=Google_Summer_of_Code/Project_Ideas#OpenSCAD_Projects http://www.openscad.org/assets/img/logo.png] | |
− | {| | + | |align="center" width="15%"|[http://brlcad.org/w/index.php?title=Google_Summer_of_Code/Project_Ideas#Slic3r_Projects https://raw.githubusercontent.com/alexrj/Slic3r/master/var/Slic3r_128px.png] |
− | |align="center" width=" | + | |align="center" width="15%"|[http://brlcad.org/w/index.php?title=Google_Summer_of_Code/Project_Ideas#LibreCAD_Projects https://librecad.org/img/logo.png] |
− | |align="center" width=" | ||
− | |align="center" width=" | ||
|- | |- | ||
|align="center"|'''OpenSCAD''': rich syntax, programmable geometry. Lots of possibilities to make it interoperate with BRL-CAD and LibreCAD. | |align="center"|'''OpenSCAD''': rich syntax, programmable geometry. Lots of possibilities to make it interoperate with BRL-CAD and LibreCAD. | ||
+ | |align="center"|'''Slic3r''': toolpath/G-code generator for 3D printers. | ||
|align="center"|'''LibreCAD''': specializes in 2D CAD modeling, drafting, drawings. Help build a bridge to BRL-CAD or add STEP support. | |align="center"|'''LibreCAD''': specializes in 2D CAD modeling, drafting, drawings. Help build a bridge to BRL-CAD or add STEP support. | ||
− | |align="center"|''' | + | |- |
+ | |align="center" width="15%"|[http://brlcad.org/w/index.php?title=Google_Summer_of_Code/Project_Ideas#BRL-CAD_Projects http://brlcad.org/images/logo/BRL-CAD_gear3d_logo_164.png] | ||
+ | |align="center" width="15%"|[http://brlcad.org/w/index.php?title=Google_Summer_of_Code/Project_Ideas#FreeCAD_Projects http://www.freecadweb.org/images/logo.png] | ||
+ | |- | ||
+ | |align="center"|'''BRL-CAD''': 3D solid modeling, geometry processing, and robust high-performance ray tracing. Help us make a better CAD system. | ||
+ | |align="center"|'''FreeCAD''': parametric 3D modelling with strong Python interface and general engineering functionality like FEM and CAM | ||
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
'''Project titles link to a page with more details.''' | '''Project titles link to a page with more details.''' | ||
= BRL-CAD Projects = | = BRL-CAD Projects = | ||
+ | == High Priority Topics == | ||
+ | This year, we are most interested in topics that will immediately benefit BRL-CAD users. Please align your proposal with one of the following three focus areas. Talk with us at http://brlcad.zulipchat.com | ||
+ | |||
+ | {| bgcolor=#fff width=100% | ||
+ | |- | ||
+ | |align=center width=20% bgcolor=#e22|'''Performance''' | ||
+ | |bgcolor=#aaa|Faster geometry. In order, ideas like'''[[Coherent Raytracing]]''', anything involving OpenCL, parallelizing serial code, and eliminating LIBBU pointer aliasing. | ||
+ | |- | ||
+ | |align=center width=20% bgcolor=#2e2|'''User Interface''' | ||
+ | |bgcolor=#ccc|Build on Google Code-In progress (OpenSCAD-style GUI), [[Convert MGED from Tk to Qt]], revamp our [[Overlap tool]] GUI, etc. Qt and ray tracing are fair game. | ||
+ | |- | ||
+ | |align=center width=20% bgcolor=#22e|'''Core Infrastructure''' | ||
+ | |bgcolor=#aaa|Integrate appleseed rendering, extend and deploy Online Geometry Viewer (OGV), expand our geometry conversion (GCV) library. | ||
+ | |} | ||
== Web Development == | == Web Development == | ||
Line 34: | Line 48: | ||
!align=center|Difficulty | !align=center|Difficulty | ||
!align=center|Contacts | !align=center|Contacts | ||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
|width=62%|'''[[Synchronize Wiki with Docbook]]:''' We use Docbook for most of our user documentation but find editing a wiki page much easier to use. Set up a system so the two are always in sync. | |width=62%|'''[[Synchronize Wiki with Docbook]]:''' We use Docbook for most of our user documentation but find editing a wiki page much easier to use. Set up a system so the two are always in sync. | ||
Line 44: | Line 53: | ||
|align=center|MEDIUM | |align=center|MEDIUM | ||
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Yapp]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Yapp]] | ||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
|width=62%|'''[[Online Geometry Viewer Back-end]]:''' Continuation of existing work, improve our interface for viewing geometry online. Focus on the back-end infrastructure. | |width=62%|'''[[Online Geometry Viewer Back-end]]:''' Continuation of existing work, improve our interface for viewing geometry online. Focus on the back-end infrastructure. | ||
− | | | + | |C++, Javascript, Meteor.js, Three.js |
− | |align=center| | + | |align=center|Medium |
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]],[[Google_Summer_of_Code/Project_Ideas#Mentors|Pooh]], [[Google_Summer_of_Code/Project_Ideas#Mentors|Panda]] |
|- | |- | ||
|width=62%|'''[[Mediawiki 3D Geometry Extension]]:''' Write an extension for Mediawiki that will visualize our .g files. Maybe leverage LLVM C->Javascript translation. | |width=62%|'''[[Mediawiki 3D Geometry Extension]]:''' Write an extension for Mediawiki that will visualize our .g files. Maybe leverage LLVM C->Javascript translation. | ||
Line 59: | Line 63: | ||
|align=center|HARD | |align=center|HARD | ||
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] | ||
− | |||
− | |||
− | |||
− | |||
− | |||
|} | |} | ||
− | |||
== Geometry == | == Geometry == | ||
Line 75: | Line 73: | ||
!align=center|Contacts | !align=center|Contacts | ||
|- | |- | ||
− | |align=left width=62%|'''[[NURBS | + | |align=left width=62%|'''[[Plate Mode NURBS raytracing]]:''' Imported NURBS geometry often does NOT enclose space (i.e., not solid), so add support for specifying an implicit thickness. |
− | |align=center|C/ | + | |align=center|C/C++ |
− | |align=center| | + | |align=center|HARD |
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] |
|- | |- | ||
|width=62%|'''[[Overlap tool]]:''' Resolving geometric interferences (aka overlaps) is a common geometry editing activity. Design an awesome GUI for resolving conflicts. | |width=62%|'''[[Overlap tool]]:''' Resolving geometric interferences (aka overlaps) is a common geometry editing activity. Design an awesome GUI for resolving conflicts. | ||
Line 84: | Line 82: | ||
|align=center|EASY | |align=center|EASY | ||
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Yapp, Morrison, Greenwald]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Yapp, Morrison, Greenwald]] | ||
+ | |- | ||
+ | |align=left width=62%|'''[[NURBS Editing Support]]:''' BRL-CAD doesn't currently have good support for editing NURBS primitives. Fix that. | ||
+ | |align=center|C/Tcl | ||
+ | |align=center|MEDIUM | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Yapp]] | ||
|- | |- | ||
|align=left width=62%|'''[[Vector Drawings from NURBS]]:''' Huge impact here if you can update one or more of our raytracers to provide vector output instead of raster. Perhaps render directly to PDF or SVG. | |align=left width=62%|'''[[Vector Drawings from NURBS]]:''' Huge impact here if you can update one or more of our raytracers to provide vector output instead of raster. Perhaps render directly to PDF or SVG. | ||
Line 95: | Line 98: | ||
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison, Rossberg]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison, Rossberg]] | ||
|- | |- | ||
− | |width=62%|'''[[ | + | |width=62%|'''[[Geometry Conversion Library]]:''' Probably our biggest open source asset is our extensive collection of importers and exporters. Turn them all into a universal conversion library. |
|align=center|C/C++ | |align=center|C/C++ | ||
|align=center|EASY | |align=center|EASY | ||
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Greenwald, Morrison, Rossberg]] |
|- | |- | ||
− | | | + | |width=62%|'''[[STEP importer improvements]]:''' We have an importer, but it's preliminary. Add support for importing hierarchy information, polygonal geometry, and implicit geometry. |
|align=center|C/C++ | |align=center|C/C++ | ||
− | |align=center| | + | |align=center|MEDIUM |
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Yapp]] |
|- | |- | ||
|width=62%|'''[[STEP exporter]]:''' We have an importer, we need a comprehensive exporter with support for implicit CSG, NURBS, or polygonal mesh geometry. | |width=62%|'''[[STEP exporter]]:''' We have an importer, we need a comprehensive exporter with support for implicit CSG, NURBS, or polygonal mesh geometry. | ||
Line 109: | Line 112: | ||
|align=center|EASY | |align=center|EASY | ||
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Yapp, Morrison]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Yapp, Morrison]] | ||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
|width=62%|'''[[Convert BoT to Pipe]]:''' Command line interface to convert facetted fluid/electrical line geometry into BRL-CAD native pipe solids. | |width=62%|'''[[Convert BoT to Pipe]]:''' Command line interface to convert facetted fluid/electrical line geometry into BRL-CAD native pipe solids. | ||
|align=center|C/C++/Tcl | |align=center|C/C++/Tcl | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|align=center|MEDIUM | |align=center|MEDIUM | ||
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] | ||
Line 155: | Line 128: | ||
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] | ||
|- | |- | ||
− | |width=62%|'''[[Python Geometry]]:''' Wrap BRL-CAD's primitives in Python, make it easier to script geometry creation. | + | |width=62%|'''[[Python Geometry]]:''' Wrap BRL-CAD's primitives in Python (or Lua), make it easier to script geometry creation. |
− | |align=center|Python | + | |align=center|Python/Lua |
|align=center|Easy | |align=center|Easy | ||
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] | ||
|} | |} | ||
− | |||
== Performance & Quality == | == Performance & Quality == | ||
Line 170: | Line 142: | ||
!align=center|Contacts | !align=center|Contacts | ||
|- | |- | ||
− | |align=left width=62%|'''[[ | + | |align=left width=62%|'''[[Coherent Raytracing]]:''' Our current raytrace pipeline dispatches and processes one ray at a time. Send bundles and convert the pipeline into phases. |
|align=center|C/C++ | |align=center|C/C++ | ||
|align=center|MEDIUM | |align=center|MEDIUM | ||
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison, Rossberg]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison, Rossberg]] | ||
|- | |- | ||
− | |align=left width=62%|'''[[ | + | |align=left width=62%|'''[[OpenCL GPGPU Raytracing]]:''' We have about a dozen simple primitives that need to have a ray-object intersection function converted from C to OpenCL. |
− | |align=center|C/ | + | |align=center|C/OpenCL |
+ | |align=center|EASY | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] | ||
+ | |- | ||
+ | |align=left width=62%|'''[[OpenCL GPGPU Complex Raytracing]]:''' We have about half a dozen complex primitives that need to have a ray-object intersection function converted from C to OpenCL. | ||
+ | |align=center|C/OpenCL | ||
|align=center|MEDIUM | |align=center|MEDIUM | ||
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] |
+ | |- | ||
+ | |align=left width=62%|'''[[OpenCL GPGPU Spatial Partitioning Raytracing]]:''' We use a Bounding Volume Hierarchy (BVH) to reduce the amount of intersections we need to compute to render an image. We need to replace this with a Kd-tree in order to be able to early terminate a render in models with high depth complexity. This should speed up render speed significantly for those models (e.g. Goliath). | ||
+ | |align=center|C/OpenCL | ||
+ | |align=center|HARD | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] | ||
+ | |- | ||
+ | |align=left width=62%|'''[[OpenCL GPGPU Brep Raytracing]]:''' We need to support Brep NURBS raytracing over the GPU. There is example CPU only code. Execution on the GPU should significantly enhance rendering performance of these primitives. | ||
+ | |align=center|C/OpenCL | ||
+ | |align=center|HARD | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] | ||
|- | |- | ||
|align=left width=62%|'''[[NURBS Booleans]]:''' We have NURBS surface-surface intersections working. Now we're using them to create evaluated forms of our CSG geometry. Make it more robust and faster. | |align=left width=62%|'''[[NURBS Booleans]]:''' We have NURBS surface-surface intersections working. Now we're using them to create evaluated forms of our CSG geometry. Make it more robust and faster. | ||
Line 185: | Line 172: | ||
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Yapp, Rossberg]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Yapp, Rossberg]] | ||
|- | |- | ||
− | |align=left width=62%|'''[[NURBS Optimization and Cleanup]]:''' We have a fantastic implementation of NURBS evaluation but haven't gone back to clean up or speed it up. Make it | + | |align=left width=62%|'''[[NURBS Optimization and Cleanup]]:''' We have a fantastic implementation of NURBS evaluation but haven't gone back to clean up or speed it up. Make it pretty and fast. |
|align=center|C/C++ | |align=center|C/C++ | ||
|align=center|MEDIUM | |align=center|MEDIUM | ||
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Yapp, Morrison]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Yapp, Morrison]] | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
|width=62%|'''[[Space Partitioning for Tessellation]]:''' Technically an optimization task, make our geometry converters run an order of magnitude faster by using spatial partitioning during tessellation. | |width=62%|'''[[Space Partitioning for Tessellation]]:''' Technically an optimization task, make our geometry converters run an order of magnitude faster by using spatial partitioning during tessellation. | ||
Line 210: | Line 182: | ||
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Greenwald, Yapp, Morrison]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Greenwald, Yapp, Morrison]] | ||
|- | |- | ||
− | |width=62%|'''[[ | + | |width=62%|'''[[Faster Overlap Detection]]:''' BRL-CAD has a 'gqa' tool that detects overlaps. Implement a replacement using a better approach. |
|align=center|C | |align=center|C | ||
− | |align=center| | + | |align=center|MEDIUM |
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Greenwald, Morrison]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Greenwald, Morrison]] | ||
|} | |} | ||
Line 233: | Line 205: | ||
|align=center|EASY | |align=center|EASY | ||
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison, Yapp]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison, Yapp]] | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
|width=62%|'''[[General Tree Walker]]:''' We have a half dozen or more functions that will traverse a geometry hierarchy in different ways. There only needs to be one. | |width=62%|'''[[General Tree Walker]]:''' We have a half dozen or more functions that will traverse a geometry hierarchy in different ways. There only needs to be one. | ||
Line 253: | Line 210: | ||
|align=center|EASY | |align=center|EASY | ||
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Greenwald, Yapp, Morrison]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Greenwald, Yapp, Morrison]] | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
|width=62%|'''[[GED Transactions]]:''' Migrating functionality from our MGED geometry editor into our LIBGED library provided excellent code reuse, but now we need transactions so that actions can be undone. | |width=62%|'''[[GED Transactions]]:''' Migrating functionality from our MGED geometry editor into our LIBGED library provided excellent code reuse, but now we need transactions so that actions can be undone. | ||
|align=center|C | |align=center|C | ||
|align=center|EASY | |align=center|EASY | ||
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison, Daga]] |
|- | |- | ||
|width=62%|'''[[Add exec option to search]]:''' Our LIBGED library provides a ''search'' command very similar to the UNIX ''find'' command for scanning through geometry. Implement the -exec option. | |width=62%|'''[[Add exec option to search]]:''' Our LIBGED library provides a ''search'' command very similar to the UNIX ''find'' command for scanning through geometry. Implement the -exec option. | ||
|align=center|C | |align=center|C | ||
|align=center|EASY | |align=center|EASY | ||
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Yapp | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Yapp, Daga]] |
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
|width=62%|'''[[Astronomical units]]:''' We already go "big", but accurately modeling at a galactic scale redefines that notion... | |width=62%|'''[[Astronomical units]]:''' We already go "big", but accurately modeling at a galactic scale redefines that notion... | ||
|align=center|C | |align=center|C | ||
|align=center|EASY | |align=center|EASY | ||
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison, Greenwald]] | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison, Greenwald, Daga]] |
|- | |- | ||
− | |width=62%|'''[[Object-oriented interfaces| | + | |width=62%|'''[[Object-oriented interfaces|Object-oriented C++ Geometry API]]:''' Extend our C++ library which provides a simple interface to BRL-CAD's core functionality. Kickstart start a new geometry kernel. |
|align=center|C++ | |align=center|C++ | ||
|align=center|MEDIUM | |align=center|MEDIUM | ||
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Rossberg]] | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Rossberg, Kamga]] |
+ | |- | ||
+ | |width=62%|'''[[Point Clouds]]:''' BRL-CAD has a basic point cloud primitive. Beef it up, make it faster, maybe integrate with the Point Cloud Library (PCL) for evaluation. | ||
+ | |align=center|C/C++ | ||
+ | |align=center|MEDIUM | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Browder, Kamga]] | ||
|- | |- | ||
− | |width=62%|'''[[ | + | |width=62%|'''[[Annotations]]:''' Implement support for 2D annotations, labels that can be added to geometry. |
− | |align=center| | + | |align=center|Perl |
− | |align=center| | + | |align=center|EASY |
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Browder]] |
|} | |} | ||
Line 303: | Line 250: | ||
!align=center|Contacts | !align=center|Contacts | ||
|- | |- | ||
− | |width=62%|'''[[ | + | |width=62%|'''[[Appleseed renderer integration]]:''' Appleseed is rendering infrastructure used by the film industry to make pretty pictures. Make it shoot rays at our native geometry with our ray trace library. |
|align=center|C | |align=center|C | ||
− | |align=center| | + | |align=center|MEDIUM |
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] |
|- | |- | ||
|width=62%|'''[[Material and Shader Objects]]:''' This one is a biggie but easy. Implement new object entities for describing shaders and material properties, use them during ray tracing. | |width=62%|'''[[Material and Shader Objects]]:''' This one is a biggie but easy. Implement new object entities for describing shaders and material properties, use them during ray tracing. | ||
Line 312: | Line 259: | ||
|align=center|EASY | |align=center|EASY | ||
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] | ||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
|width=62%|'''[[Generalized abstracted spacial partitioning capability]]:''' Need more be said? If you're familiar with BSPs, KD trees, and grid structures, then this one is for you. | |width=62%|'''[[Generalized abstracted spacial partitioning capability]]:''' Need more be said? If you're familiar with BSPs, KD trees, and grid structures, then this one is for you. | ||
Line 337: | Line 279: | ||
|align=center|MEDIUM | |align=center|MEDIUM | ||
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Greenwald]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Greenwald]] | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
|width=62%|'''[[Density functions]]:''' Accurately represent everything from atmosphere to bone. Implement support for parametric density functions for homogenous materials. | |width=62%|'''[[Density functions]]:''' Accurately represent everything from atmosphere to bone. Implement support for parametric density functions for homogenous materials. | ||
Line 359: | Line 291: | ||
|} | |} | ||
− | + | Open Channel For Goods Using Optics +robotics concept: | |
− | + | We can Create A Tunnel Like way Where we can transport goods like We Transport data through seas Using Optics. Only Need Is To make it automated with perfect coding for destination. We can Do this with the help of Software+Mechanical Engineers. Where coding and assembly plays important role.. | |
− | + | Coding can Be Done In General By C/c++ language which is Simpler | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
= OpenSCAD Projects = | = OpenSCAD Projects = | ||
Line 379: | Line 305: | ||
!align=center|Contacts | !align=center|Contacts | ||
|- | |- | ||
− | |align=left width=62%|'''[https://github.com/openscad/openscad/wiki/ | + | |align=left width=62%|'''[https://github.com/openscad/openscad/wiki/Project%3A-Improve-DXF-import-and-export Improve DXF Import and Export]:''' Look into using an external library for DXF import (and export?). |
|align=center|C++ | |align=center|C++ | ||
− | |align=center| | + | |align=center|MEDIUM |
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Marius]] | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Marius/Torsten]] |
|- | |- | ||
− | |align=left width=62%|'''[https://github.com/openscad/openscad/wiki/Ideas | + | |align=left width=62%|'''[https://github.com/openscad/openscad/wiki/Ideas-for-Development-Tasks#openscad-standard-library OpenSCAD Standard Library]:''' Create a standard user-space OpenSCAD library. |
− | |align=center| | + | |align=center|OpenSCAD |
− | |align=center| | + | |align=center|MEDIUM |
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Marius]] | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Marius/Torsten]] |
|- | |- | ||
− | |align=left width=62%|'''[https://github.com/openscad/openscad/wiki/ | + | |align=left width=62%|'''[https://github.com/openscad/openscad/wiki/Project%3A-Improve-OpenGL-rendering OpenGL framework]:''' Rewrite the OpenGL rendering code to use a rendering framework. Focus on compatibility with OpenGL ES2 and rendering performance. |
− | |align=center|C++ | + | |align=center|C++ OpenGL |
− | |align=center| | + | |align=center|MEDIUM |
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Marius | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Marius/Torsten]] |
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
− | |align=left width=62%|'''[https://github.com/openscad/openscad/wiki/ | + | |align=left width=62%|'''[https://github.com/openscad/openscad/wiki/Project%3A-Improve-Text-Editor Improve Text Editor]:''' Add more IDE style features to the text editor integrated in OpenSCAD. |
|align=center|C++ | |align=center|C++ | ||
− | |||
− | |||
− | |||
− | |||
− | |||
|align=center|MEDIUM | |align=center|MEDIUM | ||
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Marius]] | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Marius/Torsten]] |
|- | |- | ||
− | |align=left width=62%|'''[https://github.com/openscad/openscad/wiki/Ideas | + | |align=left width=62%|'''[https://github.com/openscad/openscad/wiki/Ideas-for-Development-Tasks#persistant-caching Persistent Caching]:''' Implement a disk-based version of the internal memory caches |
|align=center|C++ | |align=center|C++ | ||
|align=center|MEDIUM | |align=center|MEDIUM | ||
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Marius]] | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Marius/Torsten]] |
|- | |- | ||
− | |align=left width=62%|'''[https://github.com/openscad/openscad/wiki/ | + | |align=left width=62%|'''[https://github.com/openscad/openscad/wiki/Project%3A-Multi-threaded-geometry-rendering Multi-threaded Geometry Evaluation]:''' Implement multi-threaded evaluation of geometry. |
|align=center|C++ | |align=center|C++ | ||
|align=center|MEDIUM | |align=center|MEDIUM | ||
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Marius]] | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Marius/Torsten]] |
|- | |- | ||
− | |align=left width=62%|'''[https://github.com/openscad/openscad/wiki/ | + | |align=left width=62%|'''[https://github.com/openscad/openscad/wiki/Project%3A-Survey-of-CSG-algorithms Survey of CSG algorithms]:''' Review existing research, evaluate and prototype algorithms. |
− | |align=center| | + | |align=center|C++ |
− | |align=center|MEDIUM | + | |align=center|MEDIUM-HARD |
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Marius]] | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Marius/Torsten]] |
|- | |- | ||
− | |align=left width=62%|'''[https://github.com/openscad/openscad/wiki/ | + | |align=left width=62%|'''[https://github.com/openscad/openscad/wiki/Project%3A-Add-support-for-exporting-models-in-STEP-format Add support for exporting models in STEP format]:''' Enable better integration with other CAD tools by adding STEP export. |
|align=center|C++ | |align=center|C++ | ||
|align=center|HARD | |align=center|HARD | ||
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Marius]] | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Marius/Torsten]] |
+ | |- | ||
+ | |align=left width=62%|'''[https://github.com/openscad/openscad/wiki/Ideas-for-Development-Tasks#issue-handling Issue Handling]:''' Day-to day issue and community management, fix incoming and existing issues. Good place to get started. | ||
+ | |align=center|C++ | ||
+ | |align=center|EASY | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Marius/Torsten]] | ||
+ | |- | ||
+ | |align=left width=62%|'''[https://github.com/openscad/openscad/wiki/Ideas-for-Development-Tasks#test-framework-improvements Test Framework Improvements]:''' Improve tests and test framework. Good place to get started. | ||
+ | |align=center|Python, C++ | ||
+ | |align=center|EASY-MEDIUM | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Marius/Torsten]] | ||
+ | |- | ||
+ | |align=left width=62%|'''[https://github.com/openscad/openscad/wiki/Ideas-for-Development-Tasks#svg-import SVG Import]:''' Improve/finalize SVG import. | ||
+ | |align=center|C++, SVG | ||
+ | |align=center|MEDIUM | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Marius/Torsten]] | ||
|- | |- | ||
− | |align=left width=62%|'''[https://github.com/openscad/openscad/wiki/Ideas | + | |align=left width=62%|'''[https://github.com/openscad/openscad/wiki/Ideas-for-Development-Tasks#larger-tasks-for-particularly-experienced-people Larger tasks for particularly experienced people]:''' Various harder tasks which are not fully specified and requires significant effort to design and implement. |
|align=center|C++ | |align=center|C++ | ||
|align=center|HARD | |align=center|HARD | ||
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Marius/Torsten]] |
|} | |} | ||
Line 440: | Line 371: | ||
LibreCAD is a free Open Source CAD application for Windows, Apple and Linux. Support and documentation is free from our large, dedicated community of users, contributors and developers. | LibreCAD is a free Open Source CAD application for Windows, Apple and Linux. Support and documentation is free from our large, dedicated community of users, contributors and developers. | ||
+ | Please refer to [http://wiki.librecad.org/index.php/GSoC_2018#LibreCAD_Project_Ideas LibreCAD GSoC 2018 ideas] for more detailed description. | ||
+ | |||
{| bgcolor=#fff | {| bgcolor=#fff | ||
Line 447: | Line 380: | ||
!align=center|Contacts | !align=center|Contacts | ||
|- | |- | ||
− | |width=62%|'''[[LibreCAD 3 | + | |
+ | |- bgcolor=#ffffff | ||
+ | |width=62%|'''[http://wiki.librecad.org/index.php/GSoC_2018#LibreCAD_Project_Ideas LibreCAD 3 UI]:''' Add missing features, e.g. snapping, to the very basic GUI. | ||
+ | |align=center|C++,Math | ||
+ | |align=center|MEDIUM | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Armin]], [[Google_Summer_of_Code/Project_Ideas#Mentors|Florian]] | ||
+ | |- | ||
+ | |||
+ | |- bgcolor=#ffffff | ||
+ | |width=62%|'''[http://wiki.librecad.org/index.php/GSoC_2018#LibreCAD_Project_Ideas LibreCAD 3 DXF Entities]''' Implement missing DXF entities, e.g. blocks, use LibreCAD 2 for reference. | ||
+ | |align=center|C++,Math | ||
+ | |align=center|MEDIUM | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Armin]], [[Google_Summer_of_Code/Project_Ideas#Mentors|Florian]] | ||
+ | |- | ||
+ | |||
+ | |||
+ | |- bgcolor=#ffffff | ||
+ | |width=62%|'''[http://wiki.librecad.org/index.php/GSoC_2018#LibreCAD_Project_Ideas LibreCAD 3 OpenGL rendering]:''' Replace our current rendering engine ''Cairo'' with pure OpenGL rendering. | ||
+ | |align=center|C++ | ||
+ | |align=center|MEDIUM/HIGH | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Armin]], [[Google_Summer_of_Code/Project_Ideas#Mentors|Florian]] | ||
+ | |- | ||
+ | |||
+ | |- bgcolor=#ffffff | ||
+ | |width=62%|'''[http://wiki.librecad.org/index.php/GSoC_2018#LibreCAD_Project_Ideas LibreCAD 3 Plugin Interface]''' Right now we have some LUA based scripting support for LibreCAD 3. But we want to be much more extensible, e.g. with a XML/JSON interface. | ||
|align=center|C++ | |align=center|C++ | ||
+ | |align=center|MEDIUM/HIGH | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Armin]], [[Google_Summer_of_Code/Project_Ideas#Mentors|Florian]] | ||
+ | |- | ||
+ | |||
+ | |- bgcolor=#ffffff | ||
+ | |width=62%|'''[http://wiki.librecad.org/index.php/GSoC_2018#LibreCAD_Project_Ideas LibreCAD 3 trimming support]''' LibreCAD 3 trim operation doesn't support all entities and is entirely written in Lua. We need a better system which would support all entities and divide operation. | ||
+ | |align=center|C++,Math | ||
|align=center|MEDIUM | |align=center|MEDIUM | ||
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Armin]], [[Google_Summer_of_Code/Project_Ideas#Mentors|Florian]] |
|- | |- | ||
|} | |} | ||
− | |||
= STEPcode Projects = | = STEPcode Projects = | ||
Line 460: | Line 423: | ||
! | ! | ||
!align=center|Languages | !align=center|Languages | ||
− | |||
!align=center|Difficulty | !align=center|Difficulty | ||
!align=center|Contacts | !align=center|Contacts | ||
Line 474: | Line 436: | ||
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Mark, Charlie]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Mark, Charlie]] | ||
|- | |- | ||
− | |width=62%|'''[[STEP | + | |width=62%|'''[[STEP Minimal Examples]]:''' Create minimal examples for various schemas - such as AP214 or AP242 - in the style of [http://github.com/stepcode/stepcode/blob/master/example/ap203min/ap203min.cpp ap203min] |
|align=center|C++ | |align=center|C++ | ||
|align=center|MEDIUM | |align=center|MEDIUM | ||
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Mark, Charlie]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Mark, Charlie]] | ||
|- | |- | ||
− | |width=62%|'''[[STEP | + | |width=62%|'''[[STEP Multiple Protocol Parsing]]:''' Currently creates a parser that works with a specific application protocol (e.g., AP203, AP214). Make it work with multiple simultaneously. |
|align=center|C++ | |align=center|C++ | ||
− | |align=center| | + | |align=center|MEDIUM |
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Mark, Charlie]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Mark, Charlie]] | ||
|- | |- | ||
− | |width=62%|'''[[STEP | + | |width=62%|'''[[STEP Source Code Documentation]]:''' We already use doxygen, but could do much better. Improve code documentation and utilize additional doxygen features such as topic pages. Add a 'make doxygen' target to invoke doxygen. |
|align=center|C/C++ | |align=center|C/C++ | ||
|align=center|EASY | |align=center|EASY | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Mark, Charlie]] | ||
+ | |- | ||
+ | |width=62%|'''[[STEP EXPRESS Documentation]]:''' Write 'exp2html', similar to exp2py or exp2cxx (python and C++ generators) but outputs graphs and hyperlinked documentation with JavaScript search. Output will include EXPRESS comments (this requires modifying the parser). | ||
+ | |align=center|C/C++, JavaScript | ||
+ | |align=center|MEDIUM | ||
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Mark, Charlie]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Mark, Charlie]] | ||
|- | |- | ||
|width=62%|'''[[STEP Viewer]]:''' STEP is a common CAD file format supported by just about every major CAD system. Given we have an importer and an interface for displaying geometry, a stand-alone STEP file viewer has some great potential. | |width=62%|'''[[STEP Viewer]]:''' STEP is a common CAD file format supported by just about every major CAD system. Given we have an importer and an interface for displaying geometry, a stand-alone STEP file viewer has some great potential. | ||
+ | |align=center|C/C++ | ||
+ | |align=center|MEDIUM | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Mark, Charlie]] | ||
+ | |- | ||
+ | |width=62%|'''[[STEP Code Refactoring]]:''' Split large files and functions, add unit tests, move contents of LISTdo loops into separate functions. | ||
+ | |align=center|C/C++ | ||
+ | |align=center|EASY | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Mark, Charlie]] | ||
+ | |- | ||
+ | |width=62%|'''[[STEP Thread Safety and Performance]]:''' Modify the libraries to improve thread safety, increase performance using hotspot analysis | ||
|align=center|C/C++ | |align=center|C/C++ | ||
|align=center|MEDIUM | |align=center|MEDIUM | ||
Line 495: | Line 472: | ||
|} | |} | ||
+ | = Slic3r Projects = | ||
+ | |||
+ | [http://slic3r.org Slic3r] is CAM desktop application for toolpath/G-code generation for 3D printers. | ||
+ | |||
+ | {| bgcolor=#fff width=100% | ||
+ | ! | ||
+ | !align=center|Languages | ||
+ | !align=center|Difficulty | ||
+ | !align=center|Contacts | ||
+ | |- | ||
+ | |width=62%|'''Port the GUI to C++:''' The GUI is currently coded in Perl using wxWidgets and our goal is to have it ported to C++. The wxWidgets API is almost identical between Perl and C++, so it's an easy task. There are a couple things where we use the dynamic features of Perl which are trickier and interesting to port. | ||
+ | |C++/wxWidgets | ||
+ | |align=center|Easy | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Alessandro/Joseph]] | ||
+ | |- | ||
+ | |width=62%|'''Port the SVGNest library to C++:''' The SVGNest library provides an algorithm for polygon nesting. It's written in JavaScript and a C++ port of it would improve Slic3r's auto-arrange feature. [https://github.com/alexrj/Slic3r/issues/3237 #3237] | ||
+ | |C++ | ||
+ | |align=center|Easy | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Alessandro/Joseph]] | ||
+ | |- | ||
+ | |width=62%|'''Fix bugs of the Boost.Voronoi library:''' The good but unmaintained Boost.Voronoi library has a couple minor issues affecting Slic3r's results. Interesting task for learning the Voronoi algorithm and how to troubleshoot a computational geometry issue. [https://github.com/alexrj/Slic3r/issues/2948 #2948] | ||
+ | |C++ | ||
+ | |align=center|Medium | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Alessandro/Joseph]] | ||
+ | |- | ||
+ | |width=62%|'''Wireframe printing:''' Implement the wireframe printing algorithm. [https://github.com/alexrj/Slic3r/issues/2274 #2274] | ||
+ | |C++ | ||
+ | |align=center|Medium | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Alessandro/Joseph]] | ||
+ | |- | ||
+ | |width=62%|'''Automatic part rotation:''' Automatically rotate a part to make some face of the part the bottom. [https://github.com/alexrj/Slic3r/issues/3047 #3047] | ||
+ | |C++ | ||
+ | |align=center|Medium | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Alessandro/Joseph]] | ||
+ | |- | ||
+ | |width=62%|'''Manual support creation:''' Allow users to place and move support pillars by clicking in the 3D GUI. [https://github.com/alexrj/Slic3r/issues/3062 #3062] | ||
+ | |C++/Perl/OpenGL | ||
+ | |align=center|Medium/Hard | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Alessandro/Joseph]] | ||
+ | |- | ||
+ | |width=62%|'''Refactor the TriangleMesh class and support non-solid walls:''' Replace the internal mesh representation (currently based on admesh) using an existing 3D mesh library or implementing a half-edge structure; only use admesh for fixing models. Keep non-solid walls and slice them as single paths. Bonus: import SVG paths and position them freely using the GUI for printing as single extrusions. [https://github.com/alexrj/Slic3r/issues/3560 #3560] [https://github.com/alexrj/Slic3r/issues/3523 #3523] | ||
+ | |C++ | ||
+ | |align=center|Medium/Hard | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Alessandro/Joseph]] | ||
+ | |- | ||
+ | |width=62%|'''Non-planar printing:''' Implement techniques for non-planar printing. [https://github.com/alexrj/Slic3r/issues/3442 #3442] | ||
+ | |C++ | ||
+ | |align=center|Medium | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Alessandro/Joseph]] | ||
+ | |- | ||
+ | |width=62%|'''Support surface colors and mixing extruders:''' Read surface colors from AMF or OBJ and keep them throughout the slicing process in order to generate G-code for mixing extruders. [https://github.com/alexrj/Slic3r/issues/3546 #3546] | ||
+ | |C++/Perl | ||
+ | |align=center|Hard | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Alessandro/Joseph]] | ||
+ | |- | ||
+ | |width=62%|'''Clean the libslic3r API and write bindings for it:''' Expose the internal algorithms of Slic3r as a library and write bindings for Python, Perl etc. | ||
+ | |C++/any | ||
+ | |align=center|Easy | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Alessandro/Joseph]] | ||
+ | |- | ||
+ | |width=62%|'''Write a Slic3r plugin for Grasshopper:''' Expose Slic3r functionality as many separate components that can be plugged in larger GH definitions (for example: slice a NURBS model in GH and feed the slices to the toolpath generation process in order to skip mesh generation, or provide flow calculation for people driving 5-axis robots with custom motion). This requires a fair amount of design work. | ||
+ | |C++ | ||
+ | |align=center|Medium/Hard | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Alessandro/Joseph]] | ||
+ | |} | ||
+ | |||
+ | = FreeCAD Projects = | ||
+ | |||
+ | {| bgcolor=#fff width=100% | ||
+ | ! | ||
+ | ! Language | ||
+ | ! Difficulty | ||
+ | ! Contact | ||
+ | |- | ||
+ | |width=62%|'''[http://www.freecadweb.org/wiki/Advanced_FreeCAD_test_system Advanced FreeCAD test system ]''': Create a framework for result file based comparisons and workbench specific comparators. Also creation of test cases should be simplified by a GUI or wizard. | ||
+ | |align=center|Python/C++ | ||
+ | |align=center|Medium | ||
+ | |align=center|[http://forum.freecadweb.org/memberlist.php?mode=viewprofile&u=686 Ickby] | ||
+ | |- | ||
+ | |width=62%|'''[http://www.freecadweb.org/wiki/Topological_Naming_Project Topological Naming Project]''': Implementation of subshape identifiers based on creation history and update of topology class to work with those identifiers. | ||
+ | |align=center|C++ | ||
+ | |align=center|Hard | ||
+ | |align=center|[http://forum.freecadweb.org/memberlist.php?mode=viewprofile&u=686 Ickby] | ||
+ | |- | ||
+ | |width=62%|'''[http://www.freecadweb.org/wiki/Direct_modeling_tools Direct modeling tools]''': Create a new layer of tools and objects, that work on top of existing Part-based 3D objects, that allow a user to graphically modify their geometry. | ||
+ | |align=center|Python/C++ | ||
+ | |align=center|Medium | ||
+ | |align=center|[http://forum.freecadweb.org/memberlist.php?mode=viewprofile&u=68 Yorik] | ||
+ | |- | ||
+ | |width=62%|'''[http://www.freecadweb.org/wiki/FEM_Post_Processing_based_on_VTK FEM Post Processing based on VTK]''': Base the existing FEM VTK post processing on the updated SMESH data structure and design a python interface for it. Also improve integration into the workbench. | ||
+ | |align=center|C++ | ||
+ | |align=center|Medium | ||
+ | |align=center|[http://forum.freecadweb.org/memberlist.php?mode=viewprofile&u=686 Ickby] | ||
+ | |- | ||
+ | |width=62%|'''[http://www.freecadweb.org/wiki/IPython_notebook_integration IPython notebook integration]''': Create a way to export the open inventor scenegraph as a JavaScript file and add functions for seamless interaction with the IPython display system | ||
+ | |align=center|C++, JavaScript, Python | ||
+ | |align=center|Easy | ||
+ | |align=center|[http://forum.freecadweb.org/memberlist.php?mode=viewprofile&u=686 Ickby] | ||
+ | |- | ||
+ | |width=62%|'''[https://www.freecadweb.org/wiki/Integrate_Cycles_renderer Integrate Cycles renderer]''': Add Blender's new Cycles renderer as a new render engine to the Raytracing Workbench | ||
+ | |align=center|C++ | ||
+ | |align=center|Medium | ||
+ | |align=center|[http://forum.freecadweb.org/memberlist.php?mode=viewprofile&u=68 Yorik] | ||
+ | |- | ||
+ | |width=62%|Stepwise integration of ElmerFem into FreeCAD should be done in three phases: | ||
+ | Phase 1 - '''[https://www.freecadweb.org/wiki/New_solver_object_for_handling_ElmerFEM_execution_in_FEM-workbench New solver object for handling ElmerFEM execution in FEM-workbench]'''. | ||
+ | Phase 2 - '''[https://www.freecadweb.org/wiki/Mapping_of_main_ElmerSolver_setting_for_mechanical_simulations Mapping of main ElmerSolver setting for mechanical simulations]'''. | ||
+ | Phase 3 - '''[https://www.freecadweb.org/wiki/Give_graphical_access_to_a_wide_range_of_available_ElmerSolver_setting_from_within_FreeCAD Give graphical access to a wide range of available ElmerSolver setting from within FreeCAD]''' | ||
+ | |align=center|Python/C++ | ||
+ | |align=center|Medium-Hard | ||
+ | |align=center|[https://forum.freecadweb.org/memberlist.php?mode=viewprofile&u=2069 Bernd], [https://forum.freecadweb.org/memberlist.php?mode=viewprofile&u=6222 HoWil] | ||
+ | |- | ||
+ | |width=62%|'''[https://www.freecadweb.org/wiki/PartDesign_Updates PartDesign Updates]''': Finish PartDesign port to new Body object, simplify the workflows and extend tools while making them more robust. | ||
+ | |align=center|C++, Python | ||
+ | |align=center|Medium | ||
+ | |align=center|[http://forum.freecadweb.org/memberlist.php?mode=viewprofile&u=686 Ickby] | ||
+ | |- | ||
+ | |width=62%|'''[https://www.freecadweb.org/wiki/GSoC_FEM_Solver_Z88 GSoC FEM Solver Z88]''': Extend the capabilities of FEM solver Z88OS in FreeCAD FEM workbench. | ||
+ | |align=center|Python | ||
+ | |align=center|Easy-Medium | ||
+ | |align=center|[http://forum.freecadweb.org/memberlist.php?mode=viewprofile&u=686 Bernd] | ||
+ | |- | ||
+ | |width=62%|'''[https://www.freecadweb.org/wiki/GSoC_FEM_Unit_Tests GSoC FEM Unit Tests]''': Extend the unit tests of FreeCAD FEM workbench. | ||
+ | |align=center|Python | ||
+ | |align=center|Easy-Medium | ||
+ | |align=center|[http://forum.freecadweb.org/memberlist.php?mode=viewprofile&u=686 Bernd] | ||
+ | |- | ||
+ | |width=62%|'''[https://www.freecadweb.org/wiki/GSoC_Path/Robot_Integration GSoC Path/Robot Integration]''': Path is the CNC/CAM workbench. It currently lacks any simulation capability. Robot workbench is a tool for simulating industrial robots. Extend Path and Robot workbenches to support simulation of CNC operations in the Robot workbench. | ||
+ | |align=center|C++, Python | ||
+ | |align=center|Easy-Medium | ||
+ | |align=center|[http://forum.freecadweb.org/memberlist.php?mode=viewprofile&u=68 Yorik], [https://forum.freecadweb.org/memberlist.php?mode=viewprofile&u=708 sliptonic] | ||
+ | |} | ||
= Mentors = | = Mentors = | ||
Line 507: | Line 616: | ||
** ``Erik on irc.freenode.net | ** ``Erik on irc.freenode.net | ||
** Org admin, BRL-CAD core dev | ** Org admin, BRL-CAD core dev | ||
+ | ** mainly FDM/FFF, geometry conversion, CAE/prototyping | ||
* Cliff Yapp | * Cliff Yapp | ||
Line 525: | Line 635: | ||
* Bryan Bishop | * Bryan Bishop | ||
** BRL-CAD Mentor, python guru | ** BRL-CAD Mentor, python guru | ||
+ | |||
+ | * Isaac Kamga | ||
+ | ** Izakey on irc.freenode.net | ||
+ | ** BRL-CAD Mentor, C/C++ Programmer | ||
+ | |||
+ | * Mohit Daga | ||
+ | ** zero_level irc.freenode.net | ||
+ | ** BRL-CAD Mentor, Computer Science Engineer | ||
+ | |||
+ | * Inderpreet Singh (Pooh) | ||
+ | ** Pooh on https://brlcad.zulipchat.com | ||
+ | ** OGV mentor | ||
+ | |||
+ | * Gauravjeet Singh (Panda) | ||
+ | ** Panda on https://brlcad.zulipchat.com | ||
+ | ** OGV mentor | ||
* Mark Pictor | * Mark Pictor | ||
Line 542: | Line 668: | ||
** OpenSCAD Mentor | ** OpenSCAD Mentor | ||
− | * | + | * Armin Stebich |
− | ** | + | ** LordOfBikes on irc.freenode.net |
** LibreCAD Mentor | ** LibreCAD Mentor | ||
− | * | + | * Florian Roméo |
− | ** | + | ** Feragon on irc.freenode.net |
** LibreCAD Mentor | ** LibreCAD Mentor | ||
− | * | + | * Alessandro Ranellucci |
− | ** | + | ** Sound on irc.freenode.net |
− | ** | + | ** Slic3r Mentor |
+ | |||
+ | * Joseph Lenox | ||
+ | ** LoH on irc.freenode.net | ||
+ | ** Slic3r Mentor | ||
− | * | + | * Shubham Rathore (:gabbar1947) |
− | ** | + | ** gabbar1947 on irc.freenode.net |
− | ** | + | ** BRL-CAD Mentor |
Latest revision as of 00:00, 30 March 2020
If you want to work on computer-aided design (CAD), geometry, or graphics, you've come to the right place! Help us improve open source CAD.
Well prepared proposals from capable students have an outstanding chance of getting selected. We consider proposals for all skill levels ranging from simple to crazy hard and everything in between. Introduce yourself, and we'll help you plan one right for you.
Remember that project descriptions are just initial ideas. You must expand with considerably more detail. Change the goals to fit your experience and interests. See our checklist to get started.
This year, BRL-CAD is coordinating with five other communities that will get 1-2 students each to help bridge our work and encourage collaboration. Projects that help exchange data or share code are desired!
Project titles link to a page with more details.
Contents
BRL-CAD Projects[edit]
High Priority Topics[edit]
This year, we are most interested in topics that will immediately benefit BRL-CAD users. Please align your proposal with one of the following three focus areas. Talk with us at http://brlcad.zulipchat.com
Performance | Faster geometry. In order, ideas likeCoherent Raytracing, anything involving OpenCL, parallelizing serial code, and eliminating LIBBU pointer aliasing. |
User Interface | Build on Google Code-In progress (OpenSCAD-style GUI), Convert MGED from Tk to Qt, revamp our Overlap tool GUI, etc. Qt and ray tracing are fair game. |
Core Infrastructure | Integrate appleseed rendering, extend and deploy Online Geometry Viewer (OGV), expand our geometry conversion (GCV) library. |
Web Development[edit]
Languages | Difficulty | Contacts | |
---|---|---|---|
Synchronize Wiki with Docbook: We use Docbook for most of our user documentation but find editing a wiki page much easier to use. Set up a system so the two are always in sync. | Depends (likely PHP or Python) | MEDIUM | Yapp |
Online Geometry Viewer Back-end: Continuation of existing work, improve our interface for viewing geometry online. Focus on the back-end infrastructure. | C++, Javascript, Meteor.js, Three.js | Medium | Morrison,Pooh, Panda |
Mediawiki 3D Geometry Extension: Write an extension for Mediawiki that will visualize our .g files. Maybe leverage LLVM C->Javascript translation. | Depends (likely PHP or Python) | HARD | Morrison |
Geometry[edit]
Languages | Difficulty | Contacts | |
---|---|---|---|
Plate Mode NURBS raytracing: Imported NURBS geometry often does NOT enclose space (i.e., not solid), so add support for specifying an implicit thickness. | C/C++ | HARD | Morrison |
Overlap tool: Resolving geometric interferences (aka overlaps) is a common geometry editing activity. Design an awesome GUI for resolving conflicts. | Tcl | EASY | Yapp, Morrison, Greenwald |
NURBS Editing Support: BRL-CAD doesn't currently have good support for editing NURBS primitives. Fix that. | C/Tcl | MEDIUM | Yapp |
Vector Drawings from NURBS: Huge impact here if you can update one or more of our raytracers to provide vector output instead of raster. Perhaps render directly to PDF or SVG. | C and/or C++ | EASY | Rossberg |
NMG Editing: Our structured polygonal mesh geometry (N-Manifold Geometry = NMG) is a common export format, but our NMG edit support is non-existent. We need something. | C | HARD | Morrison, Rossberg |
Geometry Conversion Library: Probably our biggest open source asset is our extensive collection of importers and exporters. Turn them all into a universal conversion library. | C/C++ | EASY | Greenwald, Morrison, Rossberg |
STEP importer improvements: We have an importer, but it's preliminary. Add support for importing hierarchy information, polygonal geometry, and implicit geometry. | C/C++ | MEDIUM | Yapp |
STEP exporter: We have an importer, we need a comprehensive exporter with support for implicit CSG, NURBS, or polygonal mesh geometry. | C/C++ | EASY | Yapp, Morrison |
Convert BoT to Pipe: Command line interface to convert facetted fluid/electrical line geometry into BRL-CAD native pipe solids. | C/C++/Tcl | MEDIUM | Morrison |
OpenSCAD Importer: Create an importer for OpenSCAD's format. | C/C++ | EASY | Morrison |
OpenSCAD Exporter: Create an exporter for OpenSCAD's format. | C/C++ | EASY | Morrison |
Python Geometry: Wrap BRL-CAD's primitives in Python (or Lua), make it easier to script geometry creation. | Python/Lua | Easy | Morrison |
Performance & Quality[edit]
Languages | Difficulty | Contacts | |
---|---|---|---|
Coherent Raytracing: Our current raytrace pipeline dispatches and processes one ray at a time. Send bundles and convert the pipeline into phases. | C/C++ | MEDIUM | Morrison, Rossberg |
OpenCL GPGPU Raytracing: We have about a dozen simple primitives that need to have a ray-object intersection function converted from C to OpenCL. | C/OpenCL | EASY | Morrison |
OpenCL GPGPU Complex Raytracing: We have about half a dozen complex primitives that need to have a ray-object intersection function converted from C to OpenCL. | C/OpenCL | MEDIUM | Morrison |
OpenCL GPGPU Spatial Partitioning Raytracing: We use a Bounding Volume Hierarchy (BVH) to reduce the amount of intersections we need to compute to render an image. We need to replace this with a Kd-tree in order to be able to early terminate a render in models with high depth complexity. This should speed up render speed significantly for those models (e.g. Goliath). | C/OpenCL | HARD | Morrison |
OpenCL GPGPU Brep Raytracing: We need to support Brep NURBS raytracing over the GPU. There is example CPU only code. Execution on the GPU should significantly enhance rendering performance of these primitives. | C/OpenCL | HARD | Morrison |
NURBS Booleans: We have NURBS surface-surface intersections working. Now we're using them to create evaluated forms of our CSG geometry. Make it more robust and faster. | C/C++ | HARD | Yapp, Rossberg |
NURBS Optimization and Cleanup: We have a fantastic implementation of NURBS evaluation but haven't gone back to clean up or speed it up. Make it pretty and fast. | C/C++ | MEDIUM | Yapp, Morrison |
Space Partitioning for Tessellation: Technically an optimization task, make our geometry converters run an order of magnitude faster by using spatial partitioning during tessellation. | C | HARD | Greenwald, Yapp, Morrison |
Faster Overlap Detection: BRL-CAD has a 'gqa' tool that detects overlaps. Implement a replacement using a better approach. | C | MEDIUM | Greenwald, Morrison |
Infrastructure[edit]
Languages | Difficulty | Contacts | |
---|---|---|---|
New Cross-Platform 3D Display Manager: BRL-CAD uses display managers for visualizing 3D geometry in a window. We want one that uses a cross-platform toolkit such as Qt + OGRE. | C/C++ | MEDIUM | Morrison |
New Cross-Platform 2D Framebuffer: BRL-CAD uses framebuffers to display 2D imagery. The merits of having a single interface for most platforms is self-evident. | C/C++ | EASY | Morrison, Yapp |
General Tree Walker: We have a half dozen or more functions that will traverse a geometry hierarchy in different ways. There only needs to be one. | C | EASY | Greenwald, Yapp, Morrison |
GED Transactions: Migrating functionality from our MGED geometry editor into our LIBGED library provided excellent code reuse, but now we need transactions so that actions can be undone. | C | EASY | Morrison, Daga |
Add exec option to search: Our LIBGED library provides a search command very similar to the UNIX find command for scanning through geometry. Implement the -exec option. | C | EASY | Yapp, Daga |
Astronomical units: We already go "big", but accurately modeling at a galactic scale redefines that notion... | C | EASY | Morrison, Greenwald, Daga |
Object-oriented C++ Geometry API: Extend our C++ library which provides a simple interface to BRL-CAD's core functionality. Kickstart start a new geometry kernel. | C++ | MEDIUM | Rossberg, Kamga |
Point Clouds: BRL-CAD has a basic point cloud primitive. Beef it up, make it faster, maybe integrate with the Point Cloud Library (PCL) for evaluation. | C/C++ | MEDIUM | Browder, Kamga |
Annotations: Implement support for 2D annotations, labels that can be added to geometry. | Perl | EASY | Browder |
Rendering & Scientific Analysis[edit]
Languages | Difficulty | Contacts | |
---|---|---|---|
Appleseed renderer integration: Appleseed is rendering infrastructure used by the film industry to make pretty pictures. Make it shoot rays at our native geometry with our ray trace library. | C | MEDIUM | Morrison |
Material and Shader Objects: This one is a biggie but easy. Implement new object entities for describing shaders and material properties, use them during ray tracing. | C | EASY | Morrison |
Generalized abstracted spacial partitioning capability: Need more be said? If you're familiar with BSPs, KD trees, and grid structures, then this one is for you. | C | HARD | Greenwald, Morrison |
High Dynamic Range Support: We don't have displays supporting this yet, but that's never stopped us before. Implement support for images with more than 8-bits per channel. | C and/or C++ | EASY | Greenwald, Yapp |
Analysis Library: There are various tools in BRL-CAD for calculating weights, moments of inertia, and more. They're stand-alone applications. Turn them into a library. | C | HARD | Yapp, Morrison |
Celestial mechanics particle system: Simulate solar systems and galaxies. | C/C++ | MEDIUM | Greenwald |
Density functions: Accurately represent everything from atmosphere to bone. Implement support for parametric density functions for homogenous materials. | C | HARD | Rossberg, Morrison |
Bending light: Think gravity wells and satellite cameras. | C | MEDIUM | Morrison |
Open Channel For Goods Using Optics +robotics concept: We can Create A Tunnel Like way Where we can transport goods like We Transport data through seas Using Optics. Only Need Is To make it automated with perfect coding for destination. We can Do this with the help of Software+Mechanical Engineers. Where coding and assembly plays important role.. Coding can Be Done In General By C/c++ language which is Simpler
OpenSCAD Projects[edit]
OpenSCAD is a parametric solid 3D modeling tool which uses a Domain Specific Language to specify designs as plain text. It is specifically designed with 3D printing in mind.
Languages/Tools | Difficulty | Contacts | |
---|---|---|---|
Improve DXF Import and Export: Look into using an external library for DXF import (and export?). | C++ | MEDIUM | Marius/Torsten |
OpenSCAD Standard Library: Create a standard user-space OpenSCAD library. | OpenSCAD | MEDIUM | Marius/Torsten |
OpenGL framework: Rewrite the OpenGL rendering code to use a rendering framework. Focus on compatibility with OpenGL ES2 and rendering performance. | C++ OpenGL | MEDIUM | Marius/Torsten |
Improve Text Editor: Add more IDE style features to the text editor integrated in OpenSCAD. | C++ | MEDIUM | Marius/Torsten |
Persistent Caching: Implement a disk-based version of the internal memory caches | C++ | MEDIUM | Marius/Torsten |
Multi-threaded Geometry Evaluation: Implement multi-threaded evaluation of geometry. | C++ | MEDIUM | Marius/Torsten |
Survey of CSG algorithms: Review existing research, evaluate and prototype algorithms. | C++ | MEDIUM-HARD | Marius/Torsten |
Add support for exporting models in STEP format: Enable better integration with other CAD tools by adding STEP export. | C++ | HARD | Marius/Torsten |
Issue Handling: Day-to day issue and community management, fix incoming and existing issues. Good place to get started. | C++ | EASY | Marius/Torsten |
Test Framework Improvements: Improve tests and test framework. Good place to get started. | Python, C++ | EASY-MEDIUM | Marius/Torsten |
SVG Import: Improve/finalize SVG import. | C++, SVG | MEDIUM | Marius/Torsten |
Larger tasks for particularly experienced people: Various harder tasks which are not fully specified and requires significant effort to design and implement. | C++ | HARD | Marius/Torsten |
The OpenSCAD team is also open to new ideas. Please get in touch to discuss your ideas and convince a mentor to back it.
LibreCAD Projects[edit]
LibreCAD is a free Open Source CAD application for Windows, Apple and Linux. Support and documentation is free from our large, dedicated community of users, contributors and developers. Please refer to LibreCAD GSoC 2018 ideas for more detailed description.
Languages | Difficulty | Contacts | |
---|---|---|---|
LibreCAD 3 UI: Add missing features, e.g. snapping, to the very basic GUI. | C++,Math | MEDIUM | Armin, Florian |
LibreCAD 3 DXF Entities Implement missing DXF entities, e.g. blocks, use LibreCAD 2 for reference. | C++,Math | MEDIUM | Armin, Florian |
LibreCAD 3 OpenGL rendering: Replace our current rendering engine Cairo with pure OpenGL rendering. | C++ | MEDIUM/HIGH | Armin, Florian |
LibreCAD 3 Plugin Interface Right now we have some LUA based scripting support for LibreCAD 3. But we want to be much more extensible, e.g. with a XML/JSON interface. | C++ | MEDIUM/HIGH | Armin, Florian |
LibreCAD 3 trimming support LibreCAD 3 trim operation doesn't support all entities and is entirely written in Lua. We need a better system which would support all entities and divide operation. | C++,Math | MEDIUM | Armin, Florian |
STEPcode Projects[edit]
Languages | Difficulty | Contacts | |
---|---|---|---|
STEP Coverage Test: Write a program that links against STEPcode and generates a STEP output instantiating every entity for a given schema. Goal is a comprehensive program and data file for testing STEP import/export. | ANY (C/C++, Python, Java, Perl, ...) | EASY | Mark, Charlie |
STEP Incremental Loading: Basically take a work-in-progress to the next level. Modify the STEP parser to only read what it needs when it needs it, test, clean up, profile, and optimize. | C++ | EASY | Mark, Charlie |
STEP Minimal Examples: Create minimal examples for various schemas - such as AP214 or AP242 - in the style of ap203min | C++ | MEDIUM | Mark, Charlie |
STEP Multiple Protocol Parsing: Currently creates a parser that works with a specific application protocol (e.g., AP203, AP214). Make it work with multiple simultaneously. | C++ | MEDIUM | Mark, Charlie |
STEP Source Code Documentation: We already use doxygen, but could do much better. Improve code documentation and utilize additional doxygen features such as topic pages. Add a 'make doxygen' target to invoke doxygen. | C/C++ | EASY | Mark, Charlie |
STEP EXPRESS Documentation: Write 'exp2html', similar to exp2py or exp2cxx (python and C++ generators) but outputs graphs and hyperlinked documentation with JavaScript search. Output will include EXPRESS comments (this requires modifying the parser). | C/C++, JavaScript | MEDIUM | Mark, Charlie |
STEP Viewer: STEP is a common CAD file format supported by just about every major CAD system. Given we have an importer and an interface for displaying geometry, a stand-alone STEP file viewer has some great potential. | C/C++ | MEDIUM | Mark, Charlie |
STEP Code Refactoring: Split large files and functions, add unit tests, move contents of LISTdo loops into separate functions. | C/C++ | EASY | Mark, Charlie |
STEP Thread Safety and Performance: Modify the libraries to improve thread safety, increase performance using hotspot analysis | C/C++ | MEDIUM | Mark, Charlie |
Slic3r Projects[edit]
Slic3r is CAM desktop application for toolpath/G-code generation for 3D printers.
Languages | Difficulty | Contacts | |
---|---|---|---|
Port the GUI to C++: The GUI is currently coded in Perl using wxWidgets and our goal is to have it ported to C++. The wxWidgets API is almost identical between Perl and C++, so it's an easy task. There are a couple things where we use the dynamic features of Perl which are trickier and interesting to port. | C++/wxWidgets | Easy | Alessandro/Joseph |
Port the SVGNest library to C++: The SVGNest library provides an algorithm for polygon nesting. It's written in JavaScript and a C++ port of it would improve Slic3r's auto-arrange feature. #3237 | C++ | Easy | Alessandro/Joseph |
Fix bugs of the Boost.Voronoi library: The good but unmaintained Boost.Voronoi library has a couple minor issues affecting Slic3r's results. Interesting task for learning the Voronoi algorithm and how to troubleshoot a computational geometry issue. #2948 | C++ | Medium | Alessandro/Joseph |
Wireframe printing: Implement the wireframe printing algorithm. #2274 | C++ | Medium | Alessandro/Joseph |
Automatic part rotation: Automatically rotate a part to make some face of the part the bottom. #3047 | C++ | Medium | Alessandro/Joseph |
Manual support creation: Allow users to place and move support pillars by clicking in the 3D GUI. #3062 | C++/Perl/OpenGL | Medium/Hard | Alessandro/Joseph |
Refactor the TriangleMesh class and support non-solid walls: Replace the internal mesh representation (currently based on admesh) using an existing 3D mesh library or implementing a half-edge structure; only use admesh for fixing models. Keep non-solid walls and slice them as single paths. Bonus: import SVG paths and position them freely using the GUI for printing as single extrusions. #3560 #3523 | C++ | Medium/Hard | Alessandro/Joseph |
Non-planar printing: Implement techniques for non-planar printing. #3442 | C++ | Medium | Alessandro/Joseph |
Support surface colors and mixing extruders: Read surface colors from AMF or OBJ and keep them throughout the slicing process in order to generate G-code for mixing extruders. #3546 | C++/Perl | Hard | Alessandro/Joseph |
Clean the libslic3r API and write bindings for it: Expose the internal algorithms of Slic3r as a library and write bindings for Python, Perl etc. | C++/any | Easy | Alessandro/Joseph |
Write a Slic3r plugin for Grasshopper: Expose Slic3r functionality as many separate components that can be plugged in larger GH definitions (for example: slice a NURBS model in GH and feed the slices to the toolpath generation process in order to skip mesh generation, or provide flow calculation for people driving 5-axis robots with custom motion). This requires a fair amount of design work. | C++ | Medium/Hard | Alessandro/Joseph |
FreeCAD Projects[edit]
Language | Difficulty | Contact | |
---|---|---|---|
Advanced FreeCAD test system : Create a framework for result file based comparisons and workbench specific comparators. Also creation of test cases should be simplified by a GUI or wizard. | Python/C++ | Medium | Ickby |
Topological Naming Project: Implementation of subshape identifiers based on creation history and update of topology class to work with those identifiers. | C++ | Hard | Ickby |
Direct modeling tools: Create a new layer of tools and objects, that work on top of existing Part-based 3D objects, that allow a user to graphically modify their geometry. | Python/C++ | Medium | Yorik |
FEM Post Processing based on VTK: Base the existing FEM VTK post processing on the updated SMESH data structure and design a python interface for it. Also improve integration into the workbench. | C++ | Medium | Ickby |
IPython notebook integration: Create a way to export the open inventor scenegraph as a JavaScript file and add functions for seamless interaction with the IPython display system | C++, JavaScript, Python | Easy | Ickby |
Integrate Cycles renderer: Add Blender's new Cycles renderer as a new render engine to the Raytracing Workbench | C++ | Medium | Yorik |
Stepwise integration of ElmerFem into FreeCAD should be done in three phases:
Phase 1 - New solver object for handling ElmerFEM execution in FEM-workbench. Phase 2 - Mapping of main ElmerSolver setting for mechanical simulations. Phase 3 - Give graphical access to a wide range of available ElmerSolver setting from within FreeCAD |
Python/C++ | Medium-Hard | Bernd, HoWil |
PartDesign Updates: Finish PartDesign port to new Body object, simplify the workflows and extend tools while making them more robust. | C++, Python | Medium | Ickby |
GSoC FEM Solver Z88: Extend the capabilities of FEM solver Z88OS in FreeCAD FEM workbench. | Python | Easy-Medium | Bernd |
GSoC FEM Unit Tests: Extend the unit tests of FreeCAD FEM workbench. | Python | Easy-Medium | Bernd |
GSoC Path/Robot Integration: Path is the CNC/CAM workbench. It currently lacks any simulation capability. Robot workbench is a tool for simulating industrial robots. Extend Path and Robot workbenches to support simulation of CNC operations in the Robot workbench. | C++, Python | Easy-Medium | Yorik, sliptonic |
Mentors[edit]
BRL-CAD operates under group mentorship. That means you can contact anyone, not just the person assigned to you, for assistance. The mailing list and IRC channel are the preferred communication methods.
- Christopher Sean Morrison
- brlcad on irc.freenode.net
- Org admin, BRL-CAD open source project lead
- Erik Greenwald
- ``Erik on irc.freenode.net
- Org admin, BRL-CAD core dev
- mainly FDM/FFF, geometry conversion, CAE/prototyping
- Cliff Yapp
- starseeker on irc.freenode.net
- BRL-CAD Mentor, core dev
- Daniel Rossberg
- d_rossberg on irc.freenode.net
- BRL-CAD Mentor, core dev, math expert
- H.S. Rai
- hsrai on irc.freenode.net
- BRL-CAD Mentor, math expert
- Tom Browder
- BRL-CAD Mentor, analysis expert
- Bryan Bishop
- BRL-CAD Mentor, python guru
- Isaac Kamga
- Izakey on irc.freenode.net
- BRL-CAD Mentor, C/C++ Programmer
- Mohit Daga
- zero_level irc.freenode.net
- BRL-CAD Mentor, Computer Science Engineer
- Inderpreet Singh (Pooh)
- Pooh on https://brlcad.zulipchat.com
- OGV mentor
- Gauravjeet Singh (Panda)
- Panda on https://brlcad.zulipchat.com
- OGV mentor
- Mark Pictor
- mpictor on irc.freenode.net
- STEPcode Mentor
- Charlie Stirk
- cstirk
- STEPcode Mentor
- Marius Kintel
- kintel on irc.freenode.net
- OpenSCAD Mentor
- Torsten Paul
- teepee on irc.freenode.net
- OpenSCAD Mentor
- Armin Stebich
- LordOfBikes on irc.freenode.net
- LibreCAD Mentor
- Florian Roméo
- Feragon on irc.freenode.net
- LibreCAD Mentor
- Alessandro Ranellucci
- Sound on irc.freenode.net
- Slic3r Mentor
- Joseph Lenox
- LoH on irc.freenode.net
- Slic3r Mentor
- Shubham Rathore (:gabbar1947)
- gabbar1947 on irc.freenode.net
- BRL-CAD Mentor