Design an MGED command spreadsheetBRL-CAD
Status: ClosedTime to complete: 48 hrs Mentors: SeanTags: design, spreadsheet

BRL-CAD's primary solid geometry modeling application is called MGED. MGED contains a comprehensive set of more than 700 commands for manipulating, viewing, and inspecting geometry. There is a need to more effectively manage those commands, characterize them all, and get a "big picture" of the command landscape so that usability may be addressed.

This task involves designing a spreadsheet that will be used to characterize all of MGED's commands.

References:

  • An existing spreadsheet already being used for BRL-CAD (i.e., non-MGED) commands is available.
Uploaded Work
File name/URLFile sizeDate submitted
mged.xls35.0 KBDecember 22 2012 13:57 UTC
mged_2.xls36.0 KBDecember 23 2012 07:28 UTC
mged_3.xls40.0 KBDecember 25 2012 06:13 UTC
mged_4.xls40.0 KBDecember 25 2012 06:36 UTC
Comments
Gmercer015on December 3 2012 22:47 UTCSpreadsheet extension

Does the spreadsheet need to have a specific extension? I would hope to be able to use OpenOffice spreadsheets as opposed to microsofts spreadsheets

Luison December 5 2012 00:51 UTCTask Claimed

I would like to work on this task.

Luison December 5 2012 00:52 UTCClaim Removed

The claim on this task has been removed, someone else can claim it now.

Sean on December 5 2012 01:59 UTCany will work

OO spreadsheets are just fine, even a Google Doc spreadsheet would be fine.

Sharanon December 11 2012 09:41 UTCQuestion

Should we provide the description of the comand also


I will claim this task after my current task will be reviewed

Sean on December 11 2012 22:02 UTClets start simple

A description is not needed at this time.  In fact, given the progress made on other tasks, I'd like to rescope this task to be even more simple.  See my "starting simple" comment here:


http://www.google-melange.com/gci/task/view/google/gci2012/7987215


The same holds true for this task, except that they're just not all sitting in a "bin" directory.  This should report all mged commands we care about:


bin/mged -c test.g info commands 21 | sed 's/ /\n/g' | sort | grep mged | sed 's/_mged_//g' | grep -v mged_


That gives me a list with 317 commands.  Those are the ones to be categorized into no less than 10 groups (but probably many many more).  See the MGED quick reference cheat sheet at http://brlcad.org/wiki/Documentation for a start at command-grouping.

Chan Ho Junon December 20 2012 12:56 UTCTask Claimed

I would like to work on this task.

Andrei Popescu on December 20 2012 13:04 UTCTask Assigned

This task has been assigned to Chan Ho Jun. You have 48 hours to complete this task, good luck!

Chan Ho Junon December 20 2012 13:09 UTCQuestion

I did not quite understand the commands for


bin/mged -c test.g info commands 21 | sed 's/ /\n/g' | sort | grep mged | sed 's/_mged_//g' | grep -v mged_


and also how do I access the directory

Chan Ho Junon December 20 2012 13:32 UTCNever mind

I've just learned how to compile brl-cad using cmake. You can just ignore the question above :)

Sean on December 21 2012 05:02 UTConce compiled

Once you compile successfully, you'll be able to run that bin/mged line which will help to itemize all of mged's available commands.


 

Melange on December 22 2012 13:04 UTCInitial Deadline passed

Melange has detected that the initial deadline has passed and it has set the task status to ActionNeeded. The student has 24 hours to submit the work before the task is reopened and sent back to the pool for other students to claim.

Chan Ho Junon December 22 2012 13:57 UTCReady for review

The work on this task is ready to be reviewed.

Sean on December 23 2012 06:56 UTCnot sure

I'm not sure what to make of your spreadsheet...  Can you explain it for me?  What are the three columns after command supposed to represent?


 

Sean on December 23 2012 06:56 UTCTask Needs More Work

One of the mentors has sent this task back for more work. Talk to the mentor(s) assigned to this task to satisfy the requirements needed to complete this task, submit your work again and mark the task as complete once you re-submit your work.

Sean on December 23 2012 06:56 UTCDeadline extended

The deadline of the task has been extended with 2 days and 0 hours.

Chan Ho Junon December 23 2012 07:28 UTCReady for review

The work on this task is ready to be reviewed.

Sean on December 23 2012 14:59 UTCam we to infer

I suppose from your response that I'm to infer that the columns represent independent categories that describe the command, ala keywords?  


That's good effort and you went ahead and categorized the commands, so if that's the approach then the remaining work is to categorize the commands that have no category.  Every command should be in at least one of those categories.  How long did it take you to fill out the table thus far?


Also, we'll then need a tally count of how many commands are in which categories.


 

Sean on December 23 2012 15:00 UTCTask Needs More Work

One of the mentors has sent this task back for more work. Talk to the mentor(s) assigned to this task to satisfy the requirements needed to complete this task, submit your work again and mark the task as complete once you re-submit your work.

Chan Ho Junon December 23 2012 23:19 UTCMissing commands

The compiling stuffs took the most out of the two days, and I would be able to finish the remaining commands if i were to know what those commands do. The blank commands I could not find through the the "help" command nor through the MGED commands site. What shall I do with those? Or are they commands that are not existing?

Sean on December 24 2012 17:14 UTCcompiling doesn't count

Time spent compiling BRL-CAD doesn't count. :)


How long did it take to fill out the spreadsheet?


While many of those commands don't have help, they do have a usage statement if you run them within MGED.  That may help you categorize the remaining ones.


Try that and see if you can get some of the rest.  Submit that again and it should be good.

Sean on December 24 2012 17:14 UTCDeadline extended

The deadline of the task has been extended with 1 days and 0 hours.

Chan Ho Junon December 25 2012 06:23 UTCDone?

The whole spreadsheet took me about a total of four to five hours, but I just think that is nothing compared to the time spent on figuring how to compile. But anyways, I have shrunken the number of missing commands to three: get_solid_keypoint, rate, and select. I have spent my extended time researching each and every missing commands and I think this is the most I could do. 

Chan Ho Junon December 25 2012 06:37 UTCmged_4

mged_4 should be the final spreadsheet with three missing commands

Chan Ho Junon December 25 2012 06:37 UTCReady for review

The work on this task is ready to be reviewed.

Melange on December 26 2012 14:05 UTCNo more Work can be submitted

Melange has detected that the deadline has passed and no more work can be submitted. The submitted work should be reviewed.

Sean on December 26 2012 17:52 UTCTask Closed

Congratulations, this task has been completed successfully.

Sean on December 26 2012 17:53 UTCthanks

Thank you, Chan.  Nicely done.  We'll likely have a follow-on task defined in a few days, if you're interested, so keep an eye out for it.

Sean on January 14 2013 15:11 UTCthank you

As GCI comes to a close, we wanted to take the time to say THANK YOU for all your efforts.  This comment interface closes after GCI is over, so you're encouraged to join our mailing list where we'll be announcing contributions from GCI participants like yourelf over the upcoming months: 


https://lists.sourceforge.net/lists/listinfo/brlcad-news


If you've provided your full name, we'll be sure to credit you in our authorship documentation and you'll see your name in a future announcement.  If you contact us at devs@brlcad.org or via IRC, we'll even let you know when your work is integrated and follow up with updates.  You're welcome and encouraged to contact us any time, especially if you have a question about how to continue participating in Open Source after GCI is over, but even if just to keep in touch.  Note that ongoing participation in Open Source is one of the most impressive skills to have on your resumé.  Take care, be well, and thank you again!