Editing Deuces
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: | ||
− | + | This is a list of succinct tasks that are expected to take most people familiar with the prerequisites less than two hours to complete. It's a great starting point for anyone interested in contributing to BRL-CAD. | |
− | + | The tasks are all roughly the same complexity with '''''no prior BRL-CAD experience expected'''''. A description is provided along with a list of references and files you'll probably need to edit. Can we make it any easier? | |
− | = | + | = Getting Started = |
− | + | Contact us (via [[IRC]] or [[Mailing_Lists|brlcad-devel mailing list]]) if you have questions, comments, or ideas of your own you'd like to suggest. | |
+ | |||
+ | We've made an awesome virtual disk image that has everything you need preconfigured and ready to go: | ||
# [https://sourceforge.net/projects/brlcad/files/BRL-CAD%20for%20Virtual%20Machines/ Download our BRL-CAD Virtual Machine (VM) disk image.] | # [https://sourceforge.net/projects/brlcad/files/BRL-CAD%20for%20Virtual%20Machines/ Download our BRL-CAD Virtual Machine (VM) disk image.] | ||
# [https://www.virtualbox.org/wiki/Downloads Install VirtualBox.] | # [https://www.virtualbox.org/wiki/Downloads Install VirtualBox.] | ||
− | # Import | + | # Import and start the VM, log in (the password is "Brlcad!" without the quotes). |
− | # Run "svn up brlcad-svn-trunk" and | + | # Run "svn up brlcad-svn-trunk" and get started! |
− | = Pick a Task = | + | =Pick a Task= |
− | + | We break down all tasks into one of five categories. Don't be worried if the tasks all sound confusing to you. Just pick one and start reading the references we've provided. Join IRC or our mailing list and ask questions. | |
− | + | # Code (programming) | |
− | + | # Documentation and Training (writing) | |
− | + | # Outreach and Research (graphics) | |
− | + | # Quality Assurance (testing) | |
− | + | # User Interface (designing) | |
__TOC__ | __TOC__ | ||
+ | ---- | ||
== Code == | == Code == | ||
+ | ---- | ||
''Tasks related to writing or refactoring code'' | ''Tasks related to writing or refactoring code'' | ||
See the When You're Done section above for details on submitting your changes. | See the When You're Done section above for details on submitting your changes. | ||
+ | | ||
+ | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | ||
+ | | | ||
+ | === Fix bounding box function for our polygonal mesh (BoT) primitive === | ||
− | + | BRL-CAD provides functions for its geometric primitives that define a bounding box - a box that completely encloses the volume described by the primitive. Ideally, these boxes are as small as possible while still enclosing the primitive. Currently the routine for BoTs is incorrect. You can use stl-g, obj-g, or any of our other *-g converters to import BoT geometry for testing. | |
− | |||
− | |||
− | |||
− | BRL-CAD | ||
− | This task involves | + | This task involves studying the current code for the function rt_bot_bbox() and determining what is causing the current inaccuracies (the mged 'bb' command is a good way to visualize primitive bounding boxes). Make changes to produce a more optimal bounding box. Reimplement it from scratch if you like. The raytracing prep code in rt_bot_prep does prepare a better bounding box, so that is one place to check. |
Code: | Code: | ||
− | * src/ | + | * src/librt/primitives/bot/bot.c |
− | |||
− | |||
+ | |} | ||
| | ||
− | |||
| | ||
+ | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | ||
+ | | | ||
+ | === Close MGED when both windows are closed === | ||
− | + | BRL-CAD has an interactive geometry editor called MGED. It's often the starting point for beginners and allows creation and manipulation of models using commands. When ''mged'' is run, it creates 2 windows: a text-console command window and an interactive graphics window. When the user closes one of those windows, there is a bug. Closing the graphics window closes the command window. | |
− | |||
− | |||
− | + | This task involves fixing this behavior so that ONLY closing ''both'' windows terminates the process properly and that closing either window does not take the other along with it. | |
− | + | Code: | |
+ | * src/mged/mged.c | ||
+ | * src/tclscripts/mged/openw.c | ||
− | + | |} | |
− | + | | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|} | |} | ||
| | ||
+ | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | ||
+ | | | ||
− | + | === Implement a primitive centroid function === | |
− | |||
− | === Implement a primitive | ||
− | BRL-CAD provides more than two dozen types of geometry "primitives" such as ellipsoids, boxes, and cones | + | BRL-CAD provides more than two dozen types of geometry "primitives" such as ellipsoids, boxes, and cones. Every primitive is described by a collection of callback functions, for example rt_ell_bbox() returns the bounding box dimensions for an ellipsoid. Wikipedia, Wolfram Mathworld, and various other math sites (and research papers) around the web include the equations for most of our basic primitives while others are a little more tricky to compute. |
− | This task involves writing | + | This task involves writing a new callback function that takes an rt_db_internal object and calculates its centroid (as a point_t 3D point). There are numerous examples in our code where we compute centroids for other primtiives. The primitives that do not already have a centroid callback are itemized in following. |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | There are numerous examples in our code where we compute | ||
References: | References: | ||
− | * http://en.wikipedia.org/wiki/ | + | * http://en.wikipedia.org/wiki/Centroid |
− | |||
* http://mathworld.wolfram.com/ | * http://mathworld.wolfram.com/ | ||
− | * include/raytrace.h: See | + | * include/raytrace.h: See ft_centroid callback defined in the rt_functab structure |
Code: | Code: | ||
Line 94: | Line 85: | ||
* src/librt/primitives/[PRIMITIVE]/[PRIMITIVE].c | * src/librt/primitives/[PRIMITIVE]/[PRIMITIVE].c | ||
− | + | ||
+ | {| cellpadding="20" cellspacing="0" border="2" width="100%" | ||
+ | | | ||
+ | ==== ... centroid function for extruded sketches (EXTRUDE) ==== | ||
|} | |} | ||
| | ||
− | {| style="background-color:# | + | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" |
− | | | + | | |
+ | |||
=== Implement a primitive UV-mapping callback === | === Implement a primitive UV-mapping callback === | ||
− | BRL-CAD provides more than two dozen types of geometry "primitives" such as ellipsoids, boxes, and cones. Every primitive is described by a collection of callback functions, for example | + | BRL-CAD provides more than two dozen types of geometry "primitives" such as ellipsoids, boxes, and cones. Every primitive is described by a collection of callback functions, for example rt_ell_bbox() returns the bounding box dimensions for an ellipsoid. One of those functions describes a UV mapping of the object's surface, which is used for things like texture and bump mapping. An example of this is rt_ell_uv() in the src/librt/primitives/ell/ell.c source file for an ellipsoid. Several of our more complex primitive types (such as BoT, NMG, and BREP/NURBS) do not presently implement a UV-mapping function leading to unexpected runtime behavior. |
This task involves implementing a UV-mapping callback for any of the primitives that do not already have a functional UV-callback defined. Note that this is an advanced task that might take you more than a couple hours if you don't have solid coding skills, but it's ultimately just a few lines of code. See other primitives that already implement a UV-mapping callback for reference. | This task involves implementing a UV-mapping callback for any of the primitives that do not already have a functional UV-callback defined. Note that this is an advanced task that might take you more than a couple hours if you don't have solid coding skills, but it's ultimately just a few lines of code. See other primitives that already implement a UV-mapping callback for reference. | ||
Line 108: | Line 103: | ||
References: | References: | ||
* http://en.wikipedia.org/wiki/UV_mapping | * http://en.wikipedia.org/wiki/UV_mapping | ||
− | * src/librt/primitives/[PRIMITIVE]/[PRIMITIVE].c, | + | * src/librt/primitives/[PRIMITIVE]/[PRIMITIVE].c, read the rt_*_uv() function |
+ | |||
+ | {| cellpadding="20" cellspacing="0" border="2" width="100%" | ||
+ | | | ||
+ | ==== ... UV-mapping for extruded sketches (EXTRUDE) ==== | ||
Code: | Code: | ||
Line 115: | Line 114: | ||
* include/rtgeom.h | * include/rtgeom.h | ||
+ | |} | ||
| | ||
+ | |||
|} | |} | ||
| | ||
+ | | ||
+ | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | ||
+ | | | ||
+ | === Implement a platform independent re-entrant sort function === | ||
+ | The classic C library qsort() does not support a context parameter. A work around is to store the context information in a static variable. However, this solution is not thread save and may result in unpredictable behavior. | ||
− | + | There are platform specific sort functions qsort_r() in incompatible versions for BSD and GNU and qsort_s() for MSVC. Your task is to implement a bu_sort() function for BRL-CAD which is platform independent. | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Code: | Code: | ||
− | * src/ | + | * src/libbu/sort.c |
− | |||
− | + | The new sort function could look like this: | |
+ | void bu_sort(genptr_t array, size_t nummemb, size_t sizememb, int (*compare)(const_genptr_t, const_genptr_t, genptr_t), genptr_t context); | ||
|} | |} | ||
| | ||
− | + | ---- | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
+ | |} | ||
| | ||
− | |||
| | ||
+ | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | ||
+ | | | ||
+ | === Solve fonts related bug in new wiki theme === | ||
− | + | BRL-CAD has been working on a new incarnation of the website and has developed a new wiki theme and wordpress theme. Wiki theme uses a font called 'open-sans' from google fonts directory. It's linked via CSS but it does not get loaded (we still see default serif all over the place). So your task will be to debug the CSS code and get Open Sans loaded. | |
− | |||
− | + | Links: | |
− | + | *http://beta.brlcad.org/wiki/Main_Page | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
| | ||
− | + | ---- | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Documentation and Training == | == Documentation and Training == | ||
− | + | ---- | |
''Tasks related to creating/editing documents and helping others learn more about BRL-CAD'' | ''Tasks related to creating/editing documents and helping others learn more about BRL-CAD'' | ||
− | {| style="background-color:# | + | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" |
− | + | | | |
=== Add missing documentation (for any ONE command) === | === Add missing documentation (for any ONE command) === | ||
Line 229: | Line 172: | ||
* doc/docbook/system/man1/en/*.xml | * doc/docbook/system/man1/en/*.xml | ||
− | |||
|} | |} | ||
+ | |||
| | ||
+ | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | ||
+ | | | ||
+ | === Write an article "BRL-CAD for dummies" === | ||
− | + | Although BRL-CAD has extensive documentation, still it needs a short and simple document which is particularly built for dummies. | |
− | |||
− | |||
− | + | This task involves writing a article named '''BRL-CAD for dummies'''. This article should start with the installation process, if there is any existing installation guide for dummies, provide a link to it. The main motive of this article to empower dummy to make his/her first model using BRL-CAD. One thing to be kept in mind while writing this article is that this article is mainly concentrated for dummies. So use simple language to an extent and if you need to mention some technical term, first explain that term. | |
− | + | The output of this task can be a pdf, html, doc, odt or any other document file that contains this article. Go through the link provided. Use screenshots and images to make it look attractive so that the reader is not bored. | |
Reference: | Reference: | ||
− | * | + | * http://brlcad.org/wiki/Documentation |
− | |||
− | |||
− | |||
− | |||
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
| | ||
− | + | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | |
− | {| style="background-color:# | + | | |
− | | | ||
− | |||
=== Write a "BRL-CAD Commands Quick Reference" document === | === Write a "BRL-CAD Commands Quick Reference" document === | ||
Line 291: | Line 204: | ||
* http://brlcad.org/wiki/Documentation | * http://brlcad.org/wiki/Documentation | ||
* http://brlcad.org/w/images/5/52/MGED_Quick_Reference_Card.pdf | * http://brlcad.org/w/images/5/52/MGED_Quick_Reference_Card.pdf | ||
− | * | + | * http://appletree.or.kr/quick_reference_cards/CVS-Subversion-Git/git-cheat-sheet-large.png |
− | * | + | * http://www.stdout.org/~winston/latex/latexsheet-0.png |
− | * | + | * http://img.docstoccdn.com/thumb/orig/524314.png |
− | * | + | * http://www.inmensia.com/files/pictures/internal/CheatSheetDrupal4.7.png |
− | * | + | * http://www.phpmagicbook.com/wp-content/uploads/2010/06/php-reference-card.jpg |
− | |||
|} | |} | ||
| | ||
− | + | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | |
− | {| style="background-color:# | + | | |
− | | | ||
− | |||
=== Doxygen cleanup === | === Doxygen cleanup === | ||
Line 315: | Line 225: | ||
* http://www.stack.nl/~dimitri/doxygen/ | * http://www.stack.nl/~dimitri/doxygen/ | ||
− | + | {| cellpadding="20" cellspacing="0" border="2" width="100%" | |
− | + | | | |
− | {| | ||
− | |||
==== ... doxygen cleanup for LIBBU ==== | ==== ... doxygen cleanup for LIBBU ==== | ||
Line 328: | Line 236: | ||
* misc/Doxyfile | * misc/Doxyfile | ||
− | |||
|} | |} | ||
+ | |||
| | ||
− | + | {| cellpadding="20" cellspacing="0" border="2" width="100%" | |
− | {| | + | | |
− | |||
==== ... doxygen cleanup for LIBWDB ==== | ==== ... doxygen cleanup for LIBWDB ==== | ||
Line 344: | Line 251: | ||
* misc/Doxyfile | * misc/Doxyfile | ||
− | |||
|} | |} | ||
| | ||
− | + | {| cellpadding="20" cellspacing="0" border="2" width="100%" | |
− | {| | + | | |
− | |||
==== ... doxygen cleanup for LIBRT ==== | ==== ... doxygen cleanup for LIBRT ==== | ||
Line 361: | Line 266: | ||
* src/librt/binunif | * src/librt/binunif | ||
* misc/Doxyfile | * misc/Doxyfile | ||
+ | |} | ||
+ | |} | ||
| | ||
+ | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | ||
+ | | | ||
+ | === Write up Wiki page tutorial on our Volumetric Primitive === | ||
+ | |||
+ | BRL-CAD provides a couple dozen distinct primitives. Each primitive is defined by a set of parameters. Several of the more complex primitives have a wiki page describing them in more detail with an example on how to create them. | ||
+ | |||
+ | This task involves writing up a page on the VOL primitive. Figure out how to use it (see the "in" command), create an example input data set, and write up a wiki page on exactly what steps are needed similar to our other wiki pages: | ||
+ | |||
+ | References: | ||
+ | * http://brlcad.org/wiki/DSP | ||
+ | * http://brlcad.org/wiki/Sketch | ||
+ | * http://brlcad.org/wiki/EBM <-- particularly useful as the data is similar for VOL | ||
+ | |||
+ | Show how to create a VOL with at least two layers/slices. Include images like the other examples. Put the write-up at http://brlcad.org/wiki/VOL | ||
+ | |||
|} | |} | ||
− | |||
| | ||
− | + | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | |
− | + | | | |
− | + | === Write a wiki tutorial on how to create a polygonal mesh (NMG) manually === | |
− | {| style="background-color:# | ||
− | |||
− | === | ||
BRL-CAD provides a couple dozen distinct primitives. Each primitive is defined by a set of parameters. Several of the more complex primitives have a wiki page describing them in more detail with an example on how to create them. | BRL-CAD provides a couple dozen distinct primitives. Each primitive is defined by a set of parameters. Several of the more complex primitives have a wiki page describing them in more detail with an example on how to create them. | ||
− | This task involves | + | This task involves writing up a page on the NMG polygonal mesh primitive. Figure out how to use it (not a simple task, will require some trial and error), create an example input, and write up a wiki page on exactly what steps are needed similar to our other wiki pages: |
References: | References: | ||
− | |||
* http://brlcad.org/wiki/DSP | * http://brlcad.org/wiki/DSP | ||
− | |||
* http://brlcad.org/wiki/EBM | * http://brlcad.org/wiki/EBM | ||
+ | * http://brlcad.org/wiki/Sketch <-- particularly useful as neither NMG nor sketch are meant to be created manually | ||
+ | |||
+ | Note the "facetize" command in mged will convert an existing object into NMG format. The get/put commands should help from there like the sketch tutorial. | ||
+ | |||
+ | Show how to create an NMG cube or wedge or similar simple shape. Include images like the other examples. Put the write-up at http://brlcad.org/wiki/NMG | ||
− | |||
|} | |} | ||
+ | |||
| | ||
− | + | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | |
− | {| style="background-color:# | + | | |
− | |||
=== Fix Image Formatting in BRL-CAD's DocBook Documentation (any ONE large document or 4 smaller documents) === | === Fix Image Formatting in BRL-CAD's DocBook Documentation (any ONE large document or 4 smaller documents) === | ||
Line 437: | Line 357: | ||
* doc/docbook | * doc/docbook | ||
− | |||
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
− | + | ---- | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
==Outreach and Research == | ==Outreach and Research == | ||
+ | ---- | ||
''Tasks related to community management, outreach/marketing, studying problems, and recommending solutions'' | ''Tasks related to community management, outreach/marketing, studying problems, and recommending solutions'' | ||
− | {| style="background-color:# | + | |
− | + | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | |
+ | | | ||
=== Profile NURBS prep performance === | === Profile NURBS prep performance === | ||
Line 472: | Line 382: | ||
Running "rt -o file.png -s32" on the system command line (not inside mged) should minimize the ray overhead or you can specifically isolate the prep phase we care about. Prep is the time between when rt is run where it opens a window until the first pixels are fired and pixels start filling in. | Running "rt -o file.png -s32" on the system command line (not inside mged) should minimize the ray overhead or you can specifically isolate the prep phase we care about. Prep is the time between when rt is run where it opens a window until the first pixels are fired and pixels start filling in. | ||
+ | |} | ||
| | ||
− | + | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | |
− | + | | | |
− | |||
− | {| style="background-color:# | ||
− | |||
=== Continue investigating GMP integration === | === Continue investigating GMP integration === | ||
Line 489: | Line 397: | ||
Building on the previous GCI task work, take it to the next step. Try setting a vector to 1/3, 1/3, 1/3 and 0.1, 0.1, 0.1 and get proper values to print. Change the V3ARGS() macro if needed. If that all works, try to get bn_dist_pt3_pt3() to work. Report and discuss your progress. | Building on the previous GCI task work, take it to the next step. Try setting a vector to 1/3, 1/3, 1/3 and 0.1, 0.1, 0.1 and get proper values to print. Change the V3ARGS() macro if needed. If that all works, try to get bn_dist_pt3_pt3() to work. Report and discuss your progress. | ||
− | |||
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
| | ||
− | + | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | |
− | + | | | |
− | |||
− | {| style="background-color:# | ||
− | |||
=== Design a T-Shirt for BRL-CAD === | === Design a T-Shirt for BRL-CAD === | ||
Line 520: | Line 407: | ||
Logo References | Logo References | ||
− | * | + | * http://brlcad.org/images/angelov_256.png |
+ | * http://brlcad.org/d/node/92 | ||
− | |||
|} | |} | ||
+ | |||
| | ||
− | + | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | |
− | {| style="background-color:# | + | | |
− | |||
=== Design a coffee mug for BRL-CAD === | === Design a coffee mug for BRL-CAD === | ||
− | This task involves designing a coffee mug for BRL-CAD. Make it look good | + | This task involves designing a coffee mug for BRL-CAD. Make it look good, so that one can use it while working on BRL-CAD. Look over some great coffee mug designs before starting to work on this. It would be great if the design on coffee mug has some special meaning. |
Logo References | Logo References | ||
− | * | + | * http://brlcad.org/images/angelov_256.png |
+ | * http://brlcad.org/d/node/92 | ||
− | |||
|} | |} | ||
+ | |||
| | ||
− | + | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | |
− | {| style="background-color:# | + | | |
− | |||
=== Design BRL-CAD sticker === | === Design BRL-CAD sticker === | ||
Line 546: | Line 433: | ||
Logo References | Logo References | ||
− | * | + | * http://brlcad.org/images/angelov_256.png |
+ | * http://brlcad.org/d/node/92 | ||
+ | |||
+ | |} | ||
| | ||
+ | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | ||
+ | | | ||
+ | === Design BRL-CAD phone/tablet back cover === | ||
+ | |||
+ | This task involves designing a BRL-CAD phone/tablet cover. | ||
+ | While submitting your design, provide the sample phone cover, tablet cover with the design and rendered png or jpg image of the sticker design. Try to have a special meaning of design, and the concept should be creatively illustrated. | ||
+ | |||
+ | Logo References | ||
+ | * http://brlcad.org/images/angelov_256.png | ||
+ | * http://brlcad.org/d/node/92 | ||
+ | |||
|} | |} | ||
+ | |||
| | ||
+ | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | ||
+ | | | ||
+ | === Design a wallpaper set for BRL-CAD === | ||
− | + | This task involves designing a set of wallpapers for BRL-CAD. The central idea of each wallpaper should represent any feature of BRL-CAD. Try to design a minimum of 5 wallpapers but if you have more than 5 designs than you are welcomed. | |
− | |||
− | |||
− | |||
− | This task involves designing a | ||
− | Try to | + | Try to different resolutions of each wallpaper. |
− | + | Check the following wallpapers for inspiration. | |
* http://www.smashingmagazine.com/tag/wallpapers/ | * http://www.smashingmagazine.com/tag/wallpapers/ | ||
Logo References | Logo References | ||
− | * | + | * http://brlcad.org/images/angelov_256.png |
+ | * http://brlcad.org/d/node/92 | ||
− | |||
|} | |} | ||
+ | |||
+ | |||
| | ||
+ | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | ||
+ | | | ||
+ | === Create Iron Man Arc Reactor Model in BRL-CAD === | ||
− | + | This task involves creating Arc Reactor as seen in hollywood movie Iron-Man. You will have to create two versions of the Arc Reactor one glowing and another non glowing. | |
− | + | ||
− | + | Check this model for inspiration | |
+ | * http://grabcad.com/library/iron-man-arc-reactor-request | ||
− | |||
− | |||
− | |||
− | |||
− | |||
|} | |} | ||
− | + | ||
+ | |||
+ | ---- | ||
== Quality Assurance == | == Quality Assurance == | ||
+ | ---- | ||
''Tasks related to testing and ensuring code is of high quality'' | ''Tasks related to testing and ensuring code is of high quality'' | ||
− | {| style="background-color:# | + | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" |
− | + | | | |
=== Fix single-precision floating point crash === | === Fix single-precision floating point crash === | ||
Line 620: | Line 525: | ||
* src/liboptical/sh_light.c | * src/liboptical/sh_light.c | ||
− | |||
|} | |} | ||
+ | |||
| | ||
− | + | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | |
− | {| style="background-color:# | + | | |
− | |||
=== Fix closedb === | === Fix closedb === | ||
Line 644: | Line 548: | ||
* src/mged/mged.c | * src/mged/mged.c | ||
− | |||
|} | |} | ||
+ | |||
| | ||
− | + | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | |
− | {| style="background-color:# | + | | |
− | + | === Create an utility library (LIBBU) API unit test === | |
− | === Create | ||
There are more than 300 library functions in our core LIBBU library. As a core library used by nearly every one of BRL-CAD's tools, testing those functions for correct behavior is important. | There are more than 300 library functions in our core LIBBU library. As a core library used by nearly every one of BRL-CAD's tools, testing those functions for correct behavior is important. | ||
− | This task involves implementing new unit | + | This task involves implementing a new unit test for any of LIBBU's source files that do not already have a unit test defined. The test should run all of the public functions and be hooked into our build system. We have lots of existing unit tests to follow as an example. |
References: | References: | ||
Line 665: | Line 568: | ||
* src/libbu/tests/CMakeLists.txt | * src/libbu/tests/CMakeLists.txt | ||
− | + | ||
+ | {| cellpadding="20" cellspacing="0" border="2" width="100%" | ||
+ | | | ||
+ | ==== ... unit test for LIBBU bomb.c ==== | ||
+ | |} | ||
|} | |} | ||
+ | |||
| | ||
− | + | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | |
− | {| style="background-color:# | + | | |
− | | | + | === Create numerics library (LIBBN) API unit test === |
− | |||
− | === Create | ||
There are more than 300 library functions in our core LIBBN library. As a core library used by nearly every one of BRL-CAD's tools, testing those functions for correct behavior is important. | There are more than 300 library functions in our core LIBBN library. As a core library used by nearly every one of BRL-CAD's tools, testing those functions for correct behavior is important. | ||
− | This task involves implementing new unit | + | This task involves implementing a new unit test for any of LIBBN's source files that do not already have a unit test defined. The test should run all of the public functions and be hooked into our build system. We have lots of existing unit tests to follow as an example. |
References: | References: | ||
Line 683: | Line 589: | ||
* include/vmath.h | * include/vmath.h | ||
* src/libbn/*.c | * src/libbn/*.c | ||
− | * src/ | + | * src/libbu/tests/*.c <-- note libbu, not libbn for examples |
− | |||
Code: | Code: | ||
Line 690: | Line 595: | ||
* src/libbn/tests/CMakeLists.txt | * src/libbn/tests/CMakeLists.txt | ||
− | + | {| cellpadding="20" cellspacing="0" border="2" width="100%" | |
− | + | | | |
− | + | ==== ... unit test for LIBBN axis.c ==== | |
− | |||
− | |||
− | {| | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | ==== ... unit | ||
− | |||
|} | |} | ||
| | ||
− | + | {| cellpadding="20" cellspacing="0" border="2" width="100%" | |
− | {| | + | | |
− | + | ==== ... unit test for LIBBN qmath.c ==== | |
− | ==== ... unit | ||
− | |||
|} | |} | ||
| | ||
− | + | {| cellpadding="20" cellspacing="0" border="2" width="100%" | |
− | {| | + | | |
− | + | ==== ... unit test for LIBBN rand.c ==== | |
− | ==== ... unit | ||
− | |||
|} | |} | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|} | |} | ||
− | |||
| | ||
− | + | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | |
− | + | | | |
− | |||
− | {| style="background-color:# | ||
− | | | ||
− | |||
=== Find, reliably reproduce, and report any bug in Archer === | === Find, reliably reproduce, and report any bug in Archer === | ||
Line 748: | Line 625: | ||
* BUGS file in any source/binary distribution | * BUGS file in any source/binary distribution | ||
* http://sourceforge.net/tracker/?atid=640802&group_id=105292&func=browse | * http://sourceforge.net/tracker/?atid=640802&group_id=105292&func=browse | ||
+ | |} | ||
| | ||
− | + | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | |
− | + | | | |
− | |||
− | {| style="background-color:# | ||
− | |||
=== Reproduce any 10 unconfirmed open bug reports === | === Reproduce any 10 unconfirmed open bug reports === | ||
Line 763: | Line 638: | ||
References: | References: | ||
* https://sourceforge.net/tracker/?limit=100&func=&group_id=105292&atid=640802&assignee=100&status=1&submit=Filter | * https://sourceforge.net/tracker/?limit=100&func=&group_id=105292&atid=640802&assignee=100&status=1&submit=Filter | ||
+ | |} | ||
− | + | ||
− | + | ---- | |
− | |||
== User Interface == | == User Interface == | ||
+ | ---- | ||
''Tasks related to user experience research or user interface design and interaction'' | ''Tasks related to user experience research or user interface design and interaction'' | ||
− | {| style="background-color:# | + | |
− | + | | |
+ | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | ||
+ | | | ||
=== Create an ISST screenshot or animation === | === Create an ISST screenshot or animation === | ||
Everyone loves to see screenshots and animations of software in action. We use both in our marketing and outreach. See some of the examples below that we already have. | Everyone loves to see screenshots and animations of software in action. We use both in our marketing and outreach. See some of the examples below that we already have. | ||
− | Create an awesome screenshot and/or animation of our 'isst' tool in action. It's an interactive geometry viewer interface. It should be graphically interesting and give some sense of capability. You should import a visually complex and interesting model with LOTS of polygons and detail | + | Create an awesome screenshot and/or animation of our 'isst' tool in action. It's an interactive geometry viewer interface. It should be graphically interesting and give some sense of capability. You should import a visually complex and interesting model with LOTS of polygons and detail. |
References: | References: | ||
− | * | + | * http://brlcad.org/gallery/d/19-4/MGED.jpg |
+ | * http://brlcad.org/tmp/archer.png | ||
+ | * http://brlcad.org/gallery/s/screenshots/ | ||
+ | * http://www.google-melange.com/gci/task/view/google/gci2012/8019211 | ||
+ | |||
+ | Note that we have several screenshot tasks. Note you may have to go through some or our basic MGED tutorials (see docs section on our website) just to be able to display geometry. Finally, give others a chance if you already completed one of the other screenshot tasks. ;) | ||
+ | |||
+ | |} | ||
| | ||
+ | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | ||
+ | | | ||
+ | === Categorize all of BRL-CAD's commands into a spreadsheet === | ||
+ | |||
+ | BRL-CAD is a suite of more than 400 processing tools, image tools, geometry converters, and more. There is an existing spreadsheet that characterizes all of the available commands in terms of inputs, outputs, and options, but there is insufficient characterization of BRL-CAD's commands as to how they logically group and work together. | ||
+ | |||
+ | This task involves building up a spreadsheet that lists all of our commands, describing a finite set of command categories, and characterizing all commands into those categories while filling in the spreadsheet with details for each command. | ||
+ | |||
+ | References: | ||
+ | * A spreadsheet template will be provided. | ||
+ | |||
|} | |} | ||
+ | |||
| | ||
+ | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | ||
+ | | | ||
+ | === Design a Cover Photo for Facebook page (and other social networks) === | ||
− | + | BRL-CAD got it's logo changed, and it's website is undergoing a change. So this re-branding of BRL-CAD also requires a good, well designed and attractive cover photo for the BRL-CAD's Facebook page or other Social Media Appearances. It should feature a good tagline telling some killer feature of BRL-CAD, BRL-CAD's new logo and/or some illustration/image regarding the feature highlighted in tagline. | |
− | |||
− | + | It should be consistent with the color scheme of our new website design. | |
− | + | New website design | |
+ | *http://cpp-tricks.com/brlcad/ | ||
− | + | |} | |
| | ||
+ | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | ||
+ | | | ||
+ | |||
+ | === Design a banner ad for BRL-CAD === | ||
+ | |||
+ | BRL-CAD is one of the oldest open source communities. This community has a good following, so we want to give a chance to everyone so that they can show their support to the community by adding a banner ad in their website. You have to create a banner ad that can be embedded in the website by copy pasting some simple lines of code (basically an iframe). | ||
+ | |||
+ | Such a banner ad can also be used in various sections of our own website. | ||
+ | |||
+ | The task requires you to create a CSS3 based animated horizontal and vertical banner add, highlighting some feature of BRL-CAD or making some call to action. This call to action can be joining mailing list, or signing up for community, or link to latest post etc. | ||
+ | |||
+ | For Inspiration and tutorial refer | ||
+ | *http://tympanus.net/Tutorials/AnimatedWebBanners/ | ||
+ | |||
|} | |} | ||
+ | |||
| | ||
+ | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | ||
+ | | | ||
+ | === Creating Motion Typography video for BRL-CAD === | ||
− | + | BRL-CAD has a lot of great features that can be highlighted. A motion typography video highlighting these features would be a wonderful addition to the front page of website. | |
− | |||
− | + | This task requires you to create a motion typography video that will convince user to give BRL-CAD a try, it could be titled something like "x reasons to choose BRL-CAD" or anything similar (give your creative minds a flight). The video should not be more than 2 minutes. | |
− | + | For inspiration about what a motion typography, see | |
+ | *http://vimeo.com/24715531 | ||
− | + | |} | |
− | |||
| | ||
+ | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | ||
+ | | | ||
+ | === Create a screen-cast for BRL-CAD === | ||
+ | |||
+ | Getting started with BRL-CAD is sometimes not so smooth. A screen-cast giving a tour of BRL-CAD's GUI and the steps involved in creating the first model will make it easy for users to get started. | ||
+ | |||
+ | For this task you need to install BRL-CAD on your computer. Create a very basic model in it and record your screen as you create the model. It should also give a tour of BRL-CAD's workspace. You can choose model of your choice. Keep something very basic and easy for the first time users. | ||
+ | |||
|} | |} | ||
+ | |||
+ | |||
| | ||
+ | {| style="background-color:#ffffff;" cellpadding="20" cellspacing="0" border="2" width="100%" | ||
+ | | | ||
+ | === Loading Google charts from API === | ||
− | + | A basic wrapper of GCharts has been implemented a while ago : https://bitbucket.org/suryajith/benchmark/src/a27dd8c05d6819a527650e06a63076599d2e0d66/libs/charting.py?at=default With the google charts improving their API system which wasn't around then, see if the code could be optimized so to get the charts the optimal way. | |
− | |||
− | |||
− | + | Reference: | |
+ | *https://developers.google.com/chart/interactive/docs/index | ||
− | |||
− | |||
|} | |} | ||
− | + | ---- | |
= When You're Done = | = When You're Done = | ||
+ | ---- | ||
For non-code, just send us your file(s). For code changes, you will be expected to [[Patches|provide a patch file]]. Make sure you ''read'' your patch file before submitting it. Make sure your patch file will apply cleanly to an unmodified checkout of BRL-CAD: | For non-code, just send us your file(s). For code changes, you will be expected to [[Patches|provide a patch file]]. Make sure you ''read'' your patch file before submitting it. Make sure your patch file will apply cleanly to an unmodified checkout of BRL-CAD: |