Editing Google Summer of Code/Project Ideas
From BRL-CAD
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
− | If you want to work on '''computer-aided design (CAD), geometry, or graphics''', you've come to the right place! | + | If you want to work on open source '''computer-aided design (CAD), geometry, or graphics''', you've come to the right place! |
− | + | We'd love to have you work on projects that make our software better. The project possibilities range from very simple to crazy hard with intense math and everything in between. '''Each project idea below links to a page with more details.''' | |
− | + | This year, BRL-CAD is coordinating with three other open source CAD efforts to help bridge our communities and encourage collaboration. Projects that help us exchange data or share code are encouraged! | |
− | + | {|align="center" width="62%" | |
− | + | |align="center" |http://brlcad.org/images/logo/BRL-CAD_gear_logo_w_name_256.png | |
− | {| | + | |colspan=2 align="center" |Under development for 30+ years, it's big, it's complicated, it's powerful. BRL-CAD will consider just about any project that relates to computer graphics. |
− | |align="center" width=" | + | |} |
− | |align="center" width=" | + | {|align="center" width="90%" |
− | |align="center" width=" | + | |align="center" width="33%"|[https://github.com/openscad/openscad/wiki/Ideas:-GSoC-2014 http://www.openscad.org/assets/img/logo.png] |
+ | |align="center" width="33%"|[https://librecad.org http://librecad.org/files/live/sites/lc/files/WebImages/LogoLibrecad_logo.png] | ||
+ | |align="center" width="33%"|[http://stepcode.org/mw/index.php?title=List_of_projects http://stepcode.org/STEPcode_logo_sm.png] | ||
|- | |- | ||
|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"|''' | + | |align="center"|'''LibreCAD''': 2D CAD modeling, drafting, drawings. |
− | |align="center"|''' | + | |align="center"|'''STEPcode''':A file format on steroids, STEP is a complex standard for geometry data used by nearly every pro CAD system. |
+ | |} | ||
+ | |||
+ | Remember that our project descriptions are just ''initial ideas''. You must '''expand''' with [[Summer_of_Code/Application_Guidelines|considerably more detail]]. You're encouraged to scale the scope up, down, or completely change the goals to fit your experience level and interest. Proposing a hard project does not improve your chances of getting selected. | ||
+ | |||
+ | '''Unless there isn't a quality proposal, we will be selecting at least one student for each of BRL-CAD's main categories as well as at least one student each for STEPcode, OpenSCAD, and LibreCAD.''' | ||
+ | |||
+ | {|align="right" width=256 | ||
+ | |[[Image:BRL-CAD_Priorities.png|thumb|left|256px|BRL-CAD Priorities]] | ||
|- | |- | ||
− | | | + | | There are also many [http://brlcad.org/~sean/ideas.html other project ideas] that would be interesting to us. Suggest your own. Don't be shy if you have [[Mailing_Lists|questions]]! |
− | |||
|- | |- | ||
− | + | |'''Be sure to follow our [[Summer_of_Code/Checklist|checklist]] for guidance getting started.''' | |
− | |||
|} | |} | ||
− | |||
− | = | + | = Project Categories = |
− | |||
− | |||
− | + | == Geometry == | |
− | + | ||
− | + | ===Project: NURBS=== | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | BRL-CAD implements support for NURBS boundary representation geometry. Working with NURBS is pretty hard so you'll need to have either a suitable math or logic background, and lots of proposal milestones. | |
− | {| bgcolor=#fff | + | {| bgcolor=#fff width=100% |
! | ! | ||
!align=center|Languages | !align=center|Languages | ||
Line 49: | Line 46: | ||
!align=center|Contacts | !align=center|Contacts | ||
|- | |- | ||
− | |width=62%|'''[[ | + | |align=left width=62%|'''[[NURBS Intersections]]:''' Evaluate the intersection of two NURBS surfaces. You'll get a 3D curve or a point, line segment, or even a plane depending how the surfaces overlap. |
− | | | + | |align=center|C/C++ |
+ | |align=center|HARD | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Yapp, Rossberg]] | ||
+ | |- | ||
+ | |align=left width=62%|'''[[NURBS Editing Support]]:''' BRL-CAD doesn't currently have support for editing NURBS primitives. Fix that. | ||
+ | |align=center|C/Tcl | ||
|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%|'''[[ | + | |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. |
− | |C++ | + | |align=center|C and/or C++ |
− | |align=center| | + | |align=center|EASY |
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Rossberg]] |
|- | |- | ||
− | |width=62%|'''[[ | + | |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/C++ |
|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]] | ||
+ | |- | ||
+ | |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 purdy. | ||
+ | |align=center|C/C++ | ||
+ | |align=center|MEDIUM | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Yapp, Morrison]] | ||
|} | |} | ||
− | |||
− | {| bgcolor=#fff | + | === Project: Refactoring=== |
+ | |||
+ | BRL-CAD has more than a million lines of code so we have to continually refactor and clean up code for maintainability. Cruft happens. These projects help reduce the complexity and make things better. They're not very hard at all, but exceedingly valuable to our project vitality. | ||
+ | |||
+ | {| bgcolor=#fff | ||
! | ! | ||
!align=center|Languages | !align=center|Languages | ||
Line 73: | Line 83: | ||
!align=center|Contacts | !align=center|Contacts | ||
|- | |- | ||
− | | | + | |width=62%|'''[[MGED to Archer Command Migration]]:''' Our next-generation editor (Archer) needs to have the same (700+) commands that are in MGED. Help make our next CAD interface awesome. |
− | |align=center|C | + | |align=center|C and Tcl |
− | |align=center| | + | |align=center|EASY |
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Yapp]] |
|- | |- | ||
− | |width=62%|'''[[ | + | |width=62%|'''[[Code Reduction]]:''' BRL-CAD is more than 1M lines of code. Approximately 10% of that is duplication. Help reduce that percentage. |
− | |align=center| | + | |align=center|C |
|align=center|EASY | |align=center|EASY | ||
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Greenwald, Morrison]] |
|- | |- | ||
− | | | + | |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. |
− | |align=center|C | + | |align=center|C |
− | |align=center| | + | |align=center|EASY |
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Yapp]] | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Greenwald, Yapp, Morrison]] |
|- | |- | ||
− | | | + | |width=62%|'''[[Rework of libbu/libbn to not require Tcl]]:''' Tcl's '''''C API''''' is used throughout BRL-CAD providing great abstractions, but we want our basic utility and numeric libraries (LIBBU & LIBBN) to stand alone. |
− | |align=center|C | + | |align=center|C |
|align=center|EASY | |align=center|EASY | ||
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison, Yapp, Greenwald]] |
|- | |- | ||
− | |width=62%|'''[[ | + | |width=62%|'''[[Consolidate image processing]]:''' We have 100+ image processing tools that independently read and write file data. Needs much reuse love. |
|align=center|C | |align=center|C | ||
− | |align=center| | + | |align=center|EASY |
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Greenwald]] |
|- | |- | ||
− | |width=62%|'''[[ | + | |width=62%|'''[[Fix Bugs]]:''' We take pride in our breadth of functionality and time-tested stability. We still have bugs. Identify some and fix 'em! |
− | |align=center|C | + | |align=center|C |
|align=center|EASY | |align=center|EASY | ||
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|TBD]] |
+ | |- | ||
+ | |width=62%|'''[[Mesh library cleanup]]:''' BRL-CAD has an extensive n-manifold polygonal mesh library that needs some refactoring, testing, and optimization rework. | ||
+ | |align=center|C | ||
+ | |align=center|MEDIUM | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison, Rossberg]] | ||
+ | |} | ||
+ | |||
+ | |||
+ | ===Project: Graphical User Interface === | ||
+ | |||
+ | Better cross platform support and improved GUI usability are high on BRL-CAD's priority list, but those developments require some fundamental work on our core display libraries. | ||
+ | |||
+ | {| bgcolor=#fff | ||
+ | ! | ||
+ | !align=center|Languages | ||
+ | !align=center|Difficulty | ||
+ | !align=center|Contacts | ||
|- | |- | ||
− | |width=62%|'''[[ | + | |width=62%|'''[[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. |
|align=center|C/C++ | |align=center|C/C++ | ||
|align=center|MEDIUM | |align=center|MEDIUM | ||
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] |
+ | |} | ||
+ | |||
+ | ===Project: Geometry Conversion=== | ||
+ | |||
+ | When it comes to geometry conversion, STEP is our priority but other formats like COLLADA, X3D, and IGES are also interesting. | ||
+ | {| bgcolor=#fff | ||
+ | ! | ||
+ | !align=center|Languages | ||
+ | !align=center|Difficulty | ||
+ | !align=center|Contacts | ||
|- | |- | ||
|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 112: | Line 149: | ||
|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%|'''[[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|MEDIUM | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Yapp]] | ||
|- | |- | ||
|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. | ||
Line 118: | Line 160: | ||
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] | ||
|- | |- | ||
− | |width=62%|'''[[ | + | |width=62%|'''[[IGES import improvements]]:''' We have extensive support for the International Geometry Exchange Standard (IGES) with our g-iges and iges-g converters, but they need updating. |
− | |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%|'''[[ | + | |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%|'''[[ | + | |width=62%|'''[[Voxelize]] command:''' Convert geometry into voxel data sets by shooting a grid of rays. The finite element analysis and volumetric rendering folks will love you. |
− | |align=center| | + | |align=center|C |
− | |align=center| | + | |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]] |
|} | |} | ||
− | == | + | ===Project Geometry Processing=== |
+ | |||
+ | As part of our new GUI development efforts, a lot of code had to be moved out of application space into a library. That library is our geometry editing library, LIBGED. A lot of time, attention, and emphasis is going on there to make sure that all of our core functionality is reusable by applications. More than 100k lines of code have already moved, but there's still a lot more work needed. | ||
{| bgcolor=#fff | {| bgcolor=#fff | ||
Line 142: | Line 186: | ||
!align=center|Contacts | !align=center|Contacts | ||
|- | |- | ||
− | | | + | |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| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Yapp]] |
|- | |- | ||
− | | | + | |width=62%|'''[[Geometric Constraint Solver]]:''' Our LIBPC parametric constraint library is the work-in-progress foundation of being able to validate and describe geometry relationships. |
− | + | |align=center|C/C++ | |
− | |||
− | |||
− | |||
− | |||
− | |align=center|C/ | ||
|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]] | ||
+ | |} | ||
+ | |||
+ | |||
+ | == Conversion == | ||
+ | We are an invested heavily in the ISO 10303 STEP standard for geometry import and export. Collaborating with the [http://stepcode.org STEPcode] community, we will be allocating one or more slots to a qualified capable student to specifically work on a STEP project. | ||
+ | |||
+ | {| bgcolor=#fff width=100% | ||
+ | ! | ||
+ | !align=center|Languages | ||
+ | !Impact | ||
+ | !align=center|Difficulty | ||
+ | !align=center|Contacts | ||
|- | |- | ||
− | |align= | + | |width=62%|'''[[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. |
− | |align=center|C/ | + | |ANY (C/C++, Python, Java, Perl, ...) |
− | |align=center| | + | |align=center|EASY |
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Mark, Charlie]] |
+ | |- | ||
+ | |width=62%|'''[[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. | ||
+ | |align=center|C++ | ||
+ | |align=center|EASY | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Mark, Charlie]] | ||
+ | |- | ||
+ | |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|MEDIUM | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Mark, Charlie]] | ||
+ | |- | ||
+ | |width=62%|'''[[STEP AP 242 Parser]]:''' We already parse a subset of AP203, but the new kid on the block is AP242. Make AP242 work with BRL-CAD's step-g importer. | ||
+ | |align=center|C++ | ||
+ | |align=center|EASY | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Mark, Charlie]] | ||
+ | |- | ||
+ | |width=62%|'''[[STEP Libraries]]:''' We took over NIST's STEP Class Library (SCL) project during our development of a STEP importer. SCL has since turned into a larger community collaboration. The code needs cleanup. | ||
+ | |align=center|C/C++ | ||
+ | |align=center|EASY | ||
+ | |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. |
|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|Mark, Charlie]] |
+ | |} | ||
+ | |||
+ | |||
+ | == Web Development == | ||
+ | |||
+ | We have high expectations for web development projects because the developer often does not stick around after development is over. We're not interested in web code, we're interested in people. If you're willing to work on your project long after GSoC is over (i.e., joining the project) and are willing to make a long-term commitment to BRL-CAD, then we ''absolutely'' welcome your web development project idea. | ||
+ | |||
+ | {| bgcolor=#fff | ||
+ | ! | ||
+ | !align=center|Languages | ||
+ | !align=center|Difficulty | ||
+ | !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. |
− | | | + | |Depends (likely PHP or Python) |
|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%|'''[[ | + | |width=62%|'''[[Benchmark Performance Database]]:''' BRL-CAD's Benchmark has been used for two decades to compare performance across configurations. Build a database website. |
− | | | + | |Depends (likely PHP or Python) |
− | |align=center| | + | |align=center|MEDIUM |
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] |
|- | |- | ||
− | |width=62%|'''[[ | + | |width=62%|'''[[Materials Database]]:''' Create a Materials Database web site for collecting, managing, and providing programmatic interfaces to material properties. |
− | | | + | |Depends (likely PHP or Python) |
|align=center|MEDIUM | |align=center|MEDIUM | ||
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison, Yapp]] |
|} | |} | ||
− | == | + | |
+ | == Graphical User Interface (GUI) == | ||
+ | |||
+ | The primary environment in which users interact with BRL-CAD geometry is the MGED geometry editor. The "next generation" interface for MGED, dubbed ''Archer'', has been under development for some time but there is a lot of functionality that still needs to be migrated and new features needed by MGED, Archer, or both. | ||
{| bgcolor=#fff | {| bgcolor=#fff | ||
Line 195: | Line 276: | ||
!align=center|Difficulty | !align=center|Difficulty | ||
!align=center|Contacts | !align=center|Contacts | ||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
|width=62%|'''[[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. | |width=62%|'''[[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. | ||
Line 206: | Line 282: | ||
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison, Yapp]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison, Yapp]] | ||
|- | |- | ||
− | |width=62%|'''[[ | + | |width=62%|'''[[GUI Integration of Analysis Tools]]:''' There are a ''lot'' of visualization tools in BRL-CAD, but most aren't integrated with the GUI. Visualizing directly within the GUI would improve usability. |
+ | |align=center|C | ||
+ | |align=center|MEDIUM | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Rossberg]] | ||
+ | |- | ||
+ | |width=62%|'''[[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. | ||
|align=center|C | |align=center|C | ||
+ | |align=center|HARD | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison, Rossberg]] | ||
+ | |- | ||
+ | |width=62%|'''[[Visualizing Constructive Solid Geometry (CSG)]]:''' CSG forms a directed acyclic graph. Tree view widgets show a simple hierarchical representation, but we need something better. | ||
+ | |align=center|C/C++ | ||
|align=center|EASY | |align=center|EASY | ||
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] |
+ | |} | ||
+ | |||
+ | |||
+ | === Geometry Processing === | ||
+ | |||
+ | As part of our new GUI development efforts, a lot of code had to be moved out of application space into a library. That library is our geometry editing library, LIBGED. A lot of time, attention, and emphasis is going on there to make sure that all of our core functionality is reusable by applications. More than 100k lines of code have already moved, but there's still a lot more work needed. | ||
+ | |||
+ | {| bgcolor=#fff | ||
+ | ! | ||
+ | !align=center|Languages | ||
+ | !align=center|Difficulty | ||
+ | !align=center|Contacts | ||
|- | |- | ||
|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]] |
|- | |- | ||
|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]] |
|- | |- | ||
− | |width=62%|'''[[ | + | |width=62%|'''[[Geometry Selection Functionality]]:''' Implement a new selection command that lets you temporarily group objects based on spatial, attribute, or geometric properties. |
|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]] |
|- | |- | ||
− | |width=62%|'''[[ | + | |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. |
− | |align=center|C | + | |align=center|C |
− | |align=center| | + | |align=center|HARD |
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Greenwald, Yapp, Morrison]] |
|- | |- | ||
− | |width=62%|'''[[ | + | |width=62%|'''[[Overlap tool]]:''' Resolving geometric interferences (aka overlaps) is a common geometry editing activity. Design an awesome interface for resolving conflicts. |
− | + | |Tcl | |
− | |||
− | |||
− | |||
− | |||
− | | | ||
|align=center|EASY | |align=center|EASY | ||
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Yapp, Morrison, Greenwald]] |
|} | |} | ||
− | == Rendering & | + | |
+ | === Rendering & Analysis === | ||
+ | |||
+ | Raytracing is at the heart of all that is BRL-CAD. The 'rt' application was the world's first distributed parallel ray tracer, implemented in early 80's, and it's backed by our powerful LIBRT library. We're the best as full path shotlines (shooting all the way through geometry, not just first hit) and can handle crazy big geometry very efficiently, very fast. It's how we perform geometric analysis, generate images, perform simulations, and more. | ||
{| bgcolor=#fff | {| bgcolor=#fff | ||
Line 250: | Line 346: | ||
!align=center|Contacts | !align=center|Contacts | ||
|- | |- | ||
− | |width=62%|'''[[ | + | |width=62%|'''[[Shader Enhancements]]:''' We have a functioning custom shader system in BRL-CAD, but there are now folks that specialize and there's lot of room for improvements. |
|align=center|C | |align=center|C | ||
− | |align=center| | + | |align=center|EASY |
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison, Greenwald]] |
|- | |- | ||
|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 259: | Line 355: | ||
|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%|'''[[NMG Raytracing Performance Improvement]]:''' BRL-CAD's structured mesh geometry (N-Manifold Geometry = NMG) needs some time in a profiler. Malloc during raytracing is bad. | ||
+ | |align=center|C | ||
+ | |align=center|HARD | ||
+ | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison, Greenwald]] | ||
|- | |- | ||
|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 274: | Line 375: | ||
|align=center|HARD | |align=center|HARD | ||
|align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Yapp, Morrison]] | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Yapp, Morrison]] | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|} | |} | ||
− | |||
− | |||
− | |||
− | = | + | === Project: Scientific === |
− | + | BRL-CAD has been used to visualize Hubble up in orbit (before it was launched), simulate light transport (multispectral analyses), model Earth's interior layers (education), and much more but there are lots of coding projects that would really help make BRL-CAD more useful for general science a work. | |
− | {| bgcolor=#fff | + | {| bgcolor=#fff |
! | ! | ||
− | !align=center|Languages | + | !align=center|Languages |
!align=center|Difficulty | !align=center|Difficulty | ||
!align=center|Contacts | !align=center|Contacts | ||
|- | |- | ||
− | | | + | |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| | + | |align=center|EASY |
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison, Greenwald]] |
|- | |- | ||
− | | | + | |width=62%|'''[[Bending light]]:''' Think gravity wells and satellite cameras. |
− | |align=center| | + | |align=center|C |
|align=center|MEDIUM | |align=center|MEDIUM | ||
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Morrison]] |
|- | |- | ||
− | | | + | |width=62%|'''[[Celestial mechanics particle system]]:''' Simulate solar systems and galaxies. |
− | |align=center|C++ | + | |align=center|C/C++ |
|align=center|MEDIUM | |align=center|MEDIUM | ||
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Greenwald]] |
|- | |- | ||
− | | | + | |width=62%|'''[[Non-vacuum gravity simulator]]:''' Simulate falling to earth. |
− | |align=center|C++ | + | |align=center|C/C++ |
|align=center|MEDIUM | |align=center|MEDIUM | ||
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Greenwald, Morrison, Yapp]] |
|- | |- | ||
− | | | + | |width=62%|'''[[Polarization]]:''' We already do multispectral ray tracing, but don't simulate polarization effects. Implement ray splitting and filtering. |
− | + | |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|Morrison, Rossberg]] |
|- | |- | ||
− | | | + | |width=62%|'''[[Density functions]]:''' Accurately represent everything from atmosphere to bone. Implement support for parametric density functions for homogenous materials. |
− | + | |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|Rossberg, Morrison]] |
− | |} | + | |} |
− | |||
− | = | + | == OpenSCAD Projects == |
− | + | {| bgcolor=#fff width=100% | |
− | |||
− | |||
− | |||
− | {| bgcolor=#fff | ||
! | ! | ||
!align=center|Languages | !align=center|Languages | ||
Line 380: | Line 428: | ||
!align=center|Contacts | !align=center|Contacts | ||
|- | |- | ||
− | + | |align=left width=62%|'''[https://github.com/openscad/openscad/wiki/Ideas:-GSoC-2014#wiki-issue-handling Issue Handling]:''' Description... | |
− | | | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|align=center|C++ | |align=center|C++ | ||
− | |align=center| | + | |align=center|EASY |
− | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors| | + | |align=center|[[Google_Summer_of_Code/Project_Ideas#Mentors|Marius]] |
− | | | + | |} |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | == Other Tool Projects == | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | Some of these project ideas aren't as detailed or elaborate as the ones above, but would be interesting and useful nonetheless. Please discuss with us before proposing one of these ideas. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | * [[Automated exploded view tool]] (C/C++/Tcl) | |
+ | * [[Automated cutaway view tool]] (C/C++/Tcl) | ||
+ | * [[Converter completion so all current formats have both import and export]] (C) | ||
+ | * [[GUI Animation editor/creator]] (C/Tcl) | ||
+ | * [[Blender file format converter]] (C) | ||
+ | * [[Object-oriented interfaces]] (C/C++) | ||
− | + | == <AN IDEA OF YOUR OWN> == | |
− | + | Do you have an idea of your own? [[Mailing Lists|Let us know]] and maybe we'll like it too. We're very open to new ideas, areas of academic research, industry applications, and any other ways that may help get you hooked on BRL-CAD development. Just remember that BRL-CAD is a solid modeling CAD suite so keep that in mind when scoping your project. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | Requirements: | |
− | + | *Passion for the task being suggested | |
− | + | *Buy-in from one of the existing developers | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
= Mentors = | = Mentors = | ||
Line 611: | Line 461: | ||
* Christopher Sean Morrison | * Christopher Sean Morrison | ||
** brlcad on irc.freenode.net | ** brlcad on irc.freenode.net | ||
− | ** Org admin, | + | ** Org admin, core dev, open source project lead |
* Erik Greenwald | * Erik Greenwald | ||
** ``Erik on irc.freenode.net | ** ``Erik on irc.freenode.net | ||
− | ** Org admin, | + | ** Org admin, core dev |
− | |||
* Cliff Yapp | * Cliff Yapp | ||
** starseeker on irc.freenode.net | ** starseeker on irc.freenode.net | ||
− | ** | + | ** Mentor, core dev |
* Daniel Rossberg | * Daniel Rossberg | ||
** d_rossberg on irc.freenode.net | ** d_rossberg on irc.freenode.net | ||
− | ** | + | ** Mentor, core dev, math expert |
* H.S. Rai | * H.S. Rai | ||
** hsrai on irc.freenode.net | ** hsrai on irc.freenode.net | ||
− | ** | + | ** Mentor, math expert |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
* Mark Pictor | * Mark Pictor | ||
** mpictor on irc.freenode.net | ** mpictor on irc.freenode.net | ||
− | ** | + | ** STEP Mentor |
* Charlie Stirk | * Charlie Stirk | ||
** cstirk | ** cstirk | ||
− | ** | + | ** STEP Mentor |
* Marius Kintel | * Marius Kintel | ||
Line 664: | Line 491: | ||
** OpenSCAD Mentor | ** OpenSCAD Mentor | ||
− | * | + | * Dongxu Li |
− | ** | + | ** dli on irc.freenode.net |
− | ** | + | ** LibreCAD Mentor |
− | * | + | * Jose Rallaz |
− | ** | + | ** rallazz on irc.freenode.net |
** LibreCAD Mentor | ** LibreCAD Mentor | ||
− | * | + | * Ries van Twisk |
− | ** | + | ** ries on irc.freenode.net |
** LibreCAD Mentor | ** LibreCAD Mentor | ||
− | * | + | * Jasleen Kaur |
− | ** | + | ** jasleen on irc.freenode.net |
− | ** | + | ** LibreCAD Mentor |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− |